| # Print Subapplication authorizations (tgbrg5423m000) use.session.to print a selected range of subapplications and the authorizations and roles that are linked to them. You can either select a maximum of 10 subapplications and their authorizations. For every selected subapplication, or subapplication in the specified file, the system examines if it has a relationship with one or more activities in the selected range of business processes. The following three relationships exist: The subapplication is linked to the activity and can be reached from the session that is modeled as an activity type: (modeled and reachable). The subapplication can be started from the session that is modeled as an activity type, but the subapplication is not linked to the activity: (reachable). The subapplication is linked to the activity but cannot be started from the session that is modeled as an activity type: (modeled, not reachable). Related topics subapplication modeling Reference Model check.selected you can select a reference model in which the business processes (and their subprocesses) that you select must be present to have the selected subapplications and their authorizations printed. Reference Model A model that represents a line of business or business typology. A reference model is built from a library (repository) of the following model items: business-control model business-function model business-process model Subapplication List check.selected you can select a maximum of 10 subapplications whose authorizations will be printed. Subapplication An application defined as accessible from a defined component application. If the component application is an LN session, the subapplications are equivalent to LN subsessions. File with Subapplications check.selected you can select a file that contains subapplications whose authorizations will be printed. File with Subapplications The file that must contain the subapplications whose authorizations you want to print. Project Model check.selected you can select a project model in which the business processes (and their subprocesses) that you select must be present to have the selected subapplications and their authorizations printed. Print also processes present in previous versions check.selected the subapplications that meet the following conditions are printed: Are in the subapplication list or file that you selected. Are present in the selected range business processes that are modeled in the current modeling version or in versions from which the current modeling version is derived. Search depth of subapplications The number of subapplication levels that are searched to print the authorizations of the subapplications that are selected in the subapplication list, or are present in the selected file. Note The best way to view the different levels of modeled subapplications is to start the business process in which they occur in the Enterprise Modeler Editor, and use the Subapplication Modeler (tgbrg5124m000) session to actually see the modeled subapplications for each activity. Example If you specify a search depth of 3, the authorization that is linked to subapplication D is not changed. Current Version The version you currently use to create and modify model items. Project Model A model that represents a specific organization. . A project model is built from a library (repository) of the following model items: business-control model business-function model business-process model Reference Model The description of the reference model. Project Model The description of the project model. Print If you click this button, the printing of the subapplication authorizations starts. |