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

PUB Eligibility Determination Workflow Main

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

The PUB Eligibility Determination workflow invokes this workflow as a subprocess. Figure 14 shows this workflow.

Figure 14. PUB Eligibility Determination Workflow Main

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 Workflow. This workflow uses an application that determines benefits 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 Workflow. For more information about this substitute workflow, see Policy Automation Assess Workflow.
2. Validate Response Structure. This step reviews the output data from the previous step to determine whether this data is correctly formatted. The user properties of the ResponseValidationStringN form (where N is a number) in the PUB Case Benefit Plan Service business service determine the correct format. This step calls the ValidateResponseStructure method. Error messages that this method returns appear in a log file, and not in the user interface.
3. Screening? This step determines whether the user clicks the Screening button or the Eligibility button. If the user clicks the Screening button, then this step goes to Step 6. If the user clicks the Eligibility button, then this step goes to Step 4.
4. Check CoC. This step determines whether a previous active benefit plans exists for the citizen, and it determines whether the data in those plans must be changed. This step calls the CheckCoC method in the PUB Case Benefit Plan Service business service.
5. No Op? If the data in the previous benefit plans must be changed, or if a previous benefit plan does not exist, then this step goes to Step 7. If the data in the previous benefit plans does not have to be changed, then this step goes to Step 11.
6. Create Benefit Plan. This step creates benefit plans, associated benefits, and, if applicable, benefit payments. This step calls the CreateBenefitPlan method in the PUB Case Benefit Plan Service business service.
7. In CoC? If the citizen data changes a benefit plan, associated benefits, or benefit payments for an existing benefit plan, then this step goes to Step 8. If a previous benefit plan does not exist for the benefits case, then this step goes to Step 6.
8. Archive Existing Plan. This step archives a copy of the existing plans and associated benefits in the Benefit History view in the Plans view of the Cases screen. This step calls the ArchiveBenefitPlan method in the PUB Case Benefit Plan Service business service.
9. Clear Flag? This step determines whether the check in the Info Changed field of the benefits case must be cleared. If the user clicks the Eligibility button, then the check must be cleared, and the workflow goes to Step 11. If the user clicks the Screening button, then the check does not have to be cleared, and the workflow terminates.
10. Update Benefit Plan. This step changes the benefit plans, associated benefits, and benefit payments to reflect the changes to the citizen data that determines benefits. This step calls the Update Benefit Plan method.
11. Clear Info Changed Flag. This step clears the check in the Info Changed field of the benefits case. This step calls the ClearInfoChanged method.