Learn about DokuWiki
Learn about DokuWiki
Workflow pages, which are just normal wiki pages, represent flowchart activities or process steps. Decision branches or conditionals are implemented as decision tables.
<decision payment="current,late" issue="yes,no" day="mon,tues,wed,thurs,fri"> * A very simple decision link. * some page id | A decision link with text that's different than the page ID. * another id | This link remembers a state variable called payment. +payment=late * and another | This link appears if state variable payment is late. ?payment=late * yet another | This link forgets the state variable called payment. -payment * complicated | This link does a lot. +payment=late +abc=123 -cde ?issue=no ?contract=yes ?day=mon,tues,wed </decision>
which renders to
The decision table usually goes at the bottom of a workflow page after the process documentation for that step. The user reads the workflow page, does what it tells them to do and then follows a decision link to the next step.
A decision table is surrounded by the decision tag and is a list of links to other workflow pages. Each decision link begins with two spaces and an asterisk. There are 3 parts to a decision link
* Page Name | Descriptive Text +remember=value -forget ?condition=acceptable
Usually you'll want to define specific state options and specify what values they are allowed to have. Do this by setting attributes in the decision table on the wf:start page. All attributes in the decision table on the wf:start page will be treated as state option definitions for the entire workflow system. The name of the attribute is the name of the state option. The value of the attribute is a comma separated list of values that are considered valid values for that state option.
<decision payment="current,late" issue="yes,no" day="mon,tues,wed,thurs,fri">
Any state options you define on the wf:start page will be available on every workflow page at the bottom of the decision table. You can easily search for them by typing remember or forget in the search box.
State options are only defined on the wf:start page. Do not define state options on other pages. Decision tables on other pages do not have attributes.
<decision> * some page id | A decision link with text that's different than the page ID. * another id | This link remembers a state variable called payment. +payment=late * and another | This link appears if state variable payment is late. ?payment=late </decision>
That's pretty much it. Define your state options and all your process entry links in the decision table on the wf:start page and follow those links to map out the rest of your processes.
Create the wf:start page and add a decision table to it with decision links to starting points for every process in your business. Then build out the workflow pages from there to complete each process. The wf:start page is the entry point to all your business processes.
Employees use it by starting everything they do with the wf:start page and following the decision links to complete their tasks.
Define any state options you want in the decision table on the wf:start page. Employees use state options to automatically filter out large amounts of decision links to help them find the link they need faster.
The workflow plugin helps a business document workflow in a way that employees can click through step by step in a wizard like manner, rather than having to read and memorize a daunting operations manual. It works like an interactive flowchart that users can navigate through by following decision links in the same way one would follow decision or conditional branches in a graphical flowchart.
The key to the workflow plugin is filtering the decision links so a user can quickly find the appropriate link to the next step of the process in real time, often while interacting with customers. In this way it functions as a light weight workflow automation system. It doesn't automatically do the work for you like a heavy weight workflow automation system. It provides a simple and efficient way to guide employees through your business processes in real time, quickly providing them the documentation they need to do the job correctly.
Businesses typically document their business processes in an operations manual. That's simple and fairly straight forward. Getting all the employees to read and memorize the operations manual is a whole different story. It's difficult and expensive. You have to
Hence the creation of workflow automation software which attempts to automate as much of the business execution as possible, leaving as little as possible up to employee discretion and chance. Workflow automation software is great when it's implemented well but in practice we find that is often not the case. Effective workflow automation systems are expensive and difficult to implement. Even if you don't have the means to implement workflow automation well, your company can still benefit a great deal by just automating/optimizing the documentation portion of it. If you're not going to implement an automation system that does the work for the employees, you can at least provide them a system that
You can change the namespace that the workflow pages live in. The default is wf. If you're going to change the namespace, do it before you create any workflow pages.