| # Authorization review and drill back The term “Drill back” must be read as: "Start an LN session from outside LN through Infor Ming.le ". This can be initiated by another user and without providing any authorization context. For example; an approval step from a workflow set up in ION. In this approval step you must view specific LN data to decide on approval or rejection. To set up the correct authorization for your DEM users to drill back from Infor Ming.le into LN you must specify several sessions with information. The classic method to start a session is by selecting a session by the user within an UI. In the LN UIs you can use: Menu Browser Process Browser Process Viewer Run Program. The menu option “Call session by Code”. This option can start a session by entering the session code. When a session is started from the “Menu Browser” or “Run Program”, the AMS authorizations is used. AMS session authorization is the highest (aggregated) authorization level defined for a certain user over all assigned AMS roles. When a session is started from the “Process Browser” or “Work Area” the DEM generated authorization advice is used (based on the “active” DEM role). For DEM end-users the UI settings must only have granted access to the “Process Browser” and/or “Process Viewer” in order to prevent confusing authorization situations where AMS is not the same as DEM. Do not select the menu browser and “Call Session by Code” in the User Data Template (ttams1110m000) session. You can gather and view the authorization information for the AMS and DEM user with these sessions: Aggregazione dati autorizzazione (tgbrg9298m000) Visualizzazione dati autorizzazione (tgbrg9598m000) Ensure you specify the Aggregazione dati autorizzazione (tgbrg9298m000) session with the correct information. With the Visualizzazione dati autorizzazione (tgbrg9598m000) session all authorization data per user is listed. With this list you can review the authorizations for the LN users and consider necessary changes. Within the UIs personalization options are available to overrule and hide those parts of the UI that are initially enabled on the back-end. View sets are maintained within the View Modeler (tlvwm0601m000) on the back-end where custom views overrule Standard Views as delivered by Infor. Run the View Modeler from Web UI. In the View Modeler both Standard (read-only and as delivered by Infor) as configurable Custom view sets are shown |