The following configuration and set-up is deemed optional and is not mandatory for running ActiveControl.
Most organisations choose not to setup some or all of these steps due to their own internal and external requirements and obligations.
| # | Activity | Details |
|---|---|---|
| 3.4.1 | Add Skipping Rules | Create Skipping Rules for the required customer scenarios, via /BTI/TE_SKIPCP. |
| 3.4.2 | Add Labels | Labels can be used to customise the text names of fields presented within ActiveControl Windows GUI to a customer’s terminology. |
| 3.4.3 | Transport auto-naming convention | SAP transport short description can be automatically generated, via /BTI/TE_TR_DESC. |
| 3.4.4 | Transport auto-release | Define if a transport automatically released after a particular Test Queue, Inbox or Outbox approval, via Windows GUI target configuration |
| 3.4.5 | Create Document Categories | Create the relevant Document Categories via /BTI/TE_ATT_CAT. |
| 3.4.6 | Documentation Links | Define any customer documentation to be accessible via Web UI and Windows GUI, via /BTI/TE_HLP_LINK. |
| 3.4.7 | Setup Configurable Analysis | Switch on the required analysis types, via Windows GUI target configuration. |
| 3.4.8a | 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. |
| 3.4.8b | Create BAK virtual target | If using Transport Backout, a virtual system called BAK needs to be created in TMS within the transport domain of the intended systems where you will run Backout. |
| 3.4.8c | Tadirdeletions parameter | If using Transport Backout, you also need to set the STMS parameter tadirdeletions = “True” in each of the intended systems where you will run Backout. |
| 3.4.9 | Add Priority Approvers | Within the Administrators and Priority Approvers tab, add in the names of any Priority Approvers deemed necessary within your organisation. Note that for most organisations, Priority Approvers will not be used for audit/compliance reasons. |
| 3.4.10 | Configure User Roles | Within the User Roles tab, create any required user roles and then allocated the required users to each one. |
| 3.4.11 | 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 Web UI. |
| 3.4.12 | 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.13a | 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.13b | Web UI: Map Statuses to Phases | Use SM31 to update table /BTI/TE_PHASSTAT in the Domain Controller to allocate Deployment Statuses to Project Phases. |
| 3.4.13c | 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. |
Post your comment on this topic.