|
Siebel Public Sector Guide > Administering Benefits Cases >
About Controls for Benefit Data
In Siebel Public Sector, the records that contain benefit data have a hierarchical relationship with each other. Figure 1 shows this hierarchical relationship.
Figure 1. Benefit Data Hierarchy
|
Details about this benefit data hierarchy follow:
- A benefits application can include a benefits case.
- A benefits case can include benefit plans and service plans.
- A benefit plan can include benefits.
- A service plan can include benefits and goals.
- A benefit can include orders, payments, and attributes.
- A goal can include activities.
The Status field value of a given record in the benefit data hierarchy, the Status field value of the records that are above the given record (the parent record and grandparent record), and the Status field value of the record that is below the given record (the child record) can determine the following controls:
- The operations, such as create, update, and delete, that users can perform for the given record.
- The buttons that are enabled (or available for use) when users select the given record.
- The valid transitions of the Status field value for the given record.
Administrators can access state models to change preconfigured information relating to categories for Status field values, operation controls for benefit data, button controls for benefit data, and transition controls of Status field values for benefit data. For more information about changing state models, see Siebel Applications Administration Guide. The following state models are preconfigured in Siebel Public Sector:
- PUB Application Status (for benefits application records)
- HLS Case (for benefits case records)
- HLS Case - SM (for parent benefits case records)
- PUB Case Benefit Plan (for benefit plan records)
- PUB Case Benefit Plan Line Item (for benefit records)
- PUB Case Benefit Plan Payments (for benefit payment records)
- HLS Case Service Plan (for service plan records)
State models are not preconfigured in Siebel Public Sector for benefit orders, benefit attributes, goals, and activities. Categories for Status Field Values
Status field values for records that contain benefit data are associated with the following categories:
- Positive. The record will undergo further processing before it reaches the end of its life cycle (for example, an active benefits case or a pending benefit).
- Negative. The record has reached the end of its life cycle (for example, a closed benefits case or a completed benefit).
- Garbage. The record is currently inactive or was terminated before it reached the end of its life cycle (for example, an inactive benefits case or a cancelled benefit).
The categories of Status field values for records that contain benefit data are preconfigured in Siebel Public Sector. For each of these categories, Table 7 shows the Status field values for benefit data records. Benefit data records that are excluded from this table have no preconfigured categories of Status field values. Some of the records in this table can have Status field values that do not appear in the table. These Status field values (except for the Submitted value for a benefits case record) do not affect the operation controls for the records, the button controls for the records, and the transition controls for Status field values. Administrators can configure the information in this table by changing the Category Name field in the States view for each applicable state model in the State Models view of the Administration - Application screen. They can add new categories in the Categories view for each applicable state model in the State Models view of the Administration - Application screen.
Table 7. Status Field Values of Categories for Benefit Data Records
|
Status Field Values of Positive Category |
Status Field Values of Negative Category |
Status Field Values of Garbage Category |
Benefits Case |
Active and Rejected |
Closed |
Inactive |
Benefit Plan |
Active, Pending, and Approved |
Completed and Archived |
Inactive |
Benefit |
In Progress, Pending, and Approved |
Completed |
Inactive and Cancelled |
Benefit Payment |
Pending, Approved, Rejected, Request Failed, and Submitted-Pending |
Processed and Paid |
Inactive and Cancelled |
Service Plan |
Active, Pending, and Approved |
Completed and Archived |
Inactive |
Operation Controls for Benefit Data
The valid operations for records that contain benefit data are preconfigured in Siebel Public Sector. Operations, such as create, update, and delete are enabled (or available) only under certain conditions. Table 8 shows the conditions under which each operation is disabled (or unavailable) for benefit data records. Benefit data records that are excluded from this table have no preconfigured operation controls. To view the Status field values for categories, see Categories for Status Field Values. Administrators can configure the information in this table by changing the No Update and No Delete fields in the States view for each applicable state model in the State Models view of the Administration - Application screen and by changing the No Insert, No Update, and No Delete fields in the Child Operation Restriction applet in the States view. NOTE: Some of the conditions for the delete operation in this table (and additional conditions for the delete operation) are included in the Siebel Repository, and not in preconfigured hierarchical state models. These conditions are included in this table because they apply to the Status field values.
Table 8. Conditions to Disable Operations for Benefit Data Records
|
|
|
|
Benefits Applic. |
None. |
The Status field value of the benefits application is Cancelled or Processed. |
The Status field value of the benefits application is Processed. |
Benefits Case |
None. |
The Status field value of the original benefits case for an appeal case is not in the positive category. The Status field value of the benefits case is Submitted. |
The Status field value of the benefits case is in the positive or negative category. |
Benefit Plan |
The Status field value of the parent benefits case is not in the positive category. The Status field value of the parent benefits case is Submitted. |
The Status field value of the parent benefits case is not in the positive category. The Status field value of the benefit plan is in a garbage category. The Status field value of the parent benefits case is Submitted. |
The Status field value of the benefit plan is in the positive or negative category. The Status field value of the parent benefits case is Submitted. |
Benefit |
The Status field value of the parent benefit plan is not in the positive category. The Status field value of the grandparent benefits case is Submitted. |
The Status field value of the parent benefit plan is not in the positive category. The Status field value of the benefit is in a garbage category. The Status field value of the grandparent benefits case is Submitted. |
The Status field value of the benefit is in the positive or negative category. The Status field value of the grandparent benefits case is Submitted. |
Benefit Payment |
The Status field value of the parent benefit is not in the positive category. The Status field value of the great-grandparent benefits case is Submitted. |
The Status field value of the parent benefit is not in the positive category. The Status field value of the benefit payment is in a negative or garbage category. The Status field value of the great-grandparent benefits case is Submitted. |
The Status field value of the payment is in the positive or negative category. The Status field value of the great-grandparent benefits case is Submitted. |
Benefit Attribute |
The Status field value of the parent benefit is not in the positive category. The Status field value of the great-grandparent benefits case is Submitted. |
The Status field value of the parent benefit is not in the positive category. The Status field value of the great-grandparent benefits case is Submitted. |
The Status field value of the great-grandparent benefits case is Submitted. |
Service Plan |
The Status field value of the parent benefits case is not in the positive category. The Status field value of the parent benefits case is Submitted. |
The Status field value of the parent benefits case is not in the positive category. The Status field value of the service plan is in a garbage category. The Status field value of the parent benefits case is Submitted. |
The Status field value of the service plan is in the positive or negative category. The Status field value of the parent benefits case is Submitted. |
Goal |
The Status field value of the parent service plan is not in the positive category. The Status field value of the grandparent benefits case is Submitted. |
The Status field value of the parent service plan is not in the positive category. The Status field value of the grandparent benefits case is Submitted. |
The Status field value of the grandparent benefits case is Submitted. |
Activity |
The Status field value of the grandparent service plan is not in the positive category. The Status field value of the great-grandparent benefits case is Submitted. |
The Status field value of the grandparent service plan is not in the positive category. The Status field value of the great-grandparent benefits case is Submitted. |
The Status field value of the great-grandparent benefits case is Submitted. |
Button Controls for Benefit Data
Buttons in the user interface can control the operations that users perform for records that contain benefit data. These buttons are enabled (or available for use) only if a selected record (and sometimes a related record) has a designated Status field value. Table 9 shows the conditions under which these buttons are disabled (or unavailable for use) for benefit data records. Benefit data records that are excluded from this table have no preconfigured button controls. Administrators can disable these buttons by changing the No Invoke Method field in the States view for each applicable state model in the State Models view of the Administration - Application screen and by changing the No Invoke Method field in the Child Operation Restriction applet in the States view.
Table 9. Conditions to Disable Buttons for Benefit Data Records
|
|
|
Benefits Applic. |
Cancel Application |
The Status field value of the benefits application is Cancelled or Processed. This button appears on a self-service Web site for Siebel Public Sector eService. |
Benefits Case |
Scan Changes |
The Status field value of the benefits case is Closed, Inactive, or Submitted. |
Regenerate All |
The Status field value of the benefits case is Closed, Inactive, or Submitted. |
Appeal |
The Status field value of the benefits case is Inactive or Submitted. |
Submit |
The Status field value of the benefits case is Closed or Inactive. |
Recall |
The Status field value of the benefits case is Closed or Inactive. |
Benefit |
Create Order |
The Status field value of the benefit is Completed, Inactive, or Cancelled. The Status field value of the grandparent benefit case is Submitted. |
Cancel Order |
The Status field value of the benefit is Completed, Inactive, or Cancelled. The Status field value of the grandparent benefit case is Submitted. |
Benefit Payment |
Send Payment |
The Status field value of the payment is Processed, Paid, Inactive, or Cancelled. The Status field value of the parent benefit is Completed, Inactive, or Cancelled. The Status field value of the grandparent benefit case is Submitted. |
Activity |
Create Benefit |
The Status field value of the grandparent service plan is Completed, Archived, or Inactive. The Status field value of the great-grandparent benefit case is Submitted. |
Transition Controls of Status Field Values for Benefit Data
The valid transitions of Status field values for records that contain benefit data are preconfigured in Siebel Public Sector. The transitions of Status field values are enabled (or available) only under certain conditions. Table 10 shows the conditions under which each transition between categories is enabled for benefit data records. Benefit data records that are excluded from this table have no preconfigured transition controls. To view the Status field values for categories, see Categories for Status Field Values. Administrators can configure the information in this table by changing the Rule Expression field in the Transitions view for each applicable state model in the State Models view of the Administration - Application screen. Transitions to a positive category and transitions from a garbage category to a negative category are not included in the preconfigured Siebel Public Sector application.
Table 10. Conditions to Enable Transitions Between Categories for Benefit Data Records
|
Transition from Positive Category to Negative Category |
Transition from Positive or Negative Category to Garbage Category |
Benefits Case |
The Status field value of any child benefit plan or service plan is in the negative or garbage category. The Status field values of any appeal case for an original benefits case is in the negative or garbage category. |
The Status field value of any child benefit plan or service plan is in the garbage category. The status field values of any appeal case for an original benefits case is in the garbage category. |
Benefit Plan |
The Status field value of any child benefit is in the negative or garbage category. |
The Status field value of any child benefit is in the garbage category. |
Benefit |
The Status field value of any child benefit payment is in the negative or garbage category. The Status field value of any child benefit order is Closed, Inactive, or Cancelled, or any child benefit order has no order number. |
The Status field value of any child benefit payment is in the garbage category. The Status field value of any child benefit order is Inactive or Cancelled, or any child benefit order has no order number. |
Service Plan |
The Status field value of any child benefit is in the negative or garbage category. |
The Status field value of any child benefit is in the garbage category. |
|
