[MAGNOLIA-3290] Checkbox value is not stored in workitem Created: 03/Sep/10  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: workflow
Affects Version/s: 4.3.6
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Antti Hietala Assignee: Magnolia International
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

checkBox and checkBoxSwitch controls cannot be used in workflow activation dialogs because their value is not stored in the workitem and is not available from the workflow definition. This prevents passing of simple true/false conditions to the workflow definition.

For example, a frequently requested workflow customization is to add a "Publish immediately" checkbox on the activation dialog or a "Needs legal review" checkbox that routes the workitem to a legal team. Because of the bug this is not possible.

The root cause is a legacy workaround used in reading values from dialog control elements with JavaScript and storing them in the workitem.



 Comments   
Comment by Magnolia International [ 03/Sep/10 ]

More specifically, the problem lies in magnolia-module-workflow/src/main/resources/mgnl-resources/js-classes/mgnl/workflow/WorkflowWebsiteTree.js, which only passes non-hidden form fields to the request url; checkBoxSwitch's "real" checkbox is called fieldName_dummy, while its real value is store in an hidden with the fieldName name, for reasons dating back to MAGNOLIA-224.

(in fact, the fieldName_dummy value is indeed passed in the url, but it's always true)

Possible fixes: make that script a little smarter, either by letting it treat checkboxes differently, and/or by letting it pass all fields except mgnlSaveInfo and other technical fields.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:45:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.