Logon Procedure in the Subsystem Flow (Magic xpa 3.x)
The logon procedure can be introduced within the subsystem flow at different times and using different implementation methods. Each suggested logon implementation described below is valid. Choose the implementation you find best for your subsystem needs.
Before Opening the Main Subsystem Console
You may choose to have the initial request open the logon screen, and, as soon as the end-user confirms the logon details, the flow will continue from the logon screen to open the main subsystem console.
Calling the main subsystem console from the logon screen should be done by overriding the logon screen, which is no longer required. To override and replace the current screen, you should raise an event to be handled by the Main Program, which in turn calls the main application console. The destination property of the Call operation for the main application console should be set as ‘_top’. In this way the logon screen is closed, and the program that initiates the main application console is opened instead.
After Opening the Main Application Console
The logon screen can be opened within the application console. When the logon screen should be opened in the application may vary according to application needs.
Immediately After Opening the Main Application Console
When the menu program is loaded, it uses the Task Prefix to call the logon screen program, which is displayed in the main frame. When the logon procedure is completed, you can choose to run one of the application procedures or to simply display a welcome message.
By User Demand
The menu system may include an option that lets the end-user activate the logon screen program on demand. When the logon procedure is completed, you can choose to either run one of the application procedures or to simply display a confirmation message.
By Thread Demand
Some subsystems require user authentication prior to a specific application procedure. You can invoke the logon screen before entering such a procedure. When the logon procedure is completed, the relevant subsystem thread should be executed.
