There are two inbound calls in the above scenario:

  1. Creation of the Business Task in ActiveControl
  2. Approval of Testing/Entry of test results once testing complete

Both of these calls would be web service calls to standard ActiveControl APIs (although alternative techniques are available and are described later in this document). The calling system (i.e. the ticketing system) would be responsible for queuing of messages and ensuring errors were dealt with appropriately. Some mapping may be required depending on the data passed from the ticketing system to ActiveControl for classification of the change.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment