Programs Overview
A program consists of multiple activities associated together to complete a recurring business process. A program can be set up to run on a policy or specific segment for a predetermined period of time. It includes attributes that define the program instance and as a result, activities can be run over time according to a specific schedule. Examples of such programs include asset rebalancing, automatic investment plans, systematic withdrawals and cost of living adjustments.
Users can inquire and change program data and scheduling information through the use of a unified programs view, instead of trying to piece together these facts by looking at activities and activity history.
Several prototype programs have been configured to demonstrate the configuration requirements for this functionality.
Business Rules
There are several business rules that drive program functionality. Refer to the Program Business Rule page for a complete explanation of these rules.
Database Tables
The following database diagram shows the relationship between the tables that store program data.
Program Database Tables
System Codes
There is one system code and one user defined code that store program information: AsCodeProgramStatus and AsCodeProgramType. Each of these can be edited using the Code Names editor in the Admin Explorer.
- AsCodeProgramStatus: this system code identifies program statuses. Program statuses are referenced in the <ProgramPriorStatusCode> element in the ProgramDefinition rule, when identifying a program's status prior to suspension.
-
AsCodeProgramType: this user defined code identifies the various types of programs. It is referenced in the <ProgramType> element in the ProgramScreen rule.
Security
Security is applied to the Program screen in OIPA using the Plan Security node for Program. If the main ProgramScreen checkbox is not checked, then the Program node will not be visible in OIPA.
There are also two business rules that control the display of the Add and Save buttons on the Program screen in OIPA. The PolicyProgram and SegmentProgram rules have an <Eligibility> section that identifies the policy statuses that allow programs to be added and updated. If security is applied, but a policy is in a status not defined in this section of the rule, then the Add and Save buttons will not be available. Refer to the PolicyProgram and SegmentProgram rules for additional information.