Some perspectives might only be for some roles, which allows the user to restrict the perspectives that one can see in a given role (for example, no administration perspective when acting as a basic user).Ī Slice partitions choices into domains that can be shared across an organization. Some pages might only be for some roles, which allows the user, for instance, to hide or make read-only some attributes for some roles even if he or she can edit that attribute in other roles. On the other hand, a user with not many permissions could act in a role that allows a lot of things, but he or she would still be restricted to the subset that he already has permission to. The active and committed project lists are filtered to the current role.The current role choice group, page, and perspective permissions act as a filter to restrict what the current user can do while acting in that role:įor instance a user could be an administrator with CRUD permission on all choice groups but, when acting in a specific role, he or she would only be able to do the actions allowed in that role. The project drop-down consists of the Main Repository and all the projects of the current role. This drop-down lets you select a role among all the roles to which you belong. The topmost drop-down in the user interface is a role selector. To see details of the Slices selected, click the Slices tab.Ī user acts in Decision Manager within the scope of one of the roles to which he or she belongs. Different Slices can be selected for the Slices I can see, Slices I can modify and Default slices for new choices fields.ĭescription of the illustration slices_15.gif Select Slices by clicking the arrow buttons, as shown below. You should select appropriate slices for Slices I can see, Slices I can modify and Default slices for new choices so that the user in this Role is restricted to only those Slices and, in turn, to its choices.ĭescription of the illustration slices_14.gif A Role can exist with 0 or more slices but a Role that is not linked to any slice cannot view choices associated with a Slice. You are not required to assign a Slice to a Role when you create it. By default, none of the Slices are selected for the Role, as shown below. This page allows user to assign Slices so that they have permission to view, create (default slices to be used for choice creation) or update slices. The Slices page appears, as shown in the following example. In addition, to assign a Slice to this new Role, the user should select a Role (from the Role drop-down) having Read, Update and Create permissions on Slices.Ĭlick the Create icon and select the Role choice group, as shown here:ĭescription of the illustration slices_12.gifĮnter Role name and Description if required, as shown in the following example, and click Next.ĭescription of the illustration slices_13.gif Once all the required Roles, Slices and components the project needs to be committed by clicking on commit button.Ī Role can be created if a user is having Create permission on Role choice group. By default all Roles linked to logged-in user are selected, enabling you to make changes however, you can change this default selection and select only those Roles that you can modify in this project.Īfter the project is created, the context is automatically switched to the new project, as displayed in the View box, and the project details display all the Roles with which the project is associated. The ”Roles that can make changes in this project” lists all Slice based Roles assigned to the logged-in user. The user can change this default selection and select only those roles for which this project needs to be visible. By default all Roles linked to this user are selected. The ”Roles that can see this project” lists all Slice-based Roles assigned to the logged-in user. You can either leave the default value, Incremental Changes, or select another value. Some users with slice administration permissions can assign roles to newly created projects.Įnter project Name and optionally Description and Audit Trail Comment. User can choose current role from combo box. The context can be either Main Repository or an active project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |