Creating and editing system configuration settings
A few key business rules apply to creating and editing system configuration settings from the BA portal.
- Pega Smart Claims Engine for Healthcare allows the user to create and store system settings instances that will become effective in the future. In this case, the current settings remain in effect until the user defined start date of the new instance.
- When the user creates a new system setting instance that will become effective in the future, Pega Smart Claims Engine for Healthcare automatically changes the end date of the current instance to correspond with the start date of the future instance. For example, if the date span for the current system setting instance is 9/1/2017 - 12/31/2017, and the user creates a new instance to become effective on 10/1/2017, Pega Smart Claims Engine for Healthcare automatically changes the end date of the current instance to 9/30/2017.
- All future system settings are displayed in the audit history in chronological order with the most current instance on top.
- The user may edit any settings from the current date going forward; however, no edits may be made to any setting instance prior to the current date. Pega Smart Claims Engine for Healthcare displays a system validation when the user attempts to edit past settings.
- Pega Smart Claims Engine for Healthcare also ensures that system settings run concurrently and, therefore, does not allow gaps in system settings, or overlapping dates. If the user creates a system setting instance that results in a gap or overlapping date, Smart Claims Engine displays a validation, and prevents the user from moving forward.
Previous topic Reviewing system configuration history Next topic System configuration in Designer Studio