GeneratePendingRequirements

GeneratePendingRequirements defines the comparisons of requirement criteria to MathVariable values. If all conditions identified in the rule are true, then the requirement is generated. This rule must be used in conjunction with DeliveryRequirements and TransactionBusinessRulePacket.

GeneratePendingRequirements Elements/Attributes
Element Attribute Definition Element/Attribute Value

<GeneratePendingRequirements>

 

The opening and closing tags of the business rule.

 

LEVEL

Indicates the type of requirement to create. that can be defined is Activity-Level to generate pending requirements.

Activity - Indicates name of the level (Activity-Level) to generate pending requirements.

 

<PendingRequirement>

 

The opening and closing tag of the section.

 
TYPE  

Code: As defined in AsCodeActivityType table.

<RequirementName>

 

Required element:

Defines the value of the field for variables required to match database requirements in AsRequirementDefinition table.

String- Defines the MathVariable from the transaction that defines the Rate Description nameRequirement Name from the AsRequirementDefinition table.

NAME Required attribute:

String: Defines the name of Rate Description from the MathVariable VALUE. Name of the Rate Description from the AsRequirementDefinition table.

<Criteria>

 

 

 

 

Optional element:

Defines the value of the field listing the criteria sequence required to match AsRequirementDefinitionCriteria database table.

String - Identifies the MathVariable whose value will be compared to the named Criteria’s value.

NAME

Required attribute:

Name of the criteria element to compare.

CriteriaName from AsRequirementCriteria.

OPERATOR

Optional attribute:  

Equal (default if not defined)

NotEqual

GreaterThan

GreaterThanOrEqual

LessThan

LessThanOrEqual

If blank, assume operation is “equal”

DATATYPE

Data Type for the criteria to compare

DATE

TEXT

INTEGER

DECIMAL

<Fields>

 

See Fields Elements.

 

<Field>

 

 

 

<From>

 

Named MathVariable

 

<To>

 

Target Field Name

 

<WorkflowTask>   Optional: This element identifies the workflow task that is generated when the workflow feature is "turned on" (system property) and the requirement is generated. Values: Workflow task name

XML Schema

GeneratePendingRequirements LEVEL="Activity">
<PendingRequirement TYPE="[code value]">
<RequirementName>[math variable]</RequirementName>
<WorkflowTask>[workflow task name]</WorkflowTask>
<Criteria NAME="[criteria name]" OPERATOR="[Equal | NotEqual | GreaterThan | GreaterThanOrEqual | LessThan | LessThanOrEqual]" DATATYPE="[DATE | TEXT | INTEGER | DECIMAL]">[math variable]</Criteria>
<Fields>
<Field>
<From>[math variable]</From>
<To>[field name]</To>
</Field>
</Fields>
</PendingRequirement>
</GeneratePendingRequirements>

XML Example

 <GeneratePendingRequirements LEVEL="Activity">
<PendingRequirement>
<RequirementName>CoSigner</RequirementName>
<!-- IF SIGNED DATE IS PRIOR TO 03/01/2010 AND CoSign is UNCHECKED, THEN GENERATE REQUIREMENT-->
<Criteria NAME="SignedDate" OPERATOR="LessThan" DATATYPE="DATE">SignedDateMV</Criteria>
<Criteria NAME="CoSign" DATATYPE="TEXT">CoSignMV</Criteria>
<Criteria NAME="PlanGUID" DATATYPE="TEXT">PlanGUIDMV</Criteria>
<Fields>
<Field>
<From>SignedDateMV</From>
<To>SignedDate</To>
</Field>
<Field>
<From>CoSignMV</From>
<To>CoSign</To>
</Field>
</Fields>
</PendingRequirement>
</GeneratePendingRequirements>

 

 

 

 

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