Oracle® Insurance XML Configuration Guide Release 10.2.0.0 E62439-01
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.
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. |
<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>
Copyright © 2009, 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices