Easiest way to transport MDM Workflows from Dev to QA

[Former Member]

Hi gurus,

I'm trying to figure out the easiest way to trasnport our workflows from DEV to QA repository.

What I'm currently doing is manually copy and paste the workflow name, ID and parameters from DEV to QA and then when I open Visio to modify the steps I also copy and paste, but after pasting I have to manually change all the names and the appropriate assignments or validations. It's soo bad that MDM does not transport workflows...

Is there an easier way to transport a workflow from one rep to another?

Thanks,

Boris

[Former Member · Accepted solution]

Hi Boris,

In MDM 5.5 The easiest way to transport workflows is to archive and unarchive the repository. You can do this with out data too.

If this is not possible, you have to manually create them in each environment.

From MDM 7.1 you can use transport schema to move workflows from one env to another.

Hope this helps,

Regards,

Silpa

[Former Member · Accepted solution]

Hi Boris

MDM 5.5 doesnot support transport of workflows, supported in 7.1

As suggested this can be done by archive and unarhive the repository from Dev to QA.

best regards

Ravi

[Former Member]

which version of MDM are you using? This has been fixed atleast in the Latest versions of MDM7.1 and so...

thanks,

Alexander.

[Former Member]

We are using MDM 5.5 SP6 Patch 4

I'm doing it manually, but Visio is quite unstable... sometimes it doesn't save the changes, sometimes it crashes.

The most I can do is have the two systems open and the visio files tiled. Then I just copy and paste parameters...

The only good saving that works is Ctrl+S.

Best regards,

Boris

[Former Member]

Boris, typically what I do when migrating changes from development to quality is follow a procedure similar to this one:

1. a. Initial migration: archive development repository (including workflows and data)

1. b. Unarchive repository on quality system

1. c. Delete data from workflows table, main table data, check-table data, and users

1. d. Perform new data load for quality system

2. a. Delta migration: use schema transport for delta changes to data model, security roles, etc.

2. b. Manual transport for any change to workflow configuration or process

This isn't perfect, because you still have to manually transport any change to the process that you make after your initial cutover transport, but at least it cuts down on the risk of misconfiguring your workflow when you first set it up.

As has been mentioned by others in this post, MDM 7.1 / 7.2 has fixed this such that workflows can be transported with the schema migration.