Actions and workflows
Moderators: Matt Westgate/John VanDyk
Now that we have the ability to create Drupal actions and workflows, it's time for a paradigm shift. Aren't configurable actions a lot like forms with stored procedures? Aren't workflows (moving through a series of states) a lot like a wizard path of execution? Why don't we glue them together with CCK to make a configurable wizard wizard (sic)? As you can see, we have more questions than answers.
Who said that workflows need to be restricted to nodes? We hope to map out a course that will introduce workflows to the user and comment lifecycle as well. And we need to plan how to move from Drupal's current checkbox-based "workflow" settings to the real thing.
Because so many people have signed up for this session, we plan to divide the time into an initial 5-minute overview of actions and workflows followed by smaller working groups focusing on the following topics:
MIGRATION STRATEGY WORKING GROUP
Currently Drupal has a hardcoded two-state workflow (unpublished to published). How do we get from current code to workflow-in-core? What does the new workflow system look like? Core currently uses checkboxes for node options, but workflow uses a drop-down field. Can we have both? What are the usability issues surrounding this?
Outcome: a strategic plan with defined milestones.
ACTIONS WORKING GROUP
Go through Drupal's core modules and enumerate the possible actions we need to write, then write the actions. Examples:
- blocking a user (user.module)
- creating a node (node modules, focus on CCK)
- sending a ping (ping.module, drupal.module)
- enabling a block (block.module)
- changing a workflow state (workflow.module) eek! recursion!
Outcome: a list of actions for each module.
FORMS INTEGRATION WORKING GROUP
Develop plans to use the workflow engine to drive form-based wizards.
Outcome: description of the approach.
ACTION API WORKING GROUP
What is the lifecycle of an action? Do we need batchable actions? How do we solve the recursion issue? What about branches and looping?
Outcome: a refined actions API.
PERMISSIONS AND WORKFLOWS WORKING GROUP
How do workflows integrate with access control?
Outcome:enumeration of different approaches to the problem.
PREPARATION
To be prepared to participate in this session, you should
- Grab a copy of HEAD
- Install the cvs versions of actions and workflow modules
- Watch the FOSDEM 2005 video where John VanDyk presents actions and workflows if you are unfamiliar with the concepts (video is at homepage.mac.com/drupal/drupalconf-workflow.ogg and requires something like VLC)
- Get familiar with the new Form API