The ActiveControl ChaRM integration is fairly unique in its setup, in that the integration is primarily based at a transport level and not a ticket/business task level as is the case of most other ActiveControl integrations with 3rd-Party ITSM systems.
The following were the customer requirements against which the ChaRM integration was initially built. This information is included in this Administration Guide as a way of illustrating what is possible with the current ActiveControl/ChaRM integration:
| Requirement | Details |
|---|---|
| 1. | ActiveControl should automatically create a Business Task at the point a ChaRM Change Request reaches a specific (configurable) status. |
| 2. | ActiveControl should automatically create a Transport Form for every new SAP transport created in ChaRM. |
| 3. | The Transport Form should be created as soon as SAP transport first created by ChaRM. |
| 4. | Only Workbench and Customising transports should have a Transport Form created for them. All Transport of Copies created by ChaRM, and all Merge TOCs created by ActiveControl should NOT have a Transport Form created for them as part of the Integration. |
| 5. | The Transport Form should be automatically linked to the appropriate Business Task. |
| 6. | If decoupling happens on ChaRM side because decision taken not to move to Production, then the corresponding Transport Form(s) should be automatically re-assigned to a different {configurable) Business Task. |
Post your comment on this topic.