Importing workflows – Configuration IDs

7 09 2010

I have just been doing some exporting and importing of workflow configurations from one company account into another and noted something possibly expected, yet strange.

When importing, the new workflow configuration that is created maintains the configuration id that existed in the company that the workflow was exported out of, instead of allocating a new configuration id. If the number sequences are the similar e.g ####_200 in both systems then there shouldn’t be to much of an issue, however if the number sequences are quite unique per company your configuration ids may be become inconsistent. In our case the number sequences contain a different suffix per company e.g ####_200CEE and ####_200CEU.

I’m not sure if I would classify this as a bug or desired functionality, but it is definitely something to take note of when doing imports and exports.




Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: