Workflow Step Types
General
There are 9 types of workflow steps that are supported in holo|one sphere. These are:
Description only steps
Single choice steps
Multiple choice steps
Numeric input steps
Text input steps
Barcode input steps
Photo input steps
Audio input steps
Video input steps
Most steps require some kind of input in order to proceed. For example, you may want the user to capture a photo of the completed task so that it can be kept in record for traceability, compliance, and verification purposes. All answers provided for steps are recorded and will show up in the report for completed workflows.
Each step, regardless of its type, will contain some common elements:
Title - a short title for the step
Description - a description or set of instructions for the step
Optional Step - set this to true if the the step is optional and can be skipped without completing, by default all steps are mandatory
Supporting Holograms - relevant holograms can be attached to the steps to provide further help, support, and context
Step Types
Description Steps
Description steps are the simplest step type and do not require any explicit input or answer. They simply provide a description of the work to be done and it is left up to the user to perform them.
Single choice steps
Note: single choice steps can be used to support branching and conditional Workflows
Single choices steps require the user to select a certain option in order to proceed. These options are defined when the Workflow step is created. Options and can be added, updated, and deleted and be listed in a specific order. Each option contains the following information:
The name/title of the option
The next step that is associated with the option
Multiple choice steps
Multiple choice steps allow the user to select several options that are listed as an answer/response to a step. Users must select at least one option in order to proceed. These options are defined when the Workflow step is created. Options and can be added, updated, and deleted and be listed in a specific order.
Unlike, single choice steps multiple choice steps do not support branching and conditional Workflows. Their purpose is for information gathering, rather than determining subsequent steps to be performed. If you need to support branching and conditional flow, consider using several chained single choice steps.
Numeric input steps
Note: numeric input steps can be used to support branching and conditional Workflows
Numeric input steps require the user to input a number or numeric value as their answer/response to a step. During Workflow execution, the user must not only enter an answer, but this answer must also be within the allowed response ranges.
Similar to single choice steps, numeric input steps can be used to support branching/conditional Workflows based on options. Options and can be added, updated, and deleted. In the case of numeric steps, each option contains the following information:
The name/title of the option (this is not displayed on application clients)
Minimum permitted value
Maximum permitted value
The next step that is associated with the option
However, unlike single choice options, numeric options are not displayed to the user and answers are collected as exact input, and not the discretized range the fall in.
Text input steps
Text input steps are very simple steps. On application clients, they look similar to numeric input steps but the answer is not restricted to only numeric input values. Unlike numeric input steps though, they do not support branching/conditional workflows and are for information gather purposes only.
Barcode input steps
Barcode input steps require the user to scan a barcode as their answer/response. The user cannot input the values of the barcode directly, but rather uses the camera to capture the barcode. Users must have a camera attached to their device, otherwise this step will not work.
In addition to scanning the code, Workflow authors have the ability to specify a comparison text/string when creating the step. This ensures that the correct barcode is scanned before proceeding by comparing the scanned code with the expected output. This is optional and not mandatory for barcode input steps.
Physical sizes of the codes should be rather large in order to be picked up by headset cameras. We recommend at least 10cm in width to be readable from 0.5-1 meter away. For very dense codes with lots of information, the physical size will need to be larger or read from closer up.
1-D code formats supported
UPC-A, UPC-E, EAN-8, EAN-13, Code 39, Code 93, Code 128, ITF, Codabar, MSI, RSS-14
2-D code formats supported
QR Code, Data Matrix, Aztec and PDF-417
Photo input steps
Photo input steps require the user to capture a photo from the device camera, for example of their completed work, as the answer/response to the step.
Additionally, Workflow authors can specify a comparison image to attach to the photo input step. This comparison image can be used as a reference for the on-site user to compare their work and their captured photo to, in order to ensure they have completed the step correctly.
Users must have a camera attached to their device, otherwise this step will not work.
Audio input steps
Audio input steps require the user to capture a voice memo as input to the Workflow step. Users must have a microphone attached to their device, otherwise this step will not work.
Video input steps
Video input steps require the user to capture a video as input to the Workflow step. Users must have a camera attached to their device, otherwise this step will not work.