Note: This is issue is part of #2721129: Workflow Initiative and is only meant for planning and governance sign-offs. Work will happen in child issues of this plan.
Target version: Drupal 8.4
The proposal here is to add a Workflows experimental module into core.
The purpose of this is to:
- Separate workflow functionality from the content_moderation module so that is it not tied to moderating content and can be used for other purposes
Proposed module name: Workflows (workflows.module)
Implementation
Required sign-off before commit
Sign offs occurred in #2779647: Add a workflow component, ui module, and implement it in content moderation
Required before stable release
Must-have
- #2830740: Allow workflow types to lock certain changes to workflows once things are in use
- #2843785: EntityResource: Provide comprehensive test coverage for Workflow entity
- #2849827: Move workflow "settings" setters and getters to WorkflowTypeInterface
#2830736: Add indication of where workflow is being used to workflow edit form#2830737: Add link to workflow on bundle edit screen- #2830739: Discuss whether content moderations actions should be on the state or transition level
- #2830581: Fix ContentModeration workflow type to calculate correct dependencies
Should-have
- #2830584: Implement unified workflow UI
- #2758623: Redesign workflow configuration page to better visually describe the flow
- #2877926: Move buildStateConfigurationForm/buildTransitionConfigurationForm to WorkflowTypeFormInterface.
Could-have
#2830735: Add possible but not existent transitions to the state edit form- #2830741: Decide if the workflow type should be able to rename the labels "State/Place" and "Transition" so it can call them what they like
- #2835545: Provide a Workflow FieldType that references a workflow entity and tracks the current state of an entity (optionally make content_moderation use this field type)
Won’t-have (for this feature)
- TBD
Other related discussions
Sign-offs needed
Product manager
A product manager needs to sign-off on this plan as the above phases are required as part of a planned initiative.
Framework manager
A framework manager needs to sign-off on this plan as the above phases introduces major API additions (archive and purge).
Release manager
A release manager needs to sign-off on this plan as the above phases have impact on shippability.
Sub-system maintainers
The sub-system maintainers for the Entity API needs to sign-off on this plan as it significantly impacts the Entity API.