Spawning from Client Requirements

Spawn Client Activity if a Client Requirement is created or modified

Whenever a Client Requirement is created or modified, the current system behavior does not support the ability to spawn an activity on the Client. This enhancement, will allow this behavior and spawn an activity to the Client by the SpawnActivities business rule that is configured on the Client Requirement's <State> configuration.

The information below is an example of Requirement configuration that will execute the SpawnActivities business rule connected to the Requirement when it has a status value of '00'.

XML Example - Requirement Definition

<Requirement>
    <States>
        <State STATUS="00">
            <Math>
                <MathVariables>
                    <MathVariable VARIABLENAME="RequirementGuidMV" TYPE="FIELD" DATATYPE="TEXT">Requirement:RequirementGUID</MathVariable>
                    <MathVariable VARIABLENAME="RequirementNameMV" TYPE="FIELD" DATATYPE="TEXT">Requirement:RequirementName</MathVariable>
                    <MathVariable VARIABLENAME="RequirementStatusMV" TYPE="FIELD" DATATYPE="TEXT">Requirement:RequirementStatus</MathVariable>
                    <MathVariable VARIABLENAME="AllowDuplicatesMV" TYPE="FIELD" DATATYPE="TEXT">Requirement:AllowDuplicates</MathVariable>
                </MathVariables>
            </Math>
            <Rules>
                <Rule>SpawnActivities</Rule>
            </Rules>
        </State>
    </States>
</Requirement>