My Oracle Support Banner

A Future Activation Date For Assignment Rule Employees Is Getting Ignored (Doc ID 2820195.1)

Last updated on FEBRUARY 02, 2022

Applies to:

Siebel CRM - Version 8.1.1.11 [IP2013] and later
Information in this document applies to any platform.

Symptoms

When creating a new Assignment Rule and add a new employee candidate and set the Activation Date for a future date as shown in the first screenshot for the employee "Test1". For some reason, the Activation Date is getting ignored and new activities are getting assigned to this specific employee as shown in the second screenshot below:

 

 

NOTE: The same scenario is not reproduced if the Expiration Date was set for the employee "Test1" and then any new activities were assigned to the other employee "Test2" as shown in the screenshot below.

 

  

Step to reproduce the issue:

In Siebel Tools:
1. Go to Workflow Policy Object.
2. Query for the Object(Service Request).
3. Go to Assignment Object.
4. Change "Keep Man Asgn Primary Employee to False.



Siebel OpenUI:
1. Login into Siebel App.
2. Go to Sitemap > Administration - Assignment > Assignment Rules List.
3. Create a new Assignment Rule(SR Status) with the information below:

a. Person Candidates Source = From Rule
b. Organization Candidates Source = From Rule
c.  Assignee Filter = One, Best Fit
d. Candidate Passing Score = 10

4. Add a new Criteria. For this scenario, I am using "Service Request Priority" with Values(1-ASAP).
5. Go to Employee Candidates and add the following employees below:

a. Test1 | Score(15) | Activation(1/1/2022 12:00:00 AM).
b. Test2 | Score(10).


6. Go to Assignment Policies and remove the Expiration Date for "ASGN: Service Request" and then Release the Assignment Rules.
7. For WorkMon Component, changed the Group Name(Assignment Group), and set the Default Task to 1.
8. Submit a General Trigger Job. Note that this will create a new "trigger.sql" file with this new information above.

9. Go to Service Request > Service Request List Applet and create a new Service Request..
10. Change the SR Priority to 1-ASAP.
11. The new SR was assigned to Test1 a show the first screenshot above.

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
 Step to reproduce the issue:
Changes
Cause
Solution
 A. From Siebel Tools:
 B. Siebel Client:
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.