Map Enterprise Role Task

The role of this activity in the application creation life cycle

This activity maps between role-ou-activity and task of the available components in repository. Significance of the mapping infers the permission to access the activities of the components by the role-ou-task.

What the activity comprises

• 'Map Enterprise Role Task' consists of Role Name, OUInstance, Component Name,Activity Name options in the header with Role Name and OUInstance having links to the respective help screens. Component Name, Component Description, Activity Name, Activity Description ,ILCO Name,ILBO Desc,Task Name,Task Desc,and Task Type are in the multiline.

• Task Name help is available to aid user to locate task names for corresponding component-activity.

Prerequisites

OUInstances, Roles, Components, Activities and OU-Component combination should be exist.

Working with this screen

The screen provides the facility to add/modify or delete Task information for the activity

• The component combo in the header will have all the components permitted against the Role-OU combination. This means that there will be a UI task on the OU Edit Control and based on the given Role and OU, those components for which mapping has been done in the Map Enterprise Roles screen alone will be loaded.

• The activity combo in the header will be loaded dynamically based on the component combo selection. Note that only those activities that are mapped against the component in the Map Enterprise Roles Screen will be loaded in the Activity combo for the selected component. If the user selects the option ALL in the Component combo, then the Activity Combo will be defaulted with the option ALL and that will be the only option available in the Activity combo assuming that the user would like to provide permissions for all the activities of all components. ALL components would mean only those components that are mapped to the specified OU through the Perform OU instance to Component Mapping screen though system would list all the components that the OU is not mapped.

• If the user selects a particular component in the Component combo and selects the ALL option under the Activity combo and clicks on the Save all tasks for the selected Component Activity button, then all the tasks under that particular component will have permission for the specified Role and OU combination.

• If the user wants to give permission for selected components and activities, then the user can select that particular component and activity in the header combo and use the Help on Component-Activity-ILBO-Task link and choose those ILBO-Task combinations that we would like to give permissions. The tasks types that would be listed in the help screen would be Submit, Trans and Link only.

• Note that when the user gives permission for the Link tasks, it would mean that the Role-OU combination has privileges only to launch the link and all the tasks inside that launched ILBO will not have permission unless given explicitly for that ILBO under the corresponding Component and Activity combination.

• The 'Fetch all permitted ILBO-Tasks' task will have the similar functionality as that of the 'Fetch all permitted Activities' task in the Map Enterprise Roles screen. Similar to that of the Map Enterprise Roles screen, the user can view only those ILBO-Task combinations against the selected component and activity in the header combo.

• If the user wants to remove permission for a particular ILBO-Task combination, then he can delete that particular row alone from the gird and save the details.

Description of header fields

Description of the fields in the multiline

Tasks that can be carried out using this screen

• Fetch All Permitted Task

• Save All Task For Selected Comp-Act

• Help on Task

• Help on Role Name.

• Help for OU instance.

• Save Activity Task Mapping