Difference between revisions of "Workflow overview"
Jump to navigation
Jump to search
(Created page with "__NOTOC__ {{Requirements|UserLevel=Operation administrator and higher|Connectivity=Online and partial offline}} This document describes the purpose and use of workflows in th...") |
|||
Line 2: | Line 2: | ||
{{Requirements|UserLevel=Operation administrator and higher|Connectivity=Online and partial offline}} | {{Requirements|UserLevel=Operation administrator and higher|Connectivity=Online and partial offline}} | ||
− | This document describes the purpose and use of workflows in the | + | This document describes the purpose and use of workflows in the InfoEx system. |
==Background== | ==Background== | ||
− | Workflows link together tasks that assist | + | Workflows can be used to link together tasks that assist InfoEx users to view and record weather, snowpack and avalanche observations. Depending on the type of workflow selected, workflows can be used to: |
* Organize and view data by a single user | * Organize and view data by a single user | ||
* View, organize and share information within an operation | * View, organize and share information within an operation | ||
− | * View, organize and share information with the | + | * View, organize and share information with the InfoEx community by submitting the results of a workflow to the InfoEx server |
+ | |||
Workflow templates are created by users with operation administrator privileges or higher. | Workflow templates are created by users with operation administrator privileges or higher. | ||
+ | |||
==Details of: Workflow purpose and use == | ==Details of: Workflow purpose and use == | ||
Line 47: | Line 49: | ||
*[[Deleting a workflow template]] | *[[Deleting a workflow template]] | ||
*[[Editing a workflow template]] | *[[Editing a workflow template]] | ||
− | + | ||
− | + | '''Workflow modules''' | |
+ | *'''Module with data submission''' | ||
**[[Context module]] | **[[Context module]] | ||
**[[Observations module]] | **[[Observations module]] | ||
Line 54: | Line 57: | ||
**[[Hazard assessment - simple module]] | **[[Hazard assessment - simple module]] | ||
**[[Hazard assessment - detail module]] | **[[Hazard assessment - detail module]] | ||
− | + | *'''Modules without data submission''' | |
**[[Webpage module]] | **[[Webpage module]] | ||
**[[Report module]] | **[[Report module]] | ||
+ | |||
'''Using workflows''' | '''Using workflows''' | ||
*[[Starting a workflow instance]] | *[[Starting a workflow instance]] | ||
Line 62: | Line 66: | ||
==Functionality tested by== | ==Functionality tested by== | ||
− | * | + | * Nov. 15, 2013: John Kelly |
− | [[Category:Workflows]] | + | [[Category:Super User]][[Category:Operation Administrator]][[Category:Workflows]][[Category:Version3.4.0]] |
Revision as of 11:44, 23 December 2013
REQUIREMENTS | |
Permission | Operation administrator and higher |
Connectivity | Online and partial offline |
This document describes the purpose and use of workflows in the InfoEx system.
Background
Workflows can be used to link together tasks that assist InfoEx users to view and record weather, snowpack and avalanche observations. Depending on the type of workflow selected, workflows can be used to:
- Organize and view data by a single user
- View, organize and share information within an operation
- View, organize and share information with the InfoEx community by submitting the results of a workflow to the InfoEx server
Workflow templates are created by users with operation administrator privileges or higher.
Details of: Workflow purpose and use
Workflows can be used in two basic ways:
1. | To retrieve specified information for viewing.
| ||||
2. | To submit information, in a guided process, that will be available for other users. Users have the option of sharing the information within their operation, or forwarding the information to the infoEx server and hence the entire infoEx community.
|
Related documents
Workflow administration
Workflow modules
- Module with data submission
- Modules without data submission
Using workflows
Functionality tested by
- Nov. 15, 2013: John Kelly