About Controls for Benefit Data
In Siebel Public Sector, the records that contain benefit data have a hierarchical relationship with each other. The following image shows this hierarchical relationship.
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 before the given record (the parent record and grandparent record), and the Status field value of the record that is after 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.