Avalanche control module - Revision history

Admin at 16:51, 10 November 2017

2017-11-10T16:51:51Z

Admin: /* Functionality */

2017-05-30T19:23:50Z

‎Functionality

Admin at 21:58, 29 May 2017

2017-05-29T21:58:06Z

Admin: /* Information shared within InfoEx */

2017-05-29T21:56:45Z

‎Information shared within InfoEx

Admin: /* Information shared within the InfoEx */

2017-05-29T21:56:18Z

‎Information shared within the InfoEx

Admin: /* 2) Avalanche Control workflow module settings */

2017-05-29T21:55:53Z

‎2) Avalanche Control workflow module settings

Admin: /* 2) Avalanche Control workflow module settings */

2017-05-29T21:54:12Z

‎2) Avalanche Control workflow module settings

Admin: /* Settings */

2017-05-29T21:46:51Z

‎Settings

Admin: /* Settings */

2017-05-29T21:46:22Z

‎Settings

Admin: /* Settings */

2017-05-29T21:46:00Z

‎Settings

@@ Line 1: / Line 1: @@
 __NOTOC__
-{{Requirements|UserLevel=Submission Moderator and higher|Connectivity=Online and partial offline}}
+{{Requirements|UserLevel=Submission Moderator and higher|Connectivity=Online and offline}}
 {{Note|The avalanche control workflow module is not included in the regular InfoEx subscription fees. An additional subscription is required to use this functionality|NoteWithImage}}
@@ Line 10: / Line 10: @@
 '''Required connectivity:'''
 * You need to be online to create a new or edit an existing [[Definitions#WorkflowTemplate|workflow template]].
-* You need to be online to initiate a [[Definitions#WorkflowInstance|workflow instance]] for the fields to be properly prefilled from the last workflow instance with the same location(s). Once the workflow instance has been loaded, you can complete the workflow in an offline mode.
+* If you are online when you initiate a [[Definitions#WorkflowInstance|workflow instance]] the fields will be prefilled from the last workflow instance with the same location(s). Once the workflow instance has been loaded, you can complete the workflow in an offline mode.
-* You can initiate a [[Definitions#WorkflowInstance|workflow instance]] when you are offline, but none of the fields will be prefilled and you will start with a completely blank copy.
+* You can initiate a [[Definitions#WorkflowInstance|workflow instance]] when you are offline, and the fields will be filled with the latest cached information on the computer. This will be up to date unless workflows have been submitted using other computers since you were last online on the computer you are currently using.
-* You need to be online to submit your workflow.
+* If you submit whilst offline the workflow will be uploaded to the InfoEx server the next time you are online. WARNING: If the internet connection is lost whilst this is being done, the workflow will not be submitted and you will lose the data.
 ==Functionality==

@@ Line 19: / Line 19: @@
 * manage their control routes,
 * assign routes to patrol teams during the daily forecasting routine, and
-* have patrol leaders subsequently enter their control results efficiently
+* have patrol leaders subsequently [[Avalanche control|enter their control results]] efficiently
 The use of explosives requires significant paperwork that can result in multiple data entries (e.g., explosives inventory, stabilization record, occurrence sheet, InfoEx submission). The avalanche control extension aims to streamline this process and provide a central data entry location for this information. The existing report functionality can then be used to create dynamic reports for various purposes.

← Older revision		Revision as of 21:58, 29 May 2017
Line 2:		Line 2:
	{{Requirements\|UserLevel=Submission Moderator and higher\|Connectivity=Online and partial offline}}		{{Requirements\|UserLevel=Submission Moderator and higher\|Connectivity=Online and partial offline}}

−	~~{{New2014-15\|This document describes the functionality of the 'avalanche control' workflow module and how to properly configure it for a workflow.\|NewWithImage}}~~
	{{Note\|The avalanche control workflow module is not included in the regular InfoEx subscription fees. An additional subscription is required to use this functionality\|NoteWithImage}}		{{Note\|The avalanche control workflow module is not included in the regular InfoEx subscription fees. An additional subscription is required to use this functionality\|NoteWithImage}}

@@ Line 76: / Line 76: @@
 ==<span style="color: #CC0000;">Information shared within InfoEx</span>==
-All of the information entered in this workflow module is stored on the InfoEx server however it is proprietary information and not shared within the InfoEx subscriber community.
+All of the information entered in this workflow module is stored on the InfoEx server however it is proprietary information and not shared.
 ==Other workflow modules==

@@ Line 75: / Line 75: @@
 * '''Control routes'''<br/>Specify the order of the control routes in the workflow step. To change the order of the control routes, click and hold the handle on the right of the grey bar (two horizontal dashes) and drag and drop to the desired location within the list.
-==<span style="color: #CC0000;">Information shared within the InfoEx</span>==
+==<span style="color: #CC0000;">Information shared within InfoEx</span>==
 All of the information entered in this workflow module is stored on the InfoEx server however it is proprietary information and not shared within the InfoEx subscriber community.

@@ Line 65: / Line 65: @@
 ===2) Avalanche Control workflow module settings===
-The run list workflow module settings are completed each time the run list module is included in a workflow. It has the following settings (Fig. 3):
+The avalanche control workflow module settings are completed each time the avalanche control module is included in a workflow. It has the following settings (Fig. 3):
 * '''Name'''<br/>Name of the workflow step shown in the header of the workflow. It is recommended that you choose a short name to keep the navigation bar of the workflow as tidy as possible.
-* '''Pre-fill with last status assessment'''<br/>Check this box to have the run lists pre-filled with the last assessment that was previously submitted to the server by default.
+* '''Include Forecasted size/trigger?'''<br/>Check this box to include a free text field with this title in the workflow step.
-* '''Historic report'''<br/>Select the report template that should be associated with the history button of each location included in the run list. The historic report in the run list will be automatically be filtered by the location of the run.
+* '''Historic report'''<br/>Select the report template that should be associated with the history button of each control route location. The historic report will be automatically filtered to include the avalanche paths for the selected control route.
-* '''Filter location types'''<br/>Specify the types of locations that should be included in the run list. It is possible to select multiple location types.
+* '''Control routes'''<br/>Specify the order of the control routes in the workflow step.
 * '''Group by'''<br/>Select how the locations should be grouped in the run list. The options are:

@@ Line 58: / Line 58: @@
 ==Settings==
-[[File:Avalanche_Control_Workflow_Settings.png|300px|thumb|right|Fig. 3: Run list workflow module settings]] There are two sets of configuration settings for the avalanche control extension. One of them is accessed via Operation Settings (from the cogwheel menu) and the other using Manage Workflow Definitions (from the Workflows menu). The Operation Settings only affects Control Route Avalanche Observation entry which is used to record results after field operations. The configuration in Manage Workflow Definitions only affects the Avalanche Control workflow module used for planning prior to field operations:
+[[File:Avalanche_Control_Workflow_Settings.PNG|300px|thumb|right|Fig. 3: Run list workflow module settings]] There are two sets of configuration settings for the avalanche control extension. One of them is accessed via Operation Settings (from the cogwheel menu) and the other using Manage Workflow Definitions (from the Workflows menu). The Operation Settings only affects Control Route Avalanche Observation entry which is used to record results after field operations. The configuration in Manage Workflow Definitions only affects the Avalanche Control workflow module used for planning prior to field operations:
 ===1) Avalanche Control configuration===