During a nightly cycle or any specific job execution, there is a need to lock certain application functionality. Some jobs read tables modified by the processing of transactions and some read tables for processing instructions or other input. If these types of updates are made during job execution, it may result in job failure or unwanted outcomes from processing.
Typically, administrators stop users from accessing applications by bringing down the application to prevent online access. With a unified UI, if access to a specific URL is prohibited, it could prevent all users from accessing all of Advantage. For instance, if users are using the HRM URL to sign in to the application and they want to run a process that requires the online HRM application to be locked. All Administration, Financial, and Performance Budgeting users are locked out of the application. This chapter explains a way to lock a specific application without locking users from accessing other applications through a unified URL.
To lock a specific application, an administrator with database schema access updates the IN_SYS_ST table. This table always has a single row that maintains the system state. Each application schema has its own version of this table. The SYS_ST column value decides the state of the system. The CVL_SYS_ST table defines all the possible values of SYS_ST.
The following table provides the description for all possible values:
SYS_ST |
ST_DESC |
Description and Usage |
1 |
Down |
With this value the application will be truly locked and no user will be able to login to the application. |
2 |
Up |
Default value. With this value the application will be up and running. Users can login and perform necessary tasks. |
3 |
Offline Only |
Users are not able to log in to the application; however, the jobs can be scheduled and executed. |
4 |
Offline Only |
Jobs cannot be scheduled; however, users can log in to the application. |
5 |
Offline Only For Current Application |
Apart from offline access, in unified UI setup, users are allowed to log in to the application using an application URL. However, users are not allowed to open any page that belongs to the application URL. For example: Users logging in to the HRM internal or external URL can still login to the application and can open any page from FIN/Admin/PB; however, the user will not be able to open HRM application pages. |
6 |
Offline And External Facing Only For Current Application |
Apart from offline access, in unified UI and external facing application setup, users are allowed to log in to the application using an application URL. However, users are not able to open any page that belongs to the application URL. For example: User logging in to the HRM internal URL, can still log in to the application and can open any page from FIN/Admin/PB; however, the user cannot open any HRM application pages. If the user is using an external facing HRM application URL, he/she can continue to use the application normally. |
7 |
Offline And Internal Facing Only For Current Application |
Apart from offline access, in unified UI and internal facing application setup, users are allowed to log in and use the internal application normally. However, while using the external application URL, users are allowed to login, but are not allowed to open any page. For example: User logging in to an external HRM URL can still login to the application and can open any page from FIN/Admin/PB; however, the user cannot open any HRM application pages. If the user is using an internal facing HRM application URL, they can continue to use the application normally. |
If the Bypass Application Locking flag is set to true on the Security Role (SCROLE) page for a security role, then users associated with the security role can bypass the locking of application pages.