You are here: Business Rules > Attached Rules > ShadowPendingActivites

Oracle® Insurance XML Configuration Guide Release 9.4.0.0 E18894_01

# ShadowPendingActivities

## Description

This business rule is used to delete an activity from the Activity screen when the specified condition is satisfied. More than one activity can be deleted, but the activity must be in pending status. The activity will appear shadowed once processed. OIPA will give an error if the user tries to delete an activity that is not in pending status.

ShadowPendingActivities Element/Attribute Table
Element/Tag | Definition | Attribute | Element/Attribute Value and Description
--- | --- | --- | ---
<ShadowPendingActivities> | The opening and closing tag for each ShadowPendingActivity element when more than one exists. |  |
<ShadowPendingActivity> | Repeatable element. This element is used only when there is a requirement to delete more than one activity. In such cases, each activity should be defined within its own individual <ShadowPendingActivity> element. |  |
<Tests> | Allows configuration of test(s) to see if the section of rule should be invoked. In this business rule, a condition is defined to determine whether an activity should be deleted. |  |
<Test> | This element is used to specify the condition. If this condition is satisfied, the specified activity will be deleted from the policy. |  | Expression: Specify a condition.
|  | TYPE | Expression: Indicate the type of condition. Expression is the only literal value used for this attribute.
<Activities> | This is the opening tag for the activities that should be shadowed in the Activity screen. |  |
<Activity> | Repeatable element. |  | SQL: SQL statement to determine the activity that needs to be deleted.

## XML Example

    <ShadowPendingActivities>

    <ShadowPendingActivity>

    <Tests>

    <Test TYPE="Expression">BillExists &gt; 0 AND BillAmount = 0</Test>

    </Tests>

    <Activities>

    <Activity>

    <SqlServer>SELECT
     TOP 1 AsActivity.ActivityGUID, AsActivity.StatusCode, AsActivity.ClientNumber
     FROM AsActivity JOIN AsTransaction ON AsTransaction.TransactionGUID =
     AsActivity.TransactionGUID WHERE PolicyGUID='[Policy:PolicyGUID]' AND
     TransactionName IN ('Billing','BillingStart') AND AsActivity.TypeCode
     IN ('01','04') AND AsActivity.StatusCode IN ('01','14', '02') AND AsActivity.EffectiveDate
     &gt;= '[Activity:EffectiveDate]' ORDER BY AsActivity.EffectiveDate
     ASC</SqlServer>

    <Oracle>SELECT
     AsActivity.ActivityGUID, AsActivity.StatusCode, AsActivity.ClientNumber
     FROM AsActivity JOIN AsTransaction ON AsTransaction.TransactionGUID =
     AsActivity.TransactionGUID WHERE ROWNUM = 1 AND PolicyGUID='[Policy:PolicyGUID]'
     AND TransactionName IN ('Billing','BillingStart') AND AsActivity.TypeCode
     IN ('01','04') AND AsActivity.StatusCode IN ('01','14', '02') AND AsActivity.EffectiveDate
     &gt;= '[Activity:EffectiveDate]' ORDER BY AsActivity.EffectiveDate
     ASC</Oracle>

    <DB2>SELECT AsActivity.ActivityGUID,
     AsActivity.StatusCode, AsActivity.ClientNumber FROM AsActivity JOIN AsTransaction
     ON AsTransaction.TransactionGUID = AsActivity.TransactionGUID WHERE PolicyGUID
     = '[Policy:PolicyGUID]' AND TransactionName IN ('Billing','BillingStart')
     AND AsActivity.TypeCode IN ( '01' , '04' ) AND AsActivity.StatusCode IN
     ( '01' , '14' , '02' ) AND AsActivity.EffectiveDate &gt;= '[Activity:EffectiveDate]'
     ORDER BY AsActivity.EffectiveDate ASC FETCH FIRST 1 ROWS ONLY</DB2>

    </Activity>

    </Activities>

    </ShadowPendingActivity>

    </ShadowPendingActivities>

## Schema Example

    <ShadowPendingActivities>

    <ShadowPendingActivity>

    <Tests>

    <Test></Test>

    </Tests>

    <Activities>

    <Activity></Activity>

    </Activities>

    </ShadowPendingActivity>

    </ShadowPendingActivities>

Copyright © 2009, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices

Open table of contents