nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Upgrading deployed workflow tasks to the new version

epaquette75

Is there a way to upgrade deployed workflow tasks to the new version of the workflow. I don't want to use multiple versions of the same workflow.

For example, if the deployed workflow pattern goes like:

A -> B -> C

I would like to upgrade the deployed tasks so that it goes:

A -> C -> D

where B tasks would go to A or C using to new version of the workflow.

Thanks in advance

Find more posts tagged with

Comments

davidc

Not automatically. It requires a manual migration of the workflow instance data to suit your new workflow definition which is probably quite dangerous.

Do you really need to change the definition of an in-flight process??

epaquette75

We have documents that may be in the workflow for many months. Sometimes policies change on how they are to be processed. If the policies grandfather the existing documents, then leaving them in the older workflow version is fine. However, the policies may very well dictate that they be moved to the new flow and continue through it. We need to be prepared for that situation so that we can support it.

Could you give me a bit more detail about what the manual migration would entail? Is that something that we would have to write <Java> code to do? Can you easily search the repository for all documents connected to a given workflow instance?