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.
Updated: Comment #N
To be able to use Workflow, you need to create a new Field of type Workflow, and attach it to an entity.
It would be nice to be able to add a workflow to an already available property or (list) field.
See the following modules for inspiration:
List Transitions to add transitions to list fields
State Transition Control to add transitions to list fields
Entity property field to turn any property into a field.
Use some technique to attach Workflow to an existing field/property. Then, use those values to build a workflow state machine.
If the user views/changes an entity, the normal options are filtered by Workflow.
..
- Add an indicator "use this field/property in Workflow XYZ" (in Workflow or Workflow Field or in field/property)
- "workflow_get_attached_field" returns the field that contains possible values;
- "Get available states" need to call the generic read_options function to fetch them;
- "Get available states" need to filter the allowed new states, and present them to the user;
Closed: won't fix
1.0
Miscellaneous
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.