Question:
1.) Are the Account Inconsistency Checks in a program, used for the Applicant Wizard? If not, in what scenario are these checks being used? In other words, at what point in the program process does the system look at these settings and how are they used?
2.) The settings for the Account Inconsistency Checks are Enable, Disable, and Use Defaults. What do those refer to? From the text it appears we can Enable the check, but why would we have a Disable (why just not Enable it) and what is the Use Default that the text is referring to?
Answer:
We've found that for most customers, most of their programs operate with similar rules, but they have programs with exception. Across all customers, there is no single set of rules that satisfies all programs so each of the inconsistency checks has a corresponding application setting for the default, and those settings are out-of-the-box set to behave most consistently with the legacy checks we had available.
The key for anyone using it is to set the application setting to how the majority of their programs operate. For the individual programs that don't follow the same paradigm, utilize the Account Inconsistency Checks in the program to set it to what they want instead
We use these settings specifically when checking for overlapped enrollment, so the pages where this could happen are EditAcctProgram, ViewAcctProgram, and EditEmploymentPlan. The check will be triggered any time the page reloads in order to show a warning pop-up to resolve enrollment conflicts in the program.
If an 'Enable' setting has been selected for any of the Account Inconsistency checks, that check will override any other program enrollment rules which may have been created.
The check can be turned in the Configuration Options:
If the setting is set to 'Disable', that flag will not be checked. If set to 'Enable' the flag will be checked. And, if set to 'Use Default' we will either Enable or Disable based on the default for that flag.