A set of roles and composite roles are delivered with TE which can be copied and changed as required at client sites.
If the client wishes to take full advantage of the flexibility and granularity of the new authorisation concept, the following standard roles are supplied with TE, and can be used or copied and changed as required.
All of these are composite roles made up of a set of simple roles and have been created as a guide to best practice when setting up the TE authorisations concept:
| Composite Role | Description | |
| /BTI/TE:STD_VIEW_ROLE | The standard role for view only access to TE. This contains:
|
|
| /BTI/TE:STD_DEVELOPER_ROLE | The standard developer role for creating and maintaining transport forms and tasks. This contains:
|
|
| /BTI/TE:STD_PLANNER_ROLE | The standard role when using the planning functionality within TE and executing planning steps. This contains:
|
|
| /BTI/TE:STD_TEAM_LEAD_ROLE | The standard role for team leaders and approvers in TE. This contains:
|
|
| /BTI/TE:STD_TESTER_ROLE | The standard role for testers in TE. This contains:
|
|
| /BTI/TE:STD_CHANGE_TEAM_ROLE | The standard role for change teams. This contains: • /BTI/TE:CTS_USER • /BTI/TE:STD_CHANGE_TEAM_AUTHS • /BTI/TE:STD_VIEW_AUTHS |
/BTI/TE:STD_PROJECT_MGR_ROLE The standard role for project managers. This contains:
|
| /BTI/TE:STD_BASIS_ROLE | The standard role for transport maintenance, import and error handling. This contains:
|
|
| /BTI/TE:STD_ADMIN_ROLE | The standard role for configuration and administration access to TE. This contains:
|
Most clients should be able to use these ‘out-of-the-box’, but if changes are required, it is important that the client only updates copies of the TE delivered roles, as these standard roles may be updated during subsequent upgrades or other TE application updates.
Post your comment on this topic.