Context module

REQUIREMENTS
Permission	Operation administrator and higher
Connectivity	Online and partial offline

This document describes the purpose of a 'context' step in a workflow, and how to set one up.

This document describes the functionality of the 'snowpack' workflow module and how to properly configure if for a workflow.

Required permissions:

• You need to be a Operation administrator to create a workflow template.
• You need to be a Submission moderator to initiate a workflow instance.

Functionality

A 'context' step provides background information about a workflow including information on when each instance of the workflow was executed, the span of validity of the information entered during its execution and information on who participated in the workflow session.

Layout

Fig. 1: Context workflow module at the beginning of a workflow with data submission.

Settings

Fig. 2: Workflow 'context' settings

The context workflow module has the following settings (Fig. 2):

• Name
  Name of the workflow step shown in the header of the workflow. It is recommended that you choose a short name (e.g., 'Ldg Wx' instead of 'Lodge Weather') to keep the navigation bar of the workflow as tidy as possible.

Details of: The context step and the information required to set one up

Context:

Fig. 2: Workflow 'context' settings A 'context' step provides information about the workflow itself and offers a place to record the following information: The name of the context step (frequently 'Context for [workflow name]'). This provides a name for this step as the user moves through the workflow. The type of workflow. Only two selections are possible: Nowcast (the context refers to conditions at the present moment); Forecast (the context refers to future conditions). The 'Valid Until' date (This is the future date that the workflow is valid until). The default future date is selected by the person who creates the workflow and applies to all workflows of this type. The 'Valid Until' time (This is the time of day on the future date that the workflow is valid until.) The default time is selected by the person who creates the workflow. NOTE All context steps will automatically provide a field to record when the workflow was run and who attended the workflow session. NOTE The date and time of validity can be changed when the workflow is run.

Other workflow modules

• Modules for entering data that is shared among InfoEx subscribers
  • Observations module
  • Snowpack module
  • Hazard assessment module
  • Hazard comment module
• Modules for entering proprietary data
  • Free form module
  • Run list module (additional subscription required)
  • Avalanche control module (additional subscription required)
• Modules for viewing information
  • Report module
  • Webpage module
• Other modules
  • Context module
  • Workflow summary

Functionality tested by

• Dec. 24, 2013: Pascal Haegeli