You are here: Main Explorer > Prototypes > Previous Release Prototype Samples > Programs Prototype
Oracle® Insurance Rules Palette 9.7.1.0 E51561-01
Programs Prototype
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.
Program Configuration
Three programs were configured on the Functional Prototype Plan to demonstrate program functionality.
- Program A: This is a policy program linked to the Functional Prototype Plan and the Rider with Roles segment. Navigate to the Global Explorer | Programs | Program A | ProgramDefinition.xml. The ProgramDefinition contains the following configuration.
Fields: In addition to the fixed Program fields, the following fields have also been configured. ProgramStartDate (Fixed field), ProgramEndDate (FixedField), ProgramEffectiveDate (FixedField), ClientName (dynamic field), ProgramFrequency (dynamic field), ProgramAmount (dynamic field), NextScheduledDate ( Disabled field. This date is disabled and updated through CopyToProgram Fields on certain activities).
- Validations: there are three validations added to the validations section.
- Program B: This is a policy program linked to the Functional Prototype Plan only. The Both operation identifies that the Add and Save buttons will be available for programs. One test condition also exists for this program. If a policy's Issue State Code is 05, for California, then programs cannot be added. Navigate to the Global Explorer | Programs | Program B | ProgramDefinition.xml.
- Program C: This is a segment program linked to the Rider with Roles segment only. The Both operation identifies that the Add and Save buttons will be available for programs. One test condition also exists for this program. If a policy's Issue State Code is 05, for California, then programs cannot be added. Navigate to the Global Explorer | Programs | Program C | ProgramDefinition.xml.
Two new code names were added to AsCode.
- AsCodeProgramType: this user defined code identifies the types of programs. The TYPE attribute in the ProgramScreen business rule references this code name and its values.
- AsCodeProgramStatus: this system code identifies program statuses. It is referenced in the <ProgramPriorStatusCode> element in the ProgramDefinition rule, when identifying a program's status prior to suspension.
Several attached rules were configured and attached to the transactions referenced in the programs above.
Transaction Configuration
The Program Configuration section above shows how the transactions are associated to the program. The information in this section explains the configuration driving the transactions.
- SetUpProgram: This transaction was used in all three programs. It spawns the scheduled activity for each program. The configuration demonstrates how scheduling is controlled. The Function - NYOKWithDirection is used to trigger the spawning of the scheduled activities on the next business day. The ResetProgram rule is attached to this transaction.
- PolicyProgramAScheduledActivity, PolicyProgramBScheduledActivity and SegmentProgramCScheduledActivity: Using Function- NYOKWithDirection, each scheduled activity is configured to spawn on the next business day. The attached CopyToProgramFields rule copies the NextBusinessDay math variable to the NextScheduledDate on the Program screen. The TransactionBusinessRulePacket uses rule IF syntax to determine when the TerminateProgram rule should execute.
- TerminateProgram: this transaction will terminate any program on the policy after it is processed.
- Grace: this existing transaction was modified to spawn TerminateProgram. It adds a TerminateProgram transaction override to Grace demonstrating the use of the rule attached to a non-program activity. TerminateProgram will terminate any programs on the policy.
- Reinstate: this transaction was configured in two different ways to demonstrate how a program is reinstated and what happens to program activities that were suspended. This transaction spawns the scheduled program activity. The transaction has the ReinstateProgram attached rule overridden at the transaction level. The ReinstateProgram rule will reinstate the program and generate a ReinstateProgramSkip or ReinstateProgramProcess based on the behavior defined in the ProgramDefinition.
View Prototype Example in OIPA
- Log in OIPA using the Prototype Company user ID and password.
- Click Policy | New from the Main menu.
- Type the new policy information and save the record.
- Click Programs from the Left Navigation menu.
- Add a program and save.
-
Click the start icon in order to create the SetUpProgram activity.
- Click Activities to see the program activities.
Copyright © 2009, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices