Difference between revisions of "Observations module"
Jump to navigation
Jump to search
m |
m (→The Observations step and the information required to set one up) |
||
Line 6: | Line 6: | ||
An observations step provides an opportunity to enter a custom set of observations during the course of the workflow. | An observations step provides an opportunity to enter a custom set of observations during the course of the workflow. | ||
− | ==The Observations step and the information required to set one up== | + | ==Details of: The Observations step and the information required to set one up== |
{|class="TblSteps" | {|class="TblSteps" |
Revision as of 14:48, 16 November 2013
REQUIREMENTS | |
Permission | Operation administrator and higher |
Connectivity | Online and partial offline |
This document describes the purpose of an Observations step in a workflow, and how to set one up.
Background
An observations step provides an opportunity to enter a custom set of observations during the course of the workflow.
Details of: The Observations step and the information required to set one up
Observations: | An 'observation' step allows you to fill out a customized observation as part of the workflow. The following information is required to set it up:
|
Functionality tested by
- Date: Nov. 15, 2013 / John Kelly / QA Server / Version 3.0.0