PlanScreen

This rule enables the user to define plan specific data and allows other business rules to reference the data.  This rule defines the elements and values of the Plan screen business rule.   

PlanScreen Elements/Attributes
Element/Tag Definition Attribute Element/Attribute Value and Description

<PlanScreen>

The opening and closing tag of the business rule.

 

 

<Spawns> Start and end tag for the Spawns section    

<Spawn>

 

Required Element

Opening element containing a transaction to spawn based an entity action.

Note: The IF attribute which is available as part of the Spawn tag will not be available in this BR and will be ignored if used. Asides from that the typical spawn section with one Transaction element can be configured here. Please refer Spawns_ Element Section for more details

 

<Transaction>

 

Required element:

Identifies the transaction that should be spawned.

The transaction must be available from the entity’s context. A transaction’s name.
 

SPAWNCODE

.

Required element:

As defined by codename in AsCodeSpawn in AsCode table. Determines effective date of spawned transaction.

Applicable code is "03"

Note: Other spawn codes not supported

  FIELD

Required element:

Variable defining the EffectiveDate of the spawn

Field variable containing a date value
  PROCESSIMMEDIATE

Optional element:

A literal value or math variable that resolves to “Yes” or “No”.

If the value is “Yes”, the Activity object is inserted and executed immediately. If the value is “No”, the Activity object is inserted and but not executed.

The default value is “No”.

<SpawnFields>  

Required element:

Opening element that contains the list of fields from the spawned activity that will be populated with a value

 
<SpawnField>  

Required element:

Opening element for a single field from the spawned activity that will be populated.

Field Variable
<From>  

Required element:

The value to pass to spawned field.

Transaction’s field name.
<To>  

Required element:

The field from the spawned activity to populate

 
<DataType>  

Required element:

Provides the data type for the spawned field

Date Decimal Integer Money Text

<UseStateApproval>

Optional:   

Indicates whether state approval is enforced in the user interface during creation of a policy. If state approval is being enforced, the Issue State drop-down list in the PolicyScreen of OIPA is modified. The list will show only states where the Plan date is after the state approval date and before the state approval expiration date.

 

Required Element Value: Yes/No

Yes - State approval is enforced on the PolicyScreen.

No - State approval is not enforced on the PolicyScreen. This is the default value.

<Fields>

Required:   

Allows configuration of the dynamic field(s), which define the contents of the Plan screen. Field element is repeatable.
 

 

 

<Field>

See Fields Element.

 

 

<FixedFields> The opening and closing tag of the Fixed Fields section.    
<Field> The opening and closing tag for each Fixed Field being configured.    
<Display> Provides the label text that will display on the screen.   See the Fields Elements.
<DataType> DataType of the field.   See the Fields Elements.
<Expanded>     See the Fields Elements.
<Query>     See the Fields Elements.
<Hidden> Indicates if fixed field should be hidden.   See the Fields Elements.
<Disabled> Indicates if fixed field should be visible, but no entry is allowed.   See the Fields Elements.
<Required> Indicates if the field is a required field for entry.   See the Fields Elements.
<Events> The opening and closing tag for the element.    
<Event> Repeatable: Identifies the event that is being defined. TYPE

ONLOAD

ONCHANGE

ONSUBMIT

    FIELD

Any field name in the <Fields> section.

Used with ONCHANGE to identify the trigger field, which when it changes, causes the actions to process. ActivitySuspenseNumber literal value in addition to existing values.

<ScreenMath> Opening and closing tags for Event Math section.    
<Math> Call the <Math> that is defined in the <ScreenMath> section to run the names that matches the ID. ID

Any ID name given in the Math section under <ScreenMath>.

ActivitySuspenseNumber literal value in addition to the existing values

<MathVariables>      
<Actions>      
<QuerySet> Defines QuerySet. ID Any name (without spaces).
<Condition> Optional conditional logic. IF

Any expression resulting in a true or false value.

When the expression results in a true value, the system passes execution to the first statement contained by the opening and closing tags of the parent element. Statement execution continues serially to the next statements until the closing parent tag, or an Else/ElseIf element is reached.

When the expression results in a false value, the system passes execution control to Else/ElseIf element or closing parent tag, whichever is closest.

Functions and direct date comparisons are available for use in the expression.

Screen math variables and fields are available for use in the expression.

    VALUE String
<Action> Defines whether to fill combo box with SQL query, or to use fixed options.   String: SQL query string.
    ACTIONTYPE

SQL QUERY

MATHCOLLECTION: References a screen math variable containing a collection. If this value is used, the value of the <Action> element should be a COLLECTION math variable defined in screen math.

HIDE

SHOW

ENABLE

ASSIGN

<ElseIf>

ElseIf is executed when prior conditions in IF and ElseIf elements are not true. Use this element when there are further conditions to express in the condition structure.

IF attribute must be included.

Multiple ElseIf elements are possible within a condition structure.

IF

Any expression resulting in a true or false value.

When the expression results in a true value, the system passes execution to the first statement contained by the opening and closing tags of the parent element. Statement execution continues serially to the next statements until the closing parent tag, or an Else/ElseIf element is reached.

When the expression results in a false value, the system passes execution control to Else/ElseIf element or closing parent tag, whichever is closest.

Functions and direct date comparisons are available for use in the expression.

Screen math variables and fields are available for use in the expression.

    VALUE String
<Else>

Else is executed when prior conditions in IF and ElseIf elements are not true.

Use this element when there are no further conditions to express in the condition structure.

Only one Else is possible within a condition structure.

  Execution is passed to the first Action statement contained within the opening and closing <Else> element. Each statement is serially executed until the closing tag is reached.
<ActionSet> Defines ActionSet ID Any name (without spaces).
<Condition> Same as defined above.    
<Action> Defines the type of action that is to occur.  

Optional element value:

String: Message to be displayed if ACTIONTYPE is ERROR or WARNING, and the IF condition is met.

    FIELD The field name where the action is to occur. This attribute is required when action type is equal to assign. It is also available when action type is equal to error or warning.
    ACTIONTYPE

ERROR

Provides a message to the user. The user cannot proceed until the all errors are fixed. All errors will display in one section of the screen (if more than one occurs).

When FIELD is used, the error will appear in the Validation section at the top of the screen.

Note: The value of a Math Variable or a Segment Field can be substituted in the error message surrounded by $$$.

     

WARNING

Provides a warning message to the user. This is a warning to the user and the user may proceed even with the error messages. All errors will display in one section of the screen (if more than one occurs).

When FIELD is used, the warning will appear in the Validation section at the top of the screen.

Note: The value of a Math Variable or a Segment Field can be substituted in the warning message surrounded by $$$.

     

SHOW

Will make hidden field visible.

     

HIDE

Will hide a visible field.

     

ENABLE

Allows data entry in an editable field.

     

DISABLE

Prohibits data entry in an editable field, and changes the background color.

     

READONLY

Prohibits data entry in a field and does not change background color.

     

ASSIGN

Allows a value to be set to the field defined in the FIELD attribute. This action does not trigger an OnChange event on the receiving field.

<ElseIf> Same as defined above.    

XML Example

<PlanScreen>
<UseStateApproval>Yes</UseStateApproval>
<Fields>
<Field>
<Name>ProductCode</Name>
<Display>Product Code</Display>
<DataType>Text</DataType>
</Field>
<Field>
<Name>MaximumIssueAge</Name>
<Display>Max Issue Age</Display>
<DataType>Integer</DataType>
</Field>
<Field>
<Name>MinimumFaceAmount</Name>
<Display>Min Face Amount</Display>
<DataType>Money</DataType>
</Field>
</Fields>
<Spawns>
<Spawn>
<Transaction SPAWNCODE="03" FIELD="DateField" PROCESSIMMEDIATE="Yes|No">ScreenUpdateTransactionName</Transaction>
<SpawnFields>
<SpawnField>
<From>Name</From>
<To>ActivityFieldName</To>
<DataType>Type</DataType>
</SpawnField>
</SpawnFields>
</Spawn>
</Spawns>
<FixedFields>
<Field>
<Name>AllocationMethod</Name>
<Hidden>Yes</Hidden>
</Field>
</FixedFields>
<Fields>
<Field>
<Name>PlanNumber</Name>
<Display>Plan Number</Display>
<DataType>Text</DataType>
</Field>
</Fields>
</PlanScreen>

 

 

 

 

 

Oracle Insurance Logo Copyright © 2017, Oracle and/or its affiliates. All rights reserved. About Oracle Insurance | Contact Us