Creating a workflow template - Revision history

Admin: /* Adding steps to the workflow template */

2019-11-17T23:15:46Z

‎Adding steps to the workflow template

2019-05-27T21:55:57Z

‎Creating a workflow template and choosing its general features

2017-03-19T23:31:21Z

‎Creating a workflow template and choosing its general features

2017-03-19T23:30:28Z

‎Creating a workflow template and choosing its general features

2017-03-19T23:29:04Z

‎Creating a workflow template and choosing its general features

2017-03-19T23:28:34Z

‎Creating a workflow template and choosing its general features

2017-03-19T23:25:15Z

‎Creating a workflow template and choosing its general features

2017-03-19T23:23:57Z

‎Creating a workflow template and choosing its general features

2017-03-19T23:19:37Z

‎Creating a workflow template and choosing its general features

2017-03-19T23:03:43Z

‎Adding steps to the workflow template

@@ Line 46: / Line 46: @@
 {{ListWorkflowModules|}}
 {{Note|The [[Context module]] cannot explicitly be added to a workflow. Instead, it is automatically added at the beginning of all workflows.|NoteWithImage}}
-{{Note|To ensure meaningful workflows, the following restrictions have been placed on the design of workflow templates:
 |-

@@ Line 35: / Line 35: @@
 |-
 |class="StepNum" | 6.
-|Check the box to Enable a distribution list and then enter email addresses by clicking below the box.
+|Check the box to Enable a distribution list and then enter email addresses by clicking on the plus symbol.
 |}

@@ Line 36: / Line 36: @@
 |class="StepNum" | 6.
 |Check the box to Enable a distribution list and then enter email addresses by clicking below the box.
-{{Issue|Enable distribution list allows one or more email addresses to be entered to allow emailing of a completed workflow summary after submission of the workflow. However due to Operating System limitations the workflow summary may be too large for this to successfully function. If it fails to send it does so with no error message or other indication that it has not worked |IssueNoImage|64|Mar.19, 2017}}
+{{Issue|Enable distribution list allows one or more email addresses to be entered to allow emailing of a completed workflow summary after submission of the workflow. However due to Operating System limitations the workflow summary may be too large for this to successfully function. If it fails to send it does so with no error message or other indication that it has not worked. |IssueNoImage|64|Mar.19, 2017}}
 |}

@@ Line 36: / Line 36: @@
 |class="StepNum" | 6.
 |Check the box to Enable a distribution list and then enter email addresses by clicking below the box.
 {{Issue|Enable distribution list allows one or more email addresses to be entered to allow emailing of a completed workflow summary after submission of the workflow. However due to Operating System limitations the workflow summary may be too large for this to successfully function. If it fails to send it does so with no error message or other indication that it has not worked |IssueNoImage|64|Mar.19, 2017}}
 |}

@@ Line 33: / Line 33: @@
 * They determine that previously entered & shared observations are pulled into the workflow in the [[Observations module]]. Only previously entered and shared observation that fall under the hierarchy of the specified location(s) are shown within a workflow.}}
 {{Note|For the majority of users, associating their workflows with their entire [[Location_types_and_symbology#OperationArea|operation area]] (the top parent of your [[Location hierarchy]]) will be the best setup. Only operations with multiple, distinct forecast regions (e.g., consulting companies, highway and railway forecasting operations) will find it meaningful to associate workflows with forecast areas or operating zones.}}
 |-
 |class="StepNum" | 6.
 |Check the box to Enable a distribution list and then enter email addresses by clicking below the box.
 |-
 |}

← Older revision		Revision as of 23:28, 19 March 2017
Line 35:		Line 35:

	{{Issue\|Enable distribution list allows one or more email addresses to be entered to allow emailing of a completed workflow summary after submission of the workflow. However due to Operating System limitations the workflow summary may be too large for this to successfully function. If it fails to send it does so with no error message or other indication that it has not worked \|IssueNoImage\|64\|Mar.19, 2017}}		{{Issue\|Enable distribution list allows one or more email addresses to be entered to allow emailing of a completed workflow summary after submission of the workflow. However due to Operating System limitations the workflow summary may be too large for this to successfully function. If it fails to send it does so with no error message or other indication that it has not worked \|IssueNoImage\|64\|Mar.19, 2017}}
		+	\|-
		+	\|class="StepNum" \| 6.
		+	\|Check the box to Enable a distribution list and then enter email addresses by clicking below the box.
		+	\|-
	\|}		\|}

@@ Line 34: / Line 34: @@
 {{Note|For the majority of users, associating their workflows with their entire [[Location_types_and_symbology#OperationArea|operation area]] (the top parent of your [[Location hierarchy]]) will be the best setup. Only operations with multiple, distinct forecast regions (e.g., consulting companies, highway and railway forecasting operations) will find it meaningful to associate workflows with forecast areas or operating zones.}}
-{{Issue|Enable distribution list allows one or more email addresses to be entered to allow emailing of a completed workflow summary after submission of the workflow. However due to Operating System limitations the workflow summary may be too large for this to successfully function.}}
+{{Issue|Enable distribution list allows one or more email addresses to be entered to allow emailing of a completed workflow summary after submission of the workflow. However due to Operating System limitations the workflow summary may be too large for this to successfully function. |IssueNoImage|64|Mar.19, 2017}}
 |}

@@ Line 62: / Line 62: @@
 |class="StepNum" | 5.
 |Repeat steps 1 to 4 until you have created your entire workflow.
-{{Note|A [[Context module]] is automatically added at the beginning of any workflow that includes a data submitting module.}}
+{{Note|A [[Context module]] is automatically added at the beginning of all workflows.}}
 |-
 |class="StepNum" | 6.