eiben
Nintex Newbie

Deployment via Workflow Import

Hey there!

I just noticed, that when I open an existing workflow in O365 and I want to import an updated version of this workflow, I will not be able to save the workflow. Apparently when a workflow is being imported the workflow is treated as "new" apposed to being updated.

Of course I could "Save" the imported workflow with a different name, delete the original workflow and then rename the newly imported workflow to the original name. But that would also loose all the old workflow-history.

Anyone else experienced this?

0 Kudos
Reply
4 Replies
jasondurr
Nintex Newbie

Re: Deployment via Workflow Import

I have the same issue. Ideally, I am trying to move changes from my DEV/TEST environment into PROD, but get this issue when I try to publish.

0 Kudos
Reply
eiben
Nintex Newbie

Re: Deployment via Workflow Import

I got this behavior also confirmed by support

But there is already a uservoice-suggestion for this - so you might want to vote for this suggestion

Reimport workflow with the same name and allow overwriting (e.g. move between dev/test/prod) – Custo...

Reply
jasondurr
Nintex Newbie

Re: Deployment via Workflow Import

Thanks. I have cast my vote (x3)

Reply
Not applicable

Re: Deployment via Workflow Import

If no one has an objection, I will mark this as "assumed answered," although there's no solution.

Let me know if either of you would prefer this stays unmarked.

Thanks!

Frank

Your community manager

0 Kudos
Reply