Stackable Roles - Intergraph Smart Materials - Version 10.1 - Administration & Configuration - Hexagon

Intergraph Smart Materials Classic Administration (10.1)

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Administration & Configuration
Smart Materials/Smart Reference Data Version
10.1

You can either use individual roles or you can stack or summarize them. To control which way you want to use roles, set the STACKABLE_ROLES DBA setting.

If STACKABLE_ROLES is not set to Y, you are working with individual roles. This means that on the logon screen, the user can see a list of all projects/product groups, with the assigned disciplines, languages, and roles to which access has been granted to the user. After selecting a role and logging in, the user can do everything that this one role allows.

If the value of the DBA setting STACKABLE_ROLES is set to Y, you can stack your roles. On the logon screen, the user will only see a list of all projects/product groups, with the assigned disciplines and languages to select from. After having selected one record to login, the user can do everything in the application that all assigned roles for the selected combination of project/product group, discipline, and language allow.

The example below illustrates the stackable role feature in detail.

The ROLE1 and ROLE2 roles have been created on the A.30.03 Roles/Menus screen. ROLE1 covers all administration and Smart Reference Data menus and screens, and ROLE2 covers all MSCM menus and screens.

The user has been given access to project TRAINPROJ, discipline PIPING, language English, and roles ROLE1 and ROLE2 on the A.20.06.02 User Security for Projects screen.

In ROLE1, the disciplines ELECTRICAL and INSTRUMENTS can also be queried for (A.20.06.03 Queryable Disciplines screen).

For ROLE1, the user owns the privileges ASSIGN DISCIPLINES and ASSIGN USER PRIVILEGES OP; for ROLE2, the user owns the privilege PO APPROVAL (A.20.06.04 User Privileges screen).

a) Login without stackable roles (STACKABLE_ROLES not set)

b) Login with stackable roles (STACKABLE_ROLES set to Y)

On the logon screen, the user will only see one record when working with stackable roles. After he has logged on to TRAINPROJ, discipline PIPING, language English, he will be able to work within the application as if he has logged on with role ROLE1 and ROLE2 at the same time. The user will have access to all administration, SPRD, and MSCM menus and screens. He will be able to query for disciplines ELECTRICAL and INSTRUMENTS, too, and he will not only have the privileges ASSIGN DISCIPLINES and ASSIGN USER PRIVILEGES OP but also the privilege PO APPROVAL.

Such a stacked role covers:

  • all menus and forms assigned on A.30.03 Roles/Menus, Role/Menus tab

  • all guided tours assigned on A.30.03 Roles/Menus, Guided Tours tab

  • all configurations assigned on A.30.03 Roles/Menus, Configurations tab

  • all privileges assigned on A.30.03 Roles/Menus, Privileges tab, and on A.20.06.04 User Privileges

  • all sections assigned on A.30.03 Roles/Menus, Sections tab

  • all disciplines assigned on A.30.03 Roles/Menus, Queryable Disciplines tab, and on A.20.06.03 Queryable Disciplines

Some special features:

You always get the highest access of all your roles. That is, if one role grants full access to a screen and another role only allows a read-only access, the stacked role will grant full access. This also applies to the activation/de-activation of menus and the restricted availability of blocks or fields. If a menu is de-activated in one role, but not in another, this menu will not be de-activated in the stacked role. If one role allows you inserts or updates in a block or gives you the right to use a specific button but the other role does not allow you to do so, the stacked role will give you all these rights.

Configurations

If you have been assigned to roles in which the use of configuration has been limited by assigning configurations to the role but also to roles in which this use is unrestricted, all configurations will be available in the stacked role. Stacked roles are also taken into account when finding and saving favorite configurations on the core workflow screens. When working with stacked roles, all roles of the current combination of project/product group, discipline, and language are checked and updated to ensure that the user's favorite configuration is always available.

Sections

If you have been assigned to roles in which the view on requisitions and agreements for MSCM has been limited by assigning sections to the role but also to roles in which the view is not limited, all requisitions and agreements will be available in the stacked role (provided that at least one of your securities allows unlimited access to sections - Section field on the A.20.06.02 screen).

On the A.20.06.02 User Security for Projects screen, a section can be selected for each role, project, discipline, and language. Also, in this case, we recommend to only assign one section at most if you want to use this feature. Again, NULL values are ignored. So if you want a section to be available in your stacked role, you only have to assign it to one role, not to all for the same project, discipline, and language.

Queryable Disciplines

If a queryable discipline has been marked as not to be displayed in one role but to be shown in another role, this discipline will be displayed in the stacked role.

B.10.06 BOM Views

This also refers to the selection of the view name on the A.20.06.01 User Security for Product Groups and A.20.06.02 User Security for Projects screens. This view name is needed for the B.10.06 BOM Views screen. Again, a message will appear when logging on with a stacked role in which no view is available because different view names have been assigned to the user's individual roles.

C.10.21 Set Environment

On the C.10.21 Set Environment screen, you define which rules are to be used for the creation of MRRs, MIRs, OS&Ds, and so on.

If for all the user's roles per project/product group, discipline, and language, only one rule has been assigned, this rule is used by the stacked role. It is not necessary to assign this rule to all the user's roles per project/product group, discipline, and language. NULL values are ignored. It is only important that if a rule has been selected, it must be identical for all roles. If different rules have been used for different roles but the same project/product group, discipline, and language, no rule will be available at the beginning of a session with stacked roles. In this case, a message displays to tell the user that these settings are not available in the current session.

We recommend that you only assign one rule at most for each role per project/product group, discipline, and language.

C.10.23 Indicated Items and Sorting

The C.10.23 Indicated Items and Sorting screen allows you to configure the C.20.22.02 MIR by BOM Commodity (Group By) screen. For this screen, too, we recommend to use it only for one role at most to make these settings available for stacked roles. If more than one configuration can be found, a message will inform the user that this configuration is not available.

For user menu items, too, we recommend to create them only for one role at most to be able to use them in a stacked role as well.