plugin:workflow
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| plugin:workflow [2014-01-01 07:50] – [Why do we need a plugin for this?] ryan.boder | plugin:workflow [2023-09-12 14:11] (current) – [workflow Plugin] SPD | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| type : syntax | type : syntax | ||
| lastupdate : 2013-12-29 | lastupdate : 2013-12-29 | ||
| - | compatible : Binky | + | compatible : Binky, Greebo, "!Jack Jackrum" |
| depends | depends | ||
| - | conflicts | + | conflicts |
| similar | similar | ||
| - | tags : workflow automation, flowchart | + | tags : workflow automation flowchart |
| - | downloadurl: | + | downloadurl: |
| - | bugtracker : http:// | + | bugtracker : |
| - | sourcerepo : http:// | + | sourcerepo : #http:// |
| - | donationurl: | + | donationurl: |
| - | screenshot_img : http://rutobo.suretycam.net/ | + | screenshot_img : https://trello.com/ |
| ---- | ---- | ||
| ===== Installation ===== | ===== Installation ===== | ||
| - | Install | + | Search and install |
| ===== Examples/ | ===== Examples/ | ||
| Line 42: | Line 42: | ||
| which renders to | which renders to | ||
| - | {{http://rutobo.suretycam.net/ | + | {{https://trello.com/ |
| 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. | 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. | ||
| Line 68: | Line 68: | ||
| 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 // | 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 // | ||
| - | {{http://rutobo.suretycam.net/ | + | {{https://trello.com/ |
| 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. | 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. | ||
| Line 81: | Line 81: | ||
| 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. | 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. | ||
| + | |||
| ===== Getting Started ===== | ===== Getting Started ===== | ||
| Line 113: | Line 114: | ||
| ===== Why do we need a plugin for this? ===== | ===== Why do we need a plugin for this? ===== | ||
| - | At first we tried to do this using regular wiki syntax. The problem was that in any given situation it was difficult to find the next step quickly. If we keep the number of decision links on any particular page small and manageable then we don't cover all the possible decision points that occur in a real life business. On the other hand, if we really do include all the possible decision points in any given situation then quickly finding the next step, especially with the customer on the line, takes too long. The workflow plugin provides a way to efficiently manage and find the appropriate decision link on the fly by filtering them based on the known state of the current situation and by what the user types. Next steps (decision links) are automatically filtered out if they dont apply to the current context, the known state, of the situation. The user can then quickly search through the remaining valid decision links to find the next step just by typing. The search is performed in javascript as they type. | + | At first we tried to do this using regular wiki syntax. The problem was that in any given situation it was difficult to find the next step quickly. If we keep the number of decision links on any particular page small and manageable then we don't cover all the possible decision points that occur in a real life business. On the other hand, if we really do include all the possible decision points in any given situation then quickly finding the next step, especially with the customer on the line, takes too long. The workflow plugin provides a way to efficiently manage and find the appropriate decision link on the fly by filtering them based on the known state of the current situation and by what the user types. Next steps (decision links) are automatically filtered out if they don' |
| ===== Configuration and Settings ===== | ===== Configuration and Settings ===== | ||
| - | You can change the namespace that the workflow pages live in. The default is wf. | + | 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. |
| ===== Development ===== | ===== Development ===== | ||
| Line 125: | Line 126: | ||
| === Change Log === | === Change Log === | ||
| - | * **2013-12-29** | + | * **2014-01-05** |
| - | * Initial release | + | * Added box and button |
| * **2013-12-31** | * **2013-12-31** | ||
| * Added state option definitions | * Added state option definitions | ||
| + | * **2013-12-29** | ||
| + | * Initial release | ||
| === Known Bugs and Issues === | === Known Bugs and Issues === | ||
| Line 143: | Line 146: | ||
| ===== Discussion ===== | ===== Discussion ===== | ||
| + | |||
plugin/workflow.1388559028.txt.gz · Last modified: 2014-01-01 07:50 by ryan.boder