SpawnActivities

The SpawnActivities business rule is attached to Policy, Client or Policy-Client level Requirements. The rule generates activities to the entity to which the Requirement is associated. Policy-Client level activities will generate to the associated Policy. Generated activities are not processed by this rule. Instead, the activities are processed by the next batch cycle or user manual processing through the OIPA UI on the Activity Screens.

The SpawnActivities business rule processes during the execution of the <Rule> element defined in the Requirement's Definition rule.

SpawnActivities: Elements and Attributes
Element Attribute Parent Element Description Element / Attribute Values
<SpawnActivities>     This is the root element for the rule.  
<Spawn>    

Required, Repeatable:

This element's structure defines an Activity to generate and the population of their field data.  Conditions can be evaluated to conditionally generate the Activity.  This element is repeated to generate multiple Activities.

  
<Tests>    

Optional:

This element expresses one or more conditions that, when evaluating to true, will allow the remainder of the parent element's configuration to process.

  
<Test>    

Required, Repeatable:

This element provides a condition for the system to evaluate.  The element is repeated to express more than one condition.  All conditions must evaluate to true to allow the remainder of the parent element's configuration to process.

  • condition

    • Requirement fields and math variables are available to construct a condition
<Transaction>    

Required:

This element provides the name of the Transaction from which an Activity will be generated.

  • transaction name
  SPAWNCODE  

Required:

This attribute provides a valid spawn code from AsCodeSpawn.  This determines if the generated Activity is spawned for the system date or for another date.

  • 01

    • Activity is generated for the system date

  • 03

    • Activity is generated for the date provided by the

    • FIELD attributeFIELD attribute becomes mandatory
  FIELD  

Optional:

This attribute provides a value of the generated Activity's EffectiveDate when the SPAWNCODE attribute has a value of '03'.  It becomes a mandatory attribute with that spawn code.

  • math variable

  • Requirement field
<Fields>    

Required:

This element's structure identifies one or more fields to generate and the data source of their initial values.

  
<Field>    

Required, Repeatable:

This element defines a single field to generate and the data source of its initial value.  This element is repeated to generate multiple fields.

  
<From>    

Required:

This element provides a single value to the generated field. 

  • math variable

  • requirement field
<To>    

Required:

This element provides the field name to generate.

  •  field name
<OptionText>    

Optional:

This element provides a single value for the field's option text.  This applies to combo and radio fields only.

The value of a combo and radio field is not the same as its visible text.  Option text provides the visible text associated to this field's value.

  • math variable

  • requirement field

XML Schema

<!-- required spawn -->
<SpawnActivities>
    <Spawn>
        <Transaction SPAWNCODE="01">[transaction name]</Transaction>
        <Fields>
            <Field>
                <From>[variable | requirement field]</From>
                <To>[field name]</To>
                <OptionText>[variable | requirement field]</OptionText>
            </Field>
            <Field>...</Field>
        </Fields>
    </Spawn>
    <Spawn>
        <Transaction SPAWNCODE="03" FIELD="[variable | requirement field]">[transaction name]</Transaction>
        <Fields>
            <Field>
                <From>[variable | requirement field]</From>
                <To>[field name]</To>
                <OptionText>[variable | requirement field]</OptionText>
            </Field>
            <Field>...</Field>
        </Fields>
    </Spawn>
    <Spawn>...</Spawn>
</SpawnActivities>
 
<!-- conditional spawn -->
<SpawnActivities>
    <Spawn>
        <Tests>
            <Test>[condition]</Test>
            <Test>...</Test>
        </Tests>
        <Transaction SPAWNCODE="01">[transaction name]</Transaction>
        <Fields>
            <Field>
                <From>[variable | requirement field]</From>
                <To>[field name]</To>
                <OptionText>[variable | requirement field]</OptionText>
            </Field>
            <Field>...</Field>
        </Fields>
    </Spawn>
    <Spawn>
        <Tests>
            <Test>[condition]</Test>
            <Test>...</Test>
        </Tests>
        <Transaction SPAWNCODE="03" FIELD="[variable | requirement field]">[transaction name]</Transaction>
        <Fields>
            <Field>
                <From>[variable | requirement field]</From>
                <To>[field name]</To>
                <OptionText>[variable | requirement field]</OptionText>
            </Field>
            <Field>...</Field>
        </Fields>
    </Spawn>
    <Spawn>...</Spawn>
</SpawnActivities>

XML Example

<SpawnActivities>
    <Spawn>
        <Transaction SPAWNCODE="01">ReinsuranceAcceptance</Transaction>
        <Fields>
            <Field>
                <From>ActivityDate</From>
                <To>EffectiveDate</To>
            </Field>
            <Field>
                <From>ReinsurerMV</From>
                <To>CompanyName</To>
            </Field>
        </Fields>
    </Spawn>
</SpawnActivities>