|
Siebel Assignment Manager Administration Guide > Assignment Rule Administration > Process of Defining Assignment Rules >
Creating Assignment Rule Groups
Before defining assignment rules based on your particular business needs, you need to decide whether you want to use rule groups. Create rule groups if you want a separate set of assignment rules that you can apply to different business scenarios. Another factor you should consider when deciding to create rule groups is whether or not you need rule group hierarchies. Use rule group hierarchies if you plan to use delegated assignment. Alternatively, you do not need to create rule groups if you want all rules processed every time you run Assignment Manager. In this case, you use the Default Rule Group that is provided as part of the Assignment Manager seed data. This topic explains how to create new assignment rule groups using the assignment administration views. This task is a step in Process of Defining Assignment Rules. To create an assignment rule group
- From the application-level menu, choose Navigate > Site Map > Administration - Assignment > Rule Groups List.
- In the Rule Groups List list, click New.
- In the new record, click in the available fields to enter relevant information for the new rule group.
The new rule group appears in the Rule Group List and the Rule Group Explorer.
Table 21 shows the predefined fields. TIP: All fields may not be visible in the initial view; use the Columns Displayed feature to make fields visible (right-click, select Columns Displayed, use the arrows to move a field from Available Columns to Selected Columns, and then click Save).
Table 21. Assignment Rule Group Fields
|
|
Activation |
Start date of the assignment rule group. By default, rules within a group inherit the activation date from the group date. However, if you specify an activation date for a particular rule, it overrides that date. NOTE: If your application is enabled for the Universal Time Coordinated (UTC) standard, see Global Deployment Guide for proper database settings.
|
Expiration |
End date of the assignment rule group. By default, rules within a group inherit the expiration date from the group date. However, if you specify an activation date for a particular rule, it overrides that date. NOTE: If your application is enabled for the Universal Time Coordinated (UTC) standard, see Global Deployment Guide for proper database settings.
|
Key Based |
Indicates the rule group is intended for key-based routing and usually has a corresponding server key mapping. By checking this flag, even if there is no server key mapping defined for the rule group, this makes sure that the rules that belong to this rule group are not processed when running the assignment server in default mode. Note: The Key Based field may be a hidden column on the Assignment Rule Groups list. You can enable the Key Based field by selecting it through the Columns Displayed feature. For more information about key-based routing and server key maps, see About Server Key Maps. |
Name |
Name of the assignment rule group. |
Organization |
The organization in which this rule group belongs. |
Owner Login |
The login of the owner position. The owner position has visibility from the delegated administration views for rule groups and each of the child rule groups. |
Owner Position |
The owner of the rule group. Each rule group has an owner (and potentially designees who also have owner rights). For more information about owners and designees, see Owners and Designees. |
Parent Rule Group |
A rule group that appears directly above another rule group in the hierarchy. |
For more information about rule groups and the Default Rule Group, see About Assignment Rule Groups. If you plan to use delegated assignment, see also Creating Child Assignment Rule Groups.
|
