Adding System Plans to the Repository
QUESTION: How are System Plans put into the Repository?
ANSWER: The example below shows the relationship between a Repository and its System Plans.
Example - There are two plan sponsors: one for Plan A and Plan B and another for Plan Z.
Plan A and Plan B use Contract Number and Location as their key fields: Contact Number must be 12345, 444 or 1777 and Location must be 001 or 002 to be in Plan A. Contact Number must be 858 and Location must not be 001 or 002 to be in plan B.
Plan Z uses an Employee Code as its key field. Employee Code must be equal to “Officer” to be in Plan Z.
Three System Plans will be setup. Each will have the same Key Numbers in the same order. Operators: In, Not In and Any will be used when setting up the Key Values for each plan:
Key Number | System Plan A | System Plan B | System Plan Z | |||
Operator | Key Values | Operator | Key Values | Operator | Key Values | |
1 | In | 12345/444/1777 | In | 858 | Any | |
2 | In | 001/002 | Not In | 001/002 | Any | |
3 | Any | Any | In | Officer |
The paths to these fields within all of the XML Database Linkages are maintained in the Repository File Keys:
Key Number | XML Path |
1 | The XML path to Contract Number for plans A and B |
2 | The XML path to Location for plans A and B |
3 | The XML path to Employee Code for Plan Z |
Once the System Plans are complete with their Key Values, clicking the File menu item, Server Maintenance and Repository File Maintenance allows you provide the XML key paths by clicking the Manage button and selecting Keys… After clicking OK, you can click on the Manage button again, select Add a System Plan… to include a system plan into the repository.
Click here for more information on System Plans.
Click here for more information on Repositories.