Shadow Policy
Policies can be removed from the system according to two scenarios. First, if the policy has no activities, segments, roles, or pending or recoverable disbursements, then a Shadow Policy option on the Policy screen Secondary menu allows a user to delete the policy. It will be completely removed from OIPA, but it will still exist in the database. Second, a StatusChange activity can be added to a policy and processed to move the policy to Shadow status. The policy will be completely removed from OIPA, but it will still exist in the database.
Scenarios
A CSR creates a new policy but before any activities, segments, roles or disbursements are added, he receives a call saying that the policy is void. The CSR clicks the Shadow Policy button on the Secondary menu of the Policy screen. A window displays and the CSR clicks OK to delete the policy. All validations pass and the policy is deleted. It is still available in the database, but can no longer be viewed in OIPA.
A CSR creates a new policy and adds segments, roles, and activities. The policy is advanced to active status. The CSR is then told to delete the policy. He adds the StatusChange activity to the policy and processes it. The policy is changed to Shadow status and is no longer visible in OIPA. It is still available in the database.
Configuration Requirements
There arethree business rules that must be modified to support shadow policy functionality.
- CompanyCosmetics
- EligibleTransactionsByPolicyStatus
- PolicyScreen
A transaction must be created to allow a user to change the status of an activity in OIPA. The StatusChange activity is used to accomplish this.
Business Rules
- CompanyCosmetics: This rule is overridden at the company level. A new element ShadowPolicyStatus identifies the status code or codes that represent a shadowed policy. The status codes are defined in the Code Names editor in the Administration folder of the Admin Explorer.
Navigate to Global Explorer | Business Rules | System | Company Cosmetics | Company Overrides | CompanyCosmetics (Functional Prototype Plan).
CompanyCosmetics Rule and AsCodeStatus Definitions
- PolicyScreen: This rule is overridden at the plan level. The new section ShadowPolicy defines the functionality of the shadow process. The ShadowStatusCode element identifies the status the policy is moved to after it is deleted. This status must be one of the statuses identified in the CompanyCosmetics rule with the ShadowStatusCode element. The AllowShadowButton element identifies the statuses a policy must be in to display the Shadow Policy option on the Secondary menu. The Validation section identifies the elements that cannot exist on a policy if the Shadow Policy button is used.
Navigate to Global Explorer | Business Rules | Plan Rules | PolicyScreen | Plan Overrides | PolicyScreen (FunctionalPrototypePlan).
- EligibleTransactionsByPolicyStatus: This rule identifies the transactions that are available to a user based on the status of the policy. The StatusChange activity should be added to all policy statuses. This allows the user to add it to a policy regardless of the policy status.
Navigate to Global Explorer | Business Rules | Plan Rules | EligibleTransactionsByPolicyStatus | Plan Overrides | EligibleTransactionsByPolicyStatus (Functional Prototype Plan).
StatusChange Transaction in All Applicable Statuses
Transactions
- StatusChange: This transactionprovides a list of statuses a user can select from when moving a policy from it's current status to a new status. When this activity is processed in OIPA, the policy status changes to the status selected in this activity.
Navigate to Global Explorer | Transactions | StatusChange.