Validation issues and out-of-sequence jobs

If there are validation issues with a job, PolicyCenter requires you to handle validation issues before it displays the out-of-sequence user interface. In most cases, fixing the validation issues at the effective date of this job is sufficient to prevent validation issues when applying (merging forward) changes in the Out-of-Sequence Conflicts tab.

In very rare cases, even after handling out-of-sequence conflicts there can be validation errors in the same contractual period with later effective dates. For example, suppose you changed driver usage time percentages and caused out-of-sequence conflicts and applied some driver usage values forward but not others. This would mean you could temporarily cause the driver percentages to be less than 100% or greater than 100%. If validation errors at future effective dates occur due to handling out-of-sequence conflicts, PolicyCenter displays a special user interface to handle this case.

PolicyCenter alerts you to the validation errors and displays a picker in the left navigation bar so you can select future effective dates at which there are validation errors. After selecting a future effective date that contains the validation error, you can update the values that cause the validation errors.