Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PI Migration - Active Call activity/Sub process - Pre script/Post script update (Improvement) #1985

Open
madhurrya opened this issue Jul 24, 2024 · 1 comment

Comments

@madhurrya
Copy link
Contributor

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)

@essweine
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: New Issue
Development

No branches or pull requests

2 participants