Migrate Workflow Definition After Task Rename #15928
-
|
What is the recommended way to migrate/update an existing workflow definition when an existing workflow task name changes? For example, suppose the UpdateTwitterStatusTask type needs to be renamed to UpdateXStatusTask, then my existing workflow content item that uses the UpdateTwitterStatusTask will need to be updated to reference UpdateXStatusTask. Is a DataMigration the right way? I see the documentation talks about updating content types, but can content items themselves be updated in a DataMigration? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
Migrations can be used for this, yes, since this should be done automatically. You'll need to loop through all Workflow Types and update them (perhaps current running Workflow instances too). If the expected count of items here is low (for Workflow Types it is, since a large site may have like 50 workflows, but that's still a small amount) then there's nothing special to be done. If you also need to update Workflow instances, then that's harder, because there can be tens of thousands. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, @Piedone! I see something similar was done here for the Lucene search module rename. |
Beta Was this translation helpful? Give feedback.
-
|
Indeed! No problem. |
Beta Was this translation helpful? Give feedback.
Migrations can be used for this, yes, since this should be done automatically. You'll need to loop through all Workflow Types and update them (perhaps current running Workflow instances too). If the expected count of items here is low (for Workflow Types it is, since a large site may have like 50 workflows, but that's still a small amount) then there's nothing special to be done. If you also need to update Workflow instances, then that's harder, because there can be tens of thousands.