On the Actions tab, you define what entitlements are granted to the user - for example, access to an application, or membership in a role or group - when a user receives the service.
On the Actions tab, from the drop-down menu, select one or more of the following actions:
Service members receive access to the selected application. The system applies group membership or rule string configuration for the application, if necessary. For more information, see Creating an Application.
The system adds a link and icon for the application in the User Console of service members. This action need only be added when you want to give users access to an application through this service. Select one of the following options:
Select the application that you want service members to be able to access, and enter a name for it. The system adds an icon with this name in the User Console Home page of service members. The system also adds a link with this name in the left-hand navigation pane of the User Console of service members. The icon and the link both launch the application.
This action is the same as creating an admin role. If you have task administration privileges, you can add one or more tasks to this role through the Modify Admin Role task. The system then adds a link to these tasks in the left-hand navigation pane of the User Console of service members. For more information, see Admin Roles and Tasks.
Select the launch role that you want service members to be able to access. This role can be a launch role for an application, or for any admin role.
Service members receive the selected provisioning role. The system creates an account for the user in the endpoint that is configured in the provisioning role when a user receives the service. For more information, see Creating Roles to Assign Accounts.
The system adds service members to the selected group.
The system adds the indicated attribute to the user accounts of service members.
The system adds each action that you select to the service. When a user receives access to the service, the system applies each action to the user. For example, the user receives the indicated Launch Role, and access to an application in their User Console Home page.
Important! You can set the order of actions in a service. If you add actions that affect user attributes, and have a provisioning action in the service, order is important. Place actions that affect attributes before any provisioning actions in the action order. The Attribute action can affect user attributes. The Application action can also affect user attributes, if a rule string is configured for the application.
Note: Typically, the application and provisioning role you select while creating a service are closely related. The application makes a specific software resource available in the system. The provisioning role creates a user account in the same software resource. Thus, when a user receives the service, they automatically receive access to the software resource through their User Console, and an account in the same software resource.
When you have added all desired actions to the service, click Submit. The system creates a service with the selection actions. When a user receives access to the service, the user receives access to the selected application. The user also receives all roles, groups, and attributes you included in the service.
|
Copyright © 2014 CA.
All rights reserved.
|
|