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

PUB Screening Determination Workflow Main For IO Mappings

This workflow uses the data that is associated with a case to determine the benefits for which a citizen is eligible.

The PUB Screening Determination Workflow For IO Mappings invokes this workflow as a subprocess. Figure 18 shows this workflow.

Figure 18. PUB Screening Determination Workflow Main For IO Mappings

Workflow Description. This workflow performs the following actions:

1. OPA Connector. If Oracle Policy Automation Connector is installed, then this step calls the Policy Automation Assess IO Workflow. This workflow calls the deployed rulebase to evaluate the citizen data and determine the appropriate benefit plans, associated benefits, and benefit payments for the citizen. If Oracle Policy Automation Connector is not installed, then this step calls a substitute Policy Automation Assess IO Workflow. For more information about this substitute workflow, see Policy Automation Assess IO Workflow.
2. Contact IO to Case IO Conversion. This step converts the Oracle Policy Automation response (the PUB Sample Intake Contact integration object instance) into a PUB OPA Generated Benefit Plans integration object instance. Benefit plans and benefits, but not benefit payments, are mapped to the integration object instance.
3. Update Case Header. This step updates the Case Row ID in the PUB OPA Generated Benefit Plans integration object instance.
4. Delete Screening Records. This step deletes any existing screening records.
5. Upsert Case-PB IO instance. This step calls the Upsert method for the Siebel EAI Adapter to update or insert benefit plans, benefits, and payments for the case. For this upsert operation, this step uses the integration object that Oracle Policy Automation returns.