Siebel Public Sector Guide > Public Sector Workflows > Workflows for Benefits Cases >

PUB Flag Related Cases Batch Mode Process Workflow


This workflow scans the data that is associated with all active benefits cases to determine whether the data that determines the benefits changed after the benefits were last automatically assigned to each case. For each case for which this data changed, this workflow finds the associated contact records. Then, this workflow finds all cases for those contact records, and selects the check box in the Info Changed field of those cases. The processing in this workflow evaluates changed data in only the fields and records that are implemented for effective date tracking. Figure 25 shows this workflow.

Administrators configure this workflow to automatically execute at appropriate time intervals.

Figure 25. PUB Flag Related Cases Batch Mode Process Workflow

Workflow Description. This workflow performs the following actions:

  1. Load the Bus Comps to scan. This step generates a list all business components for which effective dating is set up. This step calls the LoadBusCompsToScan method.
  2. Get the BC to scan. This step selects the first business component from the list in the previous step, and goes to the next step. After the remaining steps in the workflow are complete, this step selects the next business component in the list from the previous step. This step iterates through all of the business components in the list. This step calls the UpdateTheBCToScan method.
  3. Is BC available? If any business components remain for scanning, then this step goes to the next step. If the no business components remain for scanning, then the workflow terminates.
  4. Detect a changed record. This step generates a list of all records for the business component that changed after an agent last automatically assigned benefits to the case. This step selects the first record in the list, and goes to the next step. After the remaining steps in the workflow are complete, this step selects the next record in the list. This step iterates through all of the records in the list. This step calls the DetectChangedRecord method.
  5. Record Available? If any records remain for checking, then this step goes to the next step. If no records remain for checking, then this step goes to Step 2.
  6. Find Contact Records. This step finds the contacts that are associated with the record. This step calls the FindContactRecords method.
  7. Find Cases To Flag. This step finds the cases that are associated with the contacts from the previous step. This step calls the FindCasesToFlag method.
  8. Flag Cases As Info Changed. This step selects the check box in the Info Changed field for the cases from the previous step. This step calls the FlagCasesAsInfoChanged method.
  9. Reset Core Flag. This step resets the core flag in the Siebel database. This flag tracks the history of changes to the record. This step calls the ResetCoreFlagForChangedRecord method.
Siebel Public Sector Guide Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices.