PolicyScreen
Policy screen is the foundation of an insurance contract. It
is a main screen of
This business rule is used to configure the fixed fields of the Policy screen in order to:
- Capture the basic information required for the policy like effective date, issue date, issue state, policy number, etc.
- Perform policy level allocations.
- Define roles, role counts, role percents and client types for roles that are required for a policy.
- Define segment requirements.
- Enable/Disable policy field and state approvals.
This business rule is used to configure the fixed fields of the Application screen in order to:
- Capture basic application information, such as active date, issue date, issue state, application number, etc.
- Add requirements to the application.
- Add impairments to the application.
Policy summary section is added to the Policy Overview Screen to make it consistent with other policy related pages and compatible with prior versions. Now policy summary is displayed with all of the fixed fields presented in the same order and format as they present on the PolicyScreen. This is the default presentation of the policy summary for all policy related pages except the PolicyScreen which retains the current fixed field and dynamic field presentations alone and no summary. In addition, configurability for policy summary will be added so each customer may specify the fixed fields and presentation order they wish.
PolicyScreen Elements/Attributes
Element/Tag | Attribute | Definition | Element/Attribute Value and Description |
---|---|---|---|
<PolicyScreen> |
|
The opening and closing tag of the business rule. |
|
<AllowPlanDateModifications> |
Optional element: This element defines whether the PlanDate field is disabled after the policy is saved for the first time, or if it enabled/disabled based on the value of the <DisablePolicyFields> element. |
Yes/No
Yes - The PlanDate field will be enabled/disabled based on the policy's status and the value of the <DisablePolicyFields> element. No - The PlanDate field will be disabled when the policy is saved for the first time. Note: If set to "Yes," the Plan Date entered by the user will be validated based on two conditions: If <UseStateApproval> is set to "Yes" in the PlanScreen business rule, the Plan will be valid in the selected Issue state provided the PlanDate is between the EffectiveDate and ExpirationDate saved in the AsPlanStateApproval table. If state approvals are applicable at the segment level, and the <SegmentName> element's APPROVALDATE attribute is set to "PlanDate" on the corresponding SegmentScreen rule, the Plan will be valid in the selected Issue state provided the PlanDate is between the EffectiveDate and ExpirationDate saved in the AsSegmentStateApproval table. If the PlanDate entered by the user is invalid based on any of the conditions above, an error message will be displayed, and the PlanDate field will be reset to its previous value. |
|
<FixedFields> |
|
Optional element: This element allows the fixed fields to have the same configuration capabilities as dynamic ( below the line ) fields: the only exception being the ability to change the fixed field data types.
Note:Only Issue State fixed field display can be changed. |
|
<Fields> |
|
Required element:
See Fields. Note:Icons for PolicySearchScreen and ClientSearchScreen can be configured in the PolicyScreen by using the client datatype, which will be displayed as disabled text boxes with search and people icons, respectively. Searching returns the respective GUIDs. |
|
<PolicySummary> | Optional: Allows a customized definition of the Policy Summary that appears at the top of all policy related pages except the Policy Screen. Default behavior when the element is not configured is to present all policy fixed fields in the same order and format as they display on the Policy Screen. | ||
<FixedFieldName> | Required: Names the fixed field to present. Filler may also be presented. | Optional: Indicates whether the field will occupy an entire line on the screen | |
</PolicySummary> | |||
<MultiFields> |
Optional element; Allows configuration of MultiFields in the PolicyScreen See MultiFields element for additional information. |
MultiFields enables and allows Policy Screen with multiple sets of dynamic field values. |
|
<Buttons> |
|
Required element:
|
|
<Button> |
|
Optional element:
|
Required Element value: Allocate |
<Events> |
|
See Action Events |
|
<ScreenMath> |
See ScreenMath Element. | ||
<Actions> |
See Action Events |
||
<SegmentsAllowed> |
|
Optional element:
|
Required element value: Note:The star * symbol indicates that unlimited number of segments can be allowed for a policy. |
<MinimumSegments> |
|
Optional element:
|
Optional element value: Integer
|
|
Optional element:
Note: When AutomaticPolicyNumber generator is not used, PolicyNumber field should be editable even after saving the policy that allows the entering and editing in that field until another policy event (calculating a coverage, issue of the policy). |
|
|
<DisabledStatus> |
|
Required element:
|
Required element
value: |
<SegmentCount> |
|
Optional element:
|
Optional element value: * / + " * ": Disables policy fields in all
conditions.
" + ": Disables policy fields when policy has at least a minimum of one segment in active status. |
<AutomaticPolicyNumber> |
|
Optional element:
|
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 policy number. No:Automatic policy number will not be generated
when new policy is created and allows the user to enter
the policy number in the PolicyNumber field. If this
element is not present default is "No".
|
<Roles> |
|
Opening tag for defining roles on the policy. |
|
<Role> |
|
Required and repeatable
element:
This element defines the description of the role that will be added to the policy. |
Note:
|
NAME |
Optional
attribute: |
||
DISABLEBYPOLICYSTATUS |
Optional attribute:
Used to prevent disabled roles from being disabled. It is also used to disable role fields, role percents and prevent disabled fields from being added to a policy. |
||
ALLOWREQUIREMENTS | Controls whether the Requirements tab, which allows the user to add Requirements on the Requirement Detail screen, is enabled on the Policy/Application screen. |
Optional attribute: Yes: The Requirements tab will display. No: The Requirements tab will not display. |
|
<RoleCode> |
|
Required element:
|
Required element
value: |
<RoleCount> |
|
Optional element:
|
Required element
value: |
<RolePercent> |
|
Required element:
|
Required element value:0-100 or * An asterisk can be used to indicate that the total percent for the associated role can exceed 100%. Each individual record will still have a maximum of 100%, but the total for multiple records on the same Policy Role will be able to exceed 100%. |
<ClientType> |
|
Optional element:
Example:An insured may need to be an individual client type for a particular plan. |
Required element
value: |
<Tests> |
|
Optional Element:
|
|
<Test> |
Required/Repeatable
Element:
|
Expression:
|
|
TYPE |
Optional attribute (="Expression") To indicate the type of the condition. Example: <Test TYPE="Expression"> |
||
<AllowZeroPercent> |
|
Optional element: Allows Zero percent in Role percent fields. |
Required element value: Yes/No Yes:Allows user to enter zero percent in the Rolepercent field. No:When set to "No" then Zero Percent is not allowed. Note:If this element is not present then the default is "Yes". |
<AllowPercent> |
|
Optional element: Controls the display of the Percent box next to the names of individuals that have been assigned to the specified role. |
Required element value: Yes/No Yes:When set to "Yes" the Percentage box is displayed next to the name of the individual that has been assigned to the specified role. No:Percentage box is not displayed next to the name of individuals that have been assigned to the specified role. Note: If this tag is not present default is "Yes". |
XML Example
<PolicyScreen>
<AllowPlanDateModifications>Yes</AllowPlanDateModifications>
<Fields>
<Field>
<Name>SortCompany</Name>
<Display>Company</Display>
<DataType>Combo</DataType>
<Query TYPE="SQL">SELECT FundClassGUID, FundClassName FROM AsFundClass ORDER BY 2 DESC</Query>
<Disabled>Yes</Disabled>
</Field>
<Field>
<Name>ActiveDate</Name>
<Display>Date Activated</Display>
<DataType>Date</DataType>
<Disabled>Readonly</Disabled>
</Field>
<Field>
<Name>Carrier</Name>
<Display>Carrier Company Name</Display>
<DataType>Combo</DataType> <Query TYPE="SQL">SELECT ClientGuid, CompanyName FROM AsClient WHERE TypeCode = '19'</Query>
</Field>
</Fields>
<Buttons>
<Button>Save</Button>
<Button>New</Button>
<Button>Close</Button>
</Buttons>
<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>
<SegmentsAllowed>4</SegmentsAllowed>
<MinimumSegments>1</MinimumSegments>
<AutomaticPolicyNumber>Yes</AutomaticPolicyNumber>
</PolicyScreen>
XML Schema
<PolicyScreen>
<AllowPlanDateModifications>[Yes|No]</AllowPlanDateModifications>
<FixedFields>Please refer to "Fixed Fields" </FixedFields>
<Fields>Please refer to "Fields" .</Fields>
<MultiFields RULE="[RuleName]">"[Yes|No]"</MultiFields>
<Buttons>
<Button>
"[Allocate|Activity|Values|Withholding|PolicyOverview]"</Button>
</Buttons>
<Events>Please refer to "Events"</Events>
<ScreenMath>
<Math>Please refer to "Math"</Math>
</ScreenMath>
<Actions>Please refer to "Actions"</Actions>
<Roles>
<Role NAME="[RoleName]" DISABLEBYPOLICYSTATUS="[DisableByPolicyStatusList]" EXTERNAL="[Yes|No]"
ALLOWREQUIREMENTS="[Yes|No]">
<ExternalClientRowRetriever>[client search class loader]</ExternalClientRowRetriever>
<AllowZeroPercent>"[Yes|No]"</AllowZeroPercent>
<AllowPercent>"[Yes|No]"</AllowPercent>
<RoleCode>"[RoleCode1,RoleCode2]"</RoleCode>
<RoleCount>"[Integer|*]"</RoleCount>
<RolePercent>"[0-100|*]"</RolePercent>
<ClientType>"[ClientTypeList]"</ClientType>
<Tests>
<Test>"[Condition]"</Test>
</Tests>
<CustomScreen>[custom screen display class]</CustomScreen>
</Role>
</Roles>
<AutomaticPolicyNumber>"[Yes|Optional|No]"</AutomaticPolicyNumber>
<DisablePolicyFields>
<DisabledStatus>"[DisabledStatusList]"</DisabledStatus>
<SegmentCount>"[*|+]"</SegmentCount>
</DisablePolicyFields>
<MinimumSegments>"[Integer]"</MinimumSegments>
<SegmentsAllowed>"[Integer|*]"</SegmentsAllowed>
<ShadowPolicy>
<AllowShadowButton>
<StatusCode>"[ShadowPolicyStatusCodeList]"</StatusCode>
</AllowShadowButton>
<ShadowStatusCode>"[PolicyShadowStatusCode]"</ShadowStatusCode>
</ShadowPolicy>
</PolicyScreen>