- Overview
- Specs
- Reviews
- Requirements
- Docs
This app provides institutions with the ability to add/activate or inactivate a Warning Flag or Lockout Flag on a group of persons or accounts. The batch application may be configured to process the flags maintenance based on parameter values, or to read in a comma-delimited file of data to be updated. This application produces a single report detailing the changed data and listing any errors.
Key Benefits
This application can improve your efficiency by automating the activation or inactivation of warning and lockout flags on a group of persons or accounts.
A runtime parameter (8IS) defines whether the application will read an input file or use the remaining run-time parameters to process the Warning and Lockout Flags. The 'Parameters' option works well if a large number of persons, organizations, or accounts need to have the same action performed (i.e. expiring all warning flags of a specific type). If, however, the required updates vary (i.e. some persons, some organizations, varying flags and actions), then the 'File' option should be selected. If a file is used, then the remaining run-time parameters, except 'Report Only YN' and 'Record Activity Y/N', will be ignored. For each warning or lockout flag update performed, the application can write the corresponding information to the Activity table, depending on the setting of the 'Record Activity Y/N' application parameter.
The parameter Person ID Type Codes (8PIT) will allow an institution to place a warning flag (as specified in the parameter Restriction Type Code) at the person level if the identification type in the parameter value is found on the person record with an expired date. The parameter Number of Days After Expiration (8NDE), if used, will only place the warning flag after the identification type has been expired the specified number of days.
In addition, when the parameter Person ID Type Codes (8PIT) is used, the application will inactivate the warning flag (as specified in the parameter Restriction Type Code) on any person record where the specified identification type is not expired but the warning flag is still active. PS_WRNLOCKOUT will exception out any person where the specified person id type code has no expiration date or a future dated issue date. The application will not remove an active warning flag or create a warning flag if the identification type does not have an expiration date.
When the parameter Person ID Type Codes (8PIT) is used the restriction action types listed on the report will be A = Added restriction, I = Inactivated restriction and U = Updated restriction.
Write Your Own Review
Only registered users can write reviews. Please, log in
- The Warning or Lockout code to process must exist in the database.
- The core database only supports Lockout Flags on accounts, not persons or organizations. In the event that the application parameters or file data indicate lockout flag processing for entities other than accounts, the records are not processed and an error message is generated on the report.
Exclusions:
Warning and Lockout Flags are effective and/or inactive (as applicable) as of the date and time that the application is run. No support is provided for effective dated entries.
Version Information:
1.0.0.4 Published - March 2019
Explore Appstore
- By Category
