Non-role-dependent authorizations

The user data that is not related to the user’s role can also be grouped to reduce redundant data.

To reduce this data, you can use LN ’s AMS to create templates, which contain the user’s authorizations that do not depend on the employee’s role. The templates can also contain additional parameters that are required for developers to customize software components in LN.

The templates contain data that a group of users share. The templates are linked to individual users. The LN templates offer a user-friendly method to add new data. Or to update data for a group of users by linking the users to the templates.

The templates in LN ’s AMS can be divided into these categories:

  • User data and development-related templates
  • Text-related templates
  • Device-related templates

User data and development-related templates

In these templates, you can enter the default settings and parameters for a group of ordinary LN users and for LN users who develop software components in LN.

The data a user needs to maintain or create software components is defined in these templates:

  • User-data template
  • Developer-parameters template
  • Developer-authorizations template

User-data template

You can use the user-data template to define the common user data that by a group of LN users share. The template contains the required system data and some non-role-related authorizations. The user-data template is used as an example in “To create templates,” later in this chapter.

You must use the session to create the user-data template.

Developer-parameters template

You can also use the template parameters that application developers use. For example, you can choose to run an automatic compilation after you create or change menus or forms. You can also specify commands and options, which the user can employ in the development environment.

Application parameters are settings the application developer requires to develop software components. Parameters are available for:

  • Automatic compilation to the run-time data dictionary after changes to forms or menus.
  • Actions after the Copy to Current Package VRC option.
  • The parameters that the editor can use to develop software.

For every LN user, the data in this template is dumped to LN ’s run-time data dictionary in the User Application Parameters (ttadv010) table.

You must use the session to create the developer-parameters template

Developer-authorization template

You can use this template to define some of the authorizations for developers who must customize LN software components. This session is password-protected. You can only use this session if you have system administrator’s rights.

In this template, you can specify this information:

  • The package VRC for which the developer must be authorized to customize and develop software components. This specific package VRC overrides the Default Authorization for all Package VRCs check box in the User Data (ttaad2500m000) session.
  • The languages and modules of the specified package VRC for which the developers must be authorized to customize and develop software components.

When selecting the Authorization for all Modules and Authorization for all Languages check boxes, the users who are linked to the template are authorized to maintain and develop software components in all LN modules and in all languages. If the check boxes are cleared, you must specify the specific modules and languages for which the user must be authorized.

If you select the Components of other Developer check box in this template, the user is authorized to maintain the software components that are created by other users. This option is helpful, for example, for a senior application developer.

The data in this template is dumped to LN ’s run-time data dictionary for each individual LN user to the Version Authorizations by User (ttadv041) table.

You must use the session to create the developer’s authorization template.

Text-related templates

A normal user must have some basic authorizations to use, update, or read text. The required data and authorizations are defined in the text parameters.

These text parameters are defined in these templates:

  • Default text groups template
  • Default text groups by text field template
  • Text group authorization template

You can specify text parameters for a specific company or for all companies. When selecting the All Companies check box, the users who are linked to the templates are authorized to edit text in all companies. To restrict the users to a specific company, you must define that specific company in the Comp field. The text parameters that are defined for a specific company take precedence over defaults that are defined for all companies.

Default text groups template

You can use this template to define default text groups in LN. If a text is written in a text field for which no default text group is defined, the default text group is used. You must use the session to create the default text groups template.

Default text groups by text field template

You can use this template to define default text groups for text fields in LN. If text is written in a text table field, the text is linked to the default text group of that field. You must use the session to create the default text groups by text field template.

Text group authorization template

Use this template for each text group to define the use, update and read authorizations. A text group defines how text must be presented in a window by defining the text editor, default window, and dimensions of the window. You must use the session to create the default text groups authorization template.

Device-related templates

You can define the device-related data in the device preference template.

Device preference template

You can use this template to group devices and define an order of preferences for these devices. For example, you can define a range of printers, and give the highest priority to the printer closest to the user. The data in this template is dumped for each individual LN user to the Device Preferences (ttaad306) table.

You must use the session to create the device preference template. If the template is linked to a user who is not authorized for all devices. The user is only authorized to use the devices that are defined in this template. You can authorize a user for all devices if you select the Authorization for all Devices check box in the User Data Template (ttams1110m000) session.