README.txt 4.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113
  1. ********************************************************************
  2. D R U P A L M O D U L E
  3. ********************************************************************
  4. Name: Workflow Module
  5. Author: John VanDyk
  6. Maintainers: Mark Fredrickson <mark.m.fredrickson at gmail dot com>
  7. John VanDyk drupal.org/user/2375
  8. Bastlynn http://drupal.org/user/275249
  9. Nancy Wichmann (NancyDru) http://drupal.org/user/101412
  10. Drupal: 7
  11. ********************************************************************
  12. DESCRIPTION:
  13. The workflow module enables you to create arbitrary workflows in
  14. Drupal and associate them with node types.
  15. Workflows are made up of workflow states.
  16. Moving from one state to another is called a transition.
  17. Actions are associated with transitions (actions.module was used
  18. for this in Drupal 5; core actions support is in Drupal 6).
  19. Alex Reisner introduced role-based permissions for workflow states
  20. and generally enhanced this module.
  21. ********************************************************************
  22. INSTALLATION:
  23. 1. Place the entire workflow directory into your Drupal
  24. sites/all/modules directory (or appropriate alternative).
  25. 2. Enable the workflow module by navigating to:
  26. Administer > Site building > Modules
  27. Enabling the workflow module will create the necessary database
  28. tables for you.
  29. 3. If you wish to use the administrative UI, then enable the
  30. Workflow UI module. There are several other optional modules
  31. that you may also enable, if needed.
  32. 4. If you want anyone besides the administrative user to be able
  33. to configure workflows (usually a bad idea), they must be given
  34. the "administer workflow" access permission:
  35. Administer > User management > Permissions
  36. When the module is enabled and the user has the "administer
  37. workflow" permission, a "Workflow" menu should appear in the
  38. menu system under Administer -> Site building.
  39. You may also allow only some users to schedule transitions. Select
  40. the "schedule workflow transitions" permission to allow transitions.
  41. ********************************************************************
  42. GETTING STARTED:
  43. Let's create a new workflow. Click on Administer -> Configuration ->
  44. Workflow -> Workflow and click on the "Add workflow" tab.
  45. We'll start simple. Call our workflow "Draft-Done" and click Add Workflow.
  46. Now lets add some workflow states to our workflow. Click "add state" and
  47. enter "draft" and click the Add State button. Do the same for "done".
  48. So we've got a workflow with two states, "draft" and "done". Now we
  49. have to tell each state which other states it can move to. With only
  50. two states, this is easy. Click on the "edit" link to edit the workflow
  51. and see its states.
  52. The "From / To -->" column lists all states. To the right are columns
  53. for each state. Within each cell is a list of roles with checkboxes.
  54. This is confusing. It's easiest to understand if you read rows
  55. across from the left. For example, we start with the creation
  56. state. Who may move a node from its creation state to the "draft"
  57. state? Well, the author of the node, for one. So check the "author"
  58. checkbox.
  59. Who may move the node from the "draft" state to the "done" state?
  60. This is up to you. If you want authors to be able to do this,
  61. check the "author" checkbox under the "done" state. If you had
  62. another role, say "editor", that you wanted to give the ability
  63. to decree a node as "done", you'd check the checkbox next to
  64. the "editor" role and not the author role. In this scenario authors
  65. would turn in drafts and editors would say when they are "done".
  66. Be sure to click the Save button to save your settings.
  67. Now let's tell Drupal which node types should use this workflow. Click
  68. on Administer -> Configuration -> Workflow -> Workflow. Let's assign
  69. the Draft-Done workflow to the article node type and click Save Workflow
  70. Mapping.
  71. Now we could add an action (previously configured using the trigger
  72. module). Click on the Actions link above
  73. your workflow. Add the action to the transition.
  74. Now create a new article by going to Create content -> article. If there
  75. is no sign of a workflow interface here, don't panic. The interface
  76. is only displayed if there is more than one state to which the user
  77. can move the node (why bother the user with a form with only one
  78. selection?) Click Submit to create the article.
  79. You can see the state the node is in and the history of state changes
  80. by clicking on the Workflow tab while viewing a node.
  81. Changing the state to "done" and clicking Submit will fire the action
  82. you set up earlier.
  83. ********************************************************************