Subapplication Modeling

Subapplication modeling only works for Running ERP. Within DEM, you model authorizations for end-users through specifying an authorization type with the modeled activities, and through linking Roles and specifying an authorization type with that link.

The result is that the end-user has a customized DEM menu, the Process Browser, which only contains the activities for which the end-user is authorized.

When a session is started from the Process Browser, the modeled authorization type is used. This ensures that a session is started in display mode; therefore, the user cannot change anything, but only look at the data.

From within an LN session, a lot of other LN sessions can be started. By default, these sub-sessions, known in DEM as sub-applications, inherit the authorization type of the main application, LN session. For some sub-applications that will not be acceptable. Within DEM, it is possible to model an exception for those situations.

This session is called Subapplication Modeler (tgbrg5124m000).

With this session, you can model the subapplications with an activity from within the process view in the EME.

The following sessions can be found in a new menu, which is a sub-menu of the ‘Application Components’ menu:

With the session Generate Sub-apps by Application based on Tools session tables you can automatically fill the sub-application table.

The entries are searched using the Tools information about the LN sessions. More details about the use of the session are present as online help within the session.

The result of this session is visible in the Subapplications by Component Application (tgbrg5163m000) session.

This new session Global change of Sub-application Modeling, adds a certain sub-application as a modeled sub-application to every activity, from which it can be reached as a sub-application.

For more details, see the help within the session.

The session Print Subapplication authorizations (tgbrg5423m000) can be used to print the result of the situation regarding the sub-application modeling. For more details, see the help within the session.

The session Copy Role - Subapplications by Component Application (tgbrg5228m000) session is working on activity level.

You can choose to work in the repository, or within a certain Project Model. It is possible to copy the information already modeled with a certain activity to another activity.

The session Analyzing of modeled Subapplications (tgbrg5127m000) session is made for analyzing the current modeling situation.

For every application, you can define one or more subapplications.

A subapplication can be started from another application, and for which a different level of authorization can be assigned in the business process model compared to the main application to which it is linked.

To link one or more subapplications to an application, use the Subapplications by Application (tgbrg5154m000) session.

You only need to define subapplications if you want to assign a different level of authorization to the subapplication in comparison to the main application to which it belongs.

An option is added to the Specific Menu to start the new session Generate Sub-Apps by Application Based on Tools Session Tables (tgbrg5258m000).

You cannot select a session and add it to the list in session Subapplications by Application (tgbrg5154m000).

This functionality is taken over by session Generate Sub-Apps by Application Based on Tools Session Tables (tgbrg5258m000).

Start this session from the Specific Menu in session Applications by Component (tgbrg5155m000).