You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a Call activity or a Sub process is active, if we change it's pre script/post script/instructions then we can't migrate it.
Jason has mentioned here #1907 that is how it is designed.
Alex asked to add this for discussion as it might be better to support them (specially post-script aspect)
The text was updated successfully, but these errors were encountered:
I commented here about some of the issues related to this: #1973 (comment)
Prescript and postscript changes would fall into the second (dangerous category). They affect the semantics (for lack of a better word) of a workflow. Since they affect the data coming into and out of a task, it is definitely not safe to to allow migrations after the subworkflow has started running. It's just not going to be possible for the application to know whether the changes matter because they depend on the specific changes to the scripts and potential changes to the subworkflow itself.
If a Call activity or a Sub process is active, if we change it's pre script/post script/instructions then we can't migrate it.
Jason has mentioned here #1907 that is how it is designed.
Alex asked to add this for discussion as it might be better to support them (specially post-script aspect)
The text was updated successfully, but these errors were encountered: