CaseScreen
This business rule allows a user to create and edit case records, part of the New Business Underwriting process. In OIPA, the Case screen is accessed by selecting Case from the unified search drop-down, then searching for and selecting an existing case.
Information displayed on this screen includes the case name, case number, case status, creation date and date last updated, all of which correspond to columns within the AsCase database table. Additionally, dynamic fields can be configured to display other information on the screen. A case's status is represented by a two digit role code, and these role codes are defined in the AsCodeCaseStatus code name.
The screen has three sections:
- The Case General Info section displays the screen's fixed fields, such as case name and number.
- The Policy/Application Table section displays the table defined in the <Table> tags within the <Policies> tags of the CaseScreen rule.
- The Case Detail section displays the dynamic, configurable fields defined in the CaseScreen rule's configuration. These fields' values are stored in the AsCaseField database table.
Masking and field-level security is supported on the Case screen.
| Element/Tag | Attribute | Definition |
|---|---|---|
|
<CaseScreen> |
|
Required element: The opening and closing tags of the CaseScreen business rule. |
| <Summary> | The opening and closing tags of the summary section of Case Summary | |
| <Fields> | Wrapper element of Field Element | |
| <Field> | <Fields> | Names the fields to be presented. |
| <Name> | Specifies the database column in which the field values are stored. | |
| <Display> |
BOLD ITALICS |
Optional: Renders bold or italicized representations of a dynamic field’s contents.
Yes: Field contents will be bold and/or italicized. No: Contents will not have bold or italicized content. |
| <Group> | <Field> |
Required element if configured under Summary Tag This is the name of the group (table) that should be used to obtain the value. This is used only where source data may come from multiple tables (i.e., search screens).
Case | CaseField | Math |
|
<Filter> |
Optional element: Allows to restrict access of privileged cases from selected security groups. |
|
|
<Conditions > |
Required |
|
|
SecurityGroup |
Required The security group on which the filtering should be applied. Multiple security groups can be added with coma separated values. |
|
|
Optional
|
Type Values: Exclusion Default: Exclusion |
|
|
Optional |
Operator Values: OR|AND Default: OR |
|
|
<Condition> |
Required |
|
|
Required The dynamic field name |
Fieldname |
|
|
Required The dynamic field value |
Value Field Value |
|
|
<FixedFields> |
Optional element: Standard <FixedFields> screen rule section. See Fixed Fields page. |
|
|
<Fields> |
Optional element: Standard <Fields> screen rule section. SeeFields Elements page. |
|
| <Events> |
Optional element: Standard <Events> screen rule section. See Actions/Events page. |
|
|
<Actions> |
Optional element: Standard <Actions> screen rule section. See Actions/Events page. |
|
|
<Roles> |
Required element: The container element for the sub-elements that define the roles on the application/policy. |
|
|
<CM> |
Required element: Defines the Case Manager role on the application/policy Two digit role code for Case Manager role |
|
| <UW> |
Required element: Defines the Underwriter role on the application/policy Two digit role code for Underwriter role |
|
| <Policies> |
Required element:
|
|
| <Table> |
Required element: Standard <Table> configuration. See Table Element page. |
|
| <DisableCaseFields> |
Optional element: Specifies when fields on the Case screen can or cannot be edited, based on case and application status. Disables case fields for the specified case and application statuses if the combination of case and application statuses code matches a code in the DisabledStatus section for a particular case. Note: When AutomaticCaseNumber generator is not used, CaseNumber field should be editable even after saving the policy that allows the entering and editing in that field until another case event. |
|
|
<DisabledCaseStatus> |
DISABLEDAPPLICATIONSTATUS
|
Required element: Indicates which combination of case status and application status codes would trigger the lock-down of editable fields. DisabledCaseStatus element shall be repeatable. DISABLEDAPPLICATIONSTATUS attribute shall be comma separated. This element defines Case and application status codes for the case fields that will be disabled on the case screen. In case the attribute DISABLEDAPPLICATIONSTATUS is not specified then the case fields shall be disabled for all the application statuses for a given case status.
Required element value: CaseStatusCode ApplicationStatusCode list Case and application Status Codes from AsCode=>AsCodeStatus |
| CONDITION |
CONDITION attribute can take only two values "ANY and "ALL". If this attribute is not specified or rwongly specified then the default value shall be considered as "ANY". This attribute indicates in case of multiple applications per case, whether the matching of application status of ANY application to any of the status codes specified in comma separated. DISABLEDAPPLICATIONSTATUS attribute constitute the sufficient condition for screen locking or matching of application status of ALL applications to any of the status codes specified in comma separated. DISABLEDAPPLICATIONSTATUS attribute constitute the sufficient condition for screen locking.
Example 1: If config is as below: <DisabledCaseStatus DISABLEDAPPLICATIONSTATUS ="01,02,95" CONDITION = "ANY">"01"</DisabledCaseStatus> means for case status = "01" if any of the applications belonging to the case has the application status among 01, 02 or 95 then the case screen shall be locked.
Example 2: If config is as below : <DisabledCaseStatus DISABLEDAPPLICATIONSTATUS ="01,02,95" CONDITION = "ALL">"01"</DisabledCaseStatus> means for case status = "01" if all of the applications belonging to the case has the application status among 01,02 or 95 then the case screen shall be locked. |
|
|
<AutomaticCaseNumber> |
Optional element: Allows generating automatic case number when a new case is created as per the format specified in AutomaticCaseNumber business rule. Yes: Allows generating automatic case number when new case is created. Optional: If a number is entered, then the value will be considered and recorded. If it is not entered, then the system will automatically generate a case number. No: Automatic case number will not be generated when new case is created and allows the user to enter the case number in the CaseNumber field. If this element is not present default is "No". |
XML Schema
<CaseScreen>
<Summary>
<Fields>
<Field>
<Name></Name>
<Display></Display>
<Group> Math | Literal</Group>
</Field>
..
..
</Fields>
</Summary>
<Fields>
<Field>
<Name></Name>
<Display></Display>
<DataType></DataType>
<Disabled>[Yes|No]</Disabled>
</Field>
</Fields>
<Events>
<Event TYPE="">
<ActionSet ID=""></ActionSet>
</Event>
</Events>
<Roles>
<CM></CM>
<UW></UW>
</Roles>
<Actions>
<ActionSet ID="">
<Condition IF="">
<Action ACTIONTYPE="">String</Action>
</Condition>
</ActionSet>
</Actions>
<Policies>
<Table>
<Column WIDTH="" ALIGN="[Left|Center|Right]">
<Name></Name>
<Display></Display>
<Group></Group>
<DataType></DataType>
</Column>
</Table>
</Policies>
<AutomaticCaseNumber>[Yes|No|Optional]</AutomaticCaseNumber>
<DisableCaseFields>
<DisabledCaseStatus DISABLEDAPPLICATIONSTATUS = "[DISABLEDAPPLICATIONSTATUSList]" CONDITION = "[ANY/ALL]">"[DisabledCaseStatus]"</DisabledCaseStatus>
</DisableCaseFields>
</CaseScreen>
XML Example
<CaseScreen>
<Summary>
<Fields>
<Field>
<Name>CaseDetails</Name>
<Display>Case Description</Display>
<Group>CaseField</Group>
</Field>
<Field>
<Name>CreationDate</Name>
<Display>Creation Date</Display>
<Group>CaseField</Group>
</Field>
</Fields>
</Summary>
<Fields>
<Field>
<Name>CaseDetails</Name>
<Display>Case Description</Display>
<DataType>Text</DataType>
<Disabled>[Yes|No]</Disabled>
</Field>
<Field>
<Name>CreationDate</Name>
<Display>Creation Date</Display>
<DataType>Date</DataType>
<Disabled>Yes</Disabled>
</Field>
</Fields>
<Events>
<Event TYPE="ONSUBMIT">
<ActionSet ID="FinalValidation"></ActionSet>
</Event>
</Events>
<Roles>
<Role DISABLEBYPOLICYSTATUS="01,02,95">
<RoleCode>01</RoleCode>
<RoleCount>1</RoleCount>
<RolePercent>100</RolePercent>
</Role>
<Role>
<RoleCode>37</RoleCode>
<RoleCount>1</RoleCount>
<RolePercent>100</RolePercent>
</Role>
</Roles>
<Actions>
<ActionSet ID="FinalValidation">
<Condition IF="IsEmpty(CaseText)">
<Action ACTIONTYPE="ERROR">Case Description can not be empty.</Action>
</Condition>
</ActionSet>
</Actions>
<Policies>
<Table>
<Column WIDTH="100" ALIGN="LEFT">
<Name>PolicyNumber</Name>
<Display>Application Number</Display>
<Group>Policy</Group>
<DataType>Text</DataType>
</Column>
<Column WIDTH="75" ALIGN="LEFT">
<Name>IssueStateCode</Name>
<Display>Issue State</Display>
<Group>Policy</Group>
<DataType>Text</DataType>
</Column>
<Column WIDTH="75" ALIGN="LEFT">
<Name>StatusCode</Name>
<Display>Status</Display>
<Group>Policy</Group>
<DataType>Text</DataType>
</Column>
<Column WIDTH="75" ALIGN="LEFT">
<Name>FirstName</Name>
<Display>Insured First Name</Display>
<Group ROLECODE="37">Client</Group>
<DataType>Text</DataType>
</Column>
<Column WIDTH="75" ALIGN="LEFT">
<Name>LastName</Name>
<Display>Insured Last Name</Display>
<Group ROLECODE="37">Client</Group>
<DataType>Text</DataType>
</Column>
</Table>
</Policies>
<AutomaticCaseNumber>No</AutomaticCaseNumber>
<DisableCaseFields>
<DisabledCaseStatus DISABLEDAPPLICATIONSTATUS ="01,02,95" CONDITION = "ANY">"01"</DisabledCaseStatus>
</DisableCaseFields>
</CaseScreen>
Example for Restricting Access of Privileged Cases using Filters
<CaseScreen>
<Filter>
<Conditions SecurityGroup = "Prototype Super,AlamereTest" Type ="Exclusion" Operator ="OR|AND">
<Condition Fieldname ="PrivilegedField1" Value = "X"></Condition>
<Condition Fieldname ="PrivilegedField2" Value = "Y"></Condition>
</Conditions>
</Filter>
</CaseScreen>
