The following configuration and set-up is deemed optional and is not mandatory for running ActiveControl. Many organisations choose not to setup some or all of these steps due to their own internal and external requirements and obligations.
|3.4.1||Switch on Transport Backout|| Within the Import Options tab of each Target System, enable the “Automatically create backup transport requests” for all required systems
Most organisations switch on Backout for Production systems only. Note, a virtual system called BAK also needs to be created in TMS for Backout to work.
If using Transport Backout, you also need to set the STMS parameter tadirdeletions = “True” in each of the systems where Backout transports will be created.
|3.4.2||Add TE Priority Approvers|| Within the Administrators and Priority Approvers tab, add in the names of any Priority Approvers deemed necessary within your organisation.
This activity is deemed as optional. For most organisations, Priority Approvers will not be set-up for audit/compliance reasons.
|3.4.3||Add Labels|| Labels can be used to customise the text names of fields presented within ActiveControl Windows GUI. For example, you might want to create a label to rename the default Reference field on a TE Task to be Remedy Number.
Labels can be created within the Classifications tab as required.
|3.4.4||Configure User Roles||Within the User Roles tab, create any required user roles and then allocated the required users to each one.|
|3.4.5||Configure Planning Statuses|| Within the Task Statuses tab, add any Planning Statuses that were defined during the Preparation Phase activities.
This activity is deemed as optional. For most organisations, the Planning functionality will not be used within ActiveControl as any pre-transport deployment will be handled outside of ActiveControl.
|3.4.6||Configure Planning|| Within the Planning tab, create any required planning configuration. This is used for pre-deployment approval steps (e.g. CAB approval).
|3.4.7||Setup Configurable Analysis|| Within the Targets and Transport Paths tab, open the required target systems and in the Analysis Types tab, switch on the required analysis types.
This can be used to setup checks like Risk Assessment, Security, Performance, Development Standards, etc.
|3.4.8||Web UI: Maintain preferences||Use SM31 to update table /BTI/TE_WEBUICFG in the Domain Controller to set any general parameters and preferences for the TE Web UI.|
|3.4.9||Web UI: Maintain user pictures||Use SMW0 to upload any user pictures in the Domain Controller. Refer to the Admin Guide for further instructions on how to do this optional configuration.|
|3.4.10||Web UI: Maintain Project Phases||Use SM31 to update table /BTI/TE_PHASE in the Domain Controller to reflect the project phases that your organisation may want to reflect within the ActiveControl Web UI.|
|3.4.11||Web UI: Map Statuses to Phases||Use SM31 to update table /BTI/TE_PHASSTAT in the Domain Controller to allocate TE Deployment Statuses to Project Phases.|
|3.4.12||Web UI: Allocate Project Start/End Dates||Use SM31 to update table /BTI/TE_PRJPHASE in the Domain Controller to allocate start/end dates to the phases of each Project.|
|3.4.13||Documentation Links|| It is possible to add URL documentation links via the web UI and Windows GUI help menus to point at standard BTI or customer specific TE documentation.
These document links will then be visible via the Help menu in both the ActiveControl Windows GUI and the ActiveControl Web UI.
Document links can be maintained in the ActiveControl Domain Controller via table /BTI/TE_HLP_LINK.
|3.4.14||Lock transport naming convention||SAP transport short description sequence can be locked to force developer naming consistencies.|
|3.4.15||Automate transport Release after Unit test signoff||After approval of items at the Test Queue on target DEV and CRD, TE automatically release transports.|
Thanks for your feedback.