source: sipes/modules_contrib/workflow/README.txt @ 6e81fb4

stableversion-3.0
Last change on this file since 6e81fb4 was 177a560, checked in by José Gregorio Puentes <jpuentes@…>, 8 años ago

se agrego el directorio de modulos contribuidos de drupal

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