Now that this issue is closed, please review the contribution record.
As a contributor, attribute any organization helped you, or if you volunteered your own time.
Maintainers, please credit people who helped resolve this issue.
So, instead of simply having the option to turn on or off a comment field with each workflow status update, I think it would be ideal to be able to setup fields for each workflow so that we could have values for check boxes, signatures, agent name, approval codes, confirmation #'s, etc. (as well as comment fields) stored with each workflow update. Of course this would also require the workflow history records to become entities, but that probably wouldn't be a bad thing.
Whether or not there's eventually some integration between Workflow, Workbench Moderation, State Machine, etc., I thought it would be good to have this issue here in the Workflow module issue queue.
Status for D7-version (updated up to #35):
- Patch #35
- Remarks in #27, #28
Status for D8-version (updated up to #35):
- #18: now supports Fieldable Workflow Transitions.
- #18: limitation: Not on the widget, only on the form (Block and the History tab)
- #18: limitation: Fields are added, but when editing a Transition, the added field cannot be changed.
- #18: todo: baseField definitions should be used, so you do not need to define them in the element.
- #18: todo: the WorkflowTransitionElement should be used.
- #26: adds the fieldability to the Workflow Widget and Workflow Form.
- #26: It still doesn't work for scheduled transitions.
Closed: outdated
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Now that this issue is closed, please review the contribution record.
As a contributor, attribute any organization helped you, or if you volunteered your own time.
Maintainers, please credit people who helped resolve this issue.