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

Core Workflows Fix for #5002 #5003

Closed
wants to merge 3 commits into from
Closed

Conversation

bahusafoo
Copy link

Created method merge_changes_into_restrict_values to resolve cases where perform_result does not have some of the submitted data while being passed to CoreWorkflow.perform(). This resolves an issue encountered when core workflows remove groups, and then add them back to the group selection object later on.

Created method merge_changes_into_restrict_values to resolve cases where perform_result does not have some of the submitted data while being passed to CoreWorkflow.perform().  This resolves an issue encountered when core workflows remove groups, and then add them back to the group selection object later on.
Created method merge_changes_into_restrict_values to resolve cases where perform_result does not have some of the submitted data while being passed to CoreWorkflow.perform(). This resolves an issue encountered when core workflows remove groups, and then add them back to the group selection object later on.
Modifying return line to make validator workflow happy :)
@dominikklein dominikklein changed the title Core Workflows Fix Core Workflows Fix for #5002 Jan 11, 2024
@bahusafoo
Copy link
Author

Code works nicely with any of these commits Checks seem to not like the use of "do unless " syntax - changed to use if not syntax instead.

@rolfschmidt
Copy link
Collaborator

Hi @bahusafoo ,

normally the concern is only the bridge between the core workflow engine and the rails model. I think the real reason for this issue is that there was no rerun for the group after the option was re-enabled so it was still restricted and did not recover the original state. But thank you very much for your encouragement :) Hopefully it will work for you too when it gets merged to stable soon. If not feel free to create a new issue with steps for reproduction.

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

Successfully merging this pull request may close these issues.

None yet

2 participants