ITRP Workflow transfer Test 2 Production


Business case

Workflows can become complex when considering different stakeholders. Customers usually want to have intuitive Self Service forms. IT teams aim to streamline their activities. Manual and time consuming tasks are low hanging fruits to gain efficiency to free up time for the customer or other more important things.

When it comes to ITRP workflows the transfer from the “” environment to the production environment (“”) is manual. Most people know that finding tiny mistakes during a manual transfer can be time consuming and annoying.


What does one ITRP based workflow usually contain?

In a more advanced form it contains the following components:

  • a Request template
  • linked to a Change template
  • linked to task templates
  • Request-, Change- and Task templates linked to UI extensions

How people approach ITRP workflow configuration:

Everything is developed / configured in the Test environment (“qa”). Components like UI extensions are getting tested during development and at the end of the cycle a couple of test cases are entered to ensure that the whole process works.

Everything is tested and works fine.

Now, the “manual” transfer starts…

and a couple of annoying and sometimes time consuming difficulties. Services, Service Instances deviate between test and production. Teams are not defined. SLA’s need to be created, modified, and the list goes on.

How does the automator help?

The automator’s latest feature lets you transfer selected workflows from production to test and from test to production. That way the environments don’t deviate that much over time. In ITRP language the automator transfers selected Request templates, Change templates and dependencies like Task templates, UI extensions etc.

Intelligence of the automator:
Before a workflow can be transferred the automator analyses the source and target environment. Whenever costs are involved (i. e. ITRP users with a role), contracts (i. e. SLA’s), or IT people could be confused (e. g. teams that do not exist in the production environment) the automator simply creates a manual “to do list” before the automated transfer can be performed. As all required dependencies are transferred additional testing in the target environment is not really necessary, it’s just to gain more confidence.


Goal reached

ITRP developers/configurators save time and can therefore spend more time with customers or refining other workflows.

List of most wanted ITRP integrations @

All the best




Leave a Reply