Understanding Input Types & Options
- 11 May 2023
- 17 読む分
- 印刷する
- 闇光
Understanding Input Types & Options
- 更新日 11 May 2023
- 17 読む分
- 印刷する
- 闇光
The content is currently unavailable in Ja - 日本語. You are viewing the default English version.
記事の要約
この要約は役に立ちましたか?
ご意見ありがとうございます
Overview
Procedure authors can associate one or more Inputs with each augmented step. (For an overview of augmented steps, review the Augmented Steps Overview article.)
This article provides detail regarding the eight types of inputs that a procedure author can add to a procedure template. Click the name of any input type to jump to that section of the article.
- Value: Prompts the operator to record a specific text, spoken, or numerical value. This input can also reference parameter values and values pulled in from other steps.
- Measure: Prompts the operator to record a specific measure. This input can also reference parameter measures and measures pulled in from other steps.
- Checkbox: Prompts the operator to choose between two opposing values using a toggle, typically to indicate the completion (or non-completion) of an activity or requirement.
- Resource: Prompts the operator to scan a resource.
- Location: Prompts the operator to scan a location.
- Date/Time Capture: Prompts the operator to record date/time information.
- Dropdown: Prompts the operator to select one option from a dropdown list.
- Table: Prompts the operator to complete information within a table.
PREREQUISITE:
Prior to completing the steps in any of the sections below, create or open the relevant draft procedure template in the Tempo web app. (To learn more about locating procedure templates in the Tempo web app, review the Procedure Templates Overview article.)
NOTES:
- To edit a procedure template, it must be in the Draft stage.
- Only the user who created a procedure template and any users assigned as a procedure co-author can edit a procedure template.
Value
Procedure authoring in Tempo includes six types of value inputs:
- Short Form Text: Prompts the operator to provide a short text response.
- Long Form Text: Prompts the operator to provide a long text response.
- Number: Prompts the operator to provide a numeric input.
- Two Choice: Prompts the operator to select between two choices (for example, Yes and No).
- Parameter: The app displays a value configured and enforced at the parameter level to the operator.
- From Step Input: The app displays the value of a referred step input to the operator.
NOTE:
⯈ Click here to view an example GIF of an operator completing a short form text value input on the Tempo iOS app. ⯇
Value input field explanations
- Name/Prompt: Use this field to explain to the operator what value to input during execution.
- Identifier: Each value input must have a unique identifier; this is the internal system ID for this specific value input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Name/Prompt field.
- Value Type: Select one of the six value type inputs from the dropdown list (Short Form Text, Long Form Text, Number, Two Choice, Parameter, From Step Input); this selection determines any additional fields that may display. For additional information, refer to the table below.
| Value type | Fields |
|---|---|
| Short Form Text | ⋅ Condition: If the short form text entered by an operator must be a specific accepted value, select Values, then provide any accepted value(s) in the Accepted Value(s) field; otherwise, select None. |
| Long Form Text | N/A |
| Number | ⋅ Review: If the number entered by an operator must be reviewed as a Critical Process Parameter (CPP), Critical Quality Attribute (CQA), or other reviewable value, select the relevant Trigger Value Exception option from the dropdown; otherwise, select No review required. ⋅ Condition: If the number entered by an operator must meet a certain acceptance condition, select one of the six conditions from the dropdown list (Value(s), Range, Greater Than, Greater Than or Equal, Less Than, Less Than or Equal), then define the acceptable conditions for this number using the related field(s) that display; otherwise, select None. |
| Two Choice | ⋅ Option 1: Set the name for the first option. ⋅ Option 2: Set the name for the second option. ⋅ Condition: If the two choice option selected by an operator must be an accepted option, select Single, then select the name of the accepted option in the Condition Value field; otherwise, select None. |
| Parameter | ⋅ Parameter: Select a previously-created parameter from this procedure template from the dropdown or create a new parameter by selecting Create New Parameter and completing all necessary information. For more information about parameters, review the Adding Dynamic Content: Parameters & Constants article. |
| From Step Input | ⋅ From Step Input: Select the name of the relevant previous step input from the dropdown list. |
Value & measure condition note
Both Number value inputs and Manual Entry measure inputs offer six potential acceptance conditions for information entered by an operator (Value(s), Range, Greater Than, Greater Than or Equal, Less Than, Less Than or Equal):
- Accepted Value(s): If the procedure author selects Value(s), the procedure author may set the accepted value(s). The value or values in this field are accepted.
- Range: If the procedure author selects Range, the procedure author may set the Lower Bound and Upper Bound of the acceptable range. Any value inside this range or equal the lower bound or upper bound is accepted.
- Greater Than: If the procedure author selects Greater Than, the procedure author may set the highest value that is not an acceptable value. Any value greater than this number is accepted.
- Greater Than or Equal To: If the procedure author selects Greater Than or Equal To, the procedure author may set the lowest acceptable value. Any value greater than or equal to this number is accepted.
- Less Than: If the procedure author selects Less Than, the procedure author may set the lowest value that is not an acceptable value. Any value less than this number is accepted.
- Less Than or Equal To: If the procedure author selects Less Than or Equal To, the procedure author may set the highest acceptable value. Any value less than or equal to this number is accepted.
For manual entry measure inputs, the condition values are all automatically set in the Unit of Measure selected by the procedure author.
Measure
Procedure authoring in Tempo includes three types of measure inputs. During procedure execution, a measure input prompts an operator to record or review a measurement.
- Manual Entry: Prompts the operator to manually enter a measurement.
- From Step Input: The app displays the measure of a referred step input to the operator.
- Parameter: The app displays a measure configured and enforced at the parameter level to the operator.
NOTE:
⯈ Click here to view an example GIF of an operator completing a manual measure input on the Tempo iOS app. ⯇
Measure input field explanations
- Name/Prompt: Use this field to explain the purpose of the measure input to the operator.
- Identifier: Each measure input must have a unique identifier; this is the internal system ID for this specific input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Name/Prompt field.
- Value Type: Select one of the three measure type inputs from the dropdown list (Manual Entry, From Step Input, Parameter); this selection determines any additional fields that may display. For additional information, refer to the table below.
| Measure type | Fields |
|---|---|
| Manual Entry | ⋅ Require Value in Scientific Format: Check this checkbox to require the measure value to be in scientific format; otherwise, leave the checkbox unchecked. ⋅ Unit of Measure: Select the unit of measure the operator will use. ⋅ Max # of Integer Places: Set the maximum number of digits acceptable before the decimal. ⋅ # of Decimal Places: Set the number of digits required after the decimal. ⋅ Review: If the value entered by an operator must be reviewed as a Critical Process Parameter (CPP), Critical Quality Attribute (CQA), or other reviewable value, select the relevant Trigger Measure Exception option from the dropdown; otherwise, select No review required. ⋅ Condition: If the measure entered by an operator must meet a certain acceptance condition, select one of the six conditions from the dropdown list (Value(s), Range, Greater Than, Greater Than or Equal, Less Than, Less Than or Equal), then define the acceptable conditions for this measure using the related field(s) that display; otherwise, select None. For more information, review the Value & measure condition note. |
| From Step Input | ⋅ From Step Input: Select the name of the relevant previous step input from the dropdown list. |
| Parameter | ⋅ Parameter: Select a previously-created parameter from this procedure template from the dropdown or create a new parameter by selecting Create New Parameter and completing all necessary information. For more information about parameters, review the Adding Dynamic Content: Parameters & Constants article. |
Checkbox
NOTE:
⯈ Click here to view an example GIF of an operator completing a checkbox input on the Tempo iOS app. ⯇
During procedure execution, a checkbox input prompts an operator to indicate the completion (or non-completion) of an activity or similar requirement.
Checkbox input field explanations
- Name/Prompt: Use this field to explain the purpose of the checkbox input to the operator.
- Identifier: Each checkbox input must have a unique identifier; this is the internal system ID for this specific input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Name/Prompt field.
- Condition: If the dropdown option selected by an operator must be an accepted option, select the relevant option (Checked, Unchecked); otherwise, select None.
Resource
Procedure authoring in Tempo includes up to four types of resource inputs. During procedure execution, a resource input prompts an operator to scan a resource.
NOTE:
⯈ Click here to view an example GIF of an operator completing an equipment scan resource input on the Tempo iOS app. ⯇
Resource input field explanations
- Name/Prompt: Use this field to explain the purpose of the resource input to the operator.
- Identifier: Each resource input must have a unique identifier; this is the internal system ID for this specific input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Name/Prompt field.
- Resource Type: Select one of the four measure type inputs from the list (Equipment, Material, Sample, Array); this selection determines any additional fields that may display. For additional information, refer to the table below.
| Resource type | Scan type | Fields |
|---|---|---|
| Equipment | ⋅ Scan Type: Select one of up to four scan types from the dropdown list (External Resource, Resource Query, Integration Query, Resource Parameter). | ⋅ Condition (Resource Query only): If the resource scanned by an operator must meet a certain acceptance condition, select Class/Subclass/Specific Resource, then define the acceptable conditions for this resource using the related field(s) that display; otherwise, select None. ⋅ Integration (Integration Query only) Select the relevant Integration option from the dropdown. ⋅ Parameter (Resource Parameter only): Select a previously-created parameter from this procedure template from the dropdown. For more information about parameters, review the Adding Dynamic Content: Parameters & Constants article. ⋅ Require This Equipment to Be Usable (Resource Query and Integration Query only): If checked, the equipment must be calibrated and in a usable status. |
| Material | ⋅ Scan Type: Select one of up to four scan types from the dropdown list (External Resource, Resource Query, Integration Query, Resource Parameter). | ⋅ Condition (Resource Query only): If the resource scanned by an operator must meet a certain acceptance condition, select Class/Subclass/Specific Resource, then define the acceptable conditions for this resource using the related field(s) that display; otherwise, select None. ⋅ Integration (Integration Query only) Select the relevant Integration option from the dropdown. ⋅ Parameter (Resource Parameter only): Select a previously-created parameter from this procedure template from the dropdown. For more information about parameters, review the Adding Dynamic Content: Parameters & Constants article. ⋅ Require This Material to Be Usable (Resource Query and Integration Query only): If checked, the material must be unexpired, in a usable status, and the lot must be approved. |
| Sample | ⋅ Scan Type: Select one of up to four scan types from the dropdown list (External Resource, Resource Query, Integration Query, Resource Parameter). | ⋅ Condition (Resource Query only): If the resource scanned by an operator must meet a certain acceptance condition, select Class/Subclass/Specific Resource, then define the acceptable conditions for this resource using the related field(s) that display; otherwise, select None. ⋅ Integration (Integration Query only) Select the relevant Integration option from the dropdown. ⋅ Parameter (Resource Parameter only): Select a previously-created parameter from this procedure template from the dropdown. For more information about parameters, review the Adding Dynamic Content: Parameters & Constants article. |
| Array | ⋅ Scan Type: Select one of up to four scan types from the dropdown list (External Resource, Resource Query, Integration Query, Resource Parameter). | ⋅ Condition (Resource Query only): If the resource scanned by an operator must meet a certain acceptance condition, select Class/Subclass/Specific Resource, then define the acceptable conditions for this resource using the related field(s) that display; otherwise, select None. ⋅ Integration (Integration Query only) Select the relevant Integration option from the dropdown. ⋅ Parameter (Resource Parameter only): Select a previously-created parameter from this procedure template from the dropdown. For more information about parameters, review the Adding Dynamic Content: Parameters & Constants article. |
Location
During procedure execution, a location input prompts an operator to scan a location.
Location input field explanations
- Name/Prompt: Use this field to explain the purpose of the location input to the operator.
- Identifier: Each location input must have a unique identifier; this is the internal system ID for this specific input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Name/Prompt field.
- Condition: If the location input by an operator must meet a specific condition, select one of the four conditions from the dropdown list (Site, Building, Area, Unit), then define the acceptable conditions for this input using the related field(s) that display; otherwise, select None.
- Require Location to Be Usable: If checked, the location must be in a usable status.
Date/time capture
Procedure authoring in Tempo includes three types of date/time capture inputs. During procedure execution, a date/time capture input prompts an operator to record a date and/or time.
NOTE:
⯈ Click here to view an example GIF of an operator completing a date and time capture input on the Tempo iOS app. ⯇
Date/time capture input field explanations
- Name/Prompt: Use this field to explain the purpose of the date/time capture input to the operator.
- Identifier: Each date/time capture input must have a unique identifier; this is the internal system ID for this specific input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Name/Prompt field.
- Time Capture Type: Select one of the three date/time capture type inputs from the dropdown list (Either, Date and Time, Date). For additional information, refer to the table below.
| Date/Time type | Fields |
|---|---|
| Either (operator may enter Date and Time or Date) | ⋅ Time Capture Condition: If the date/time or date capture entered by an operator must meet a specific condition in relation to other date/time capture input(s), select one of the three conditions from the dropdown list (Between, On or After, On or Before), then define the acceptable conditions for this input using the related field(s) that display; otherwise, select None. For more information, review the Date/time capture condition note below. |
| Date and Time | ⋅ Time Capture Condition: If the date and time capture entered by an operator must meet a specific condition in relation to other date/time capture input(s), select one of the three conditions from the dropdown list (Between, On or After, On or Before), then define the acceptable conditions for this input using the related field(s) that display; otherwise, select None. For more information, review the Date/time capture condition note below. |
| Date | ⋅ Time Capture Condition: If the date capture entered by an operator must meet a specific condition in relation to other date/time capture input(s), select one of the three conditions from the dropdown list (Between, On or After, On or Before), then define the acceptable conditions for this input using the related field(s) that display; otherwise, select None. For more information, review the Date/time capture condition note below. |
Date/time capture condition note
All date/time capture conditions are set in terms of the relationship between this input with either one or two other date/time capture inputs. These other inputs cannot be added to the same step as the input that should have a condition. This means that setting up any other inputs on an earlier or later step in the procedure template is a prerequisite to defining a date/time capture condition.
Dropdown
During procedure execution, a dropdown input prompts an operator to select one option among any listed dropdown options.
NOTE:
⯈ Click here to view an example GIF of an operator completing a dropdown input on the Tempo iOS app. ⯇
Dropdown input field explanations
- Name/Prompt: Use this field to explain the purpose of the dropdown to the operator.
- Identifier: Each dropdown input must have a unique identifier; this is the internal system ID for this specific input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Name/Prompt field.
- Add Option: Add an additional dropdown option; repeat as needed.
- Option X: Set the name this option.
- Condition: If the dropdown option selected by an operator must be an accepted option, select Accepted Values, then select any accepted options in the Accepted Selections field; otherwise, select None.
Table
Procedure authoring in Tempo includes up to three types of table inputs. During procedure execution, a table input prompts an operator to capture a set of other inputs in a table format.
- Standard tables are available for use in any Tempo package.
- Sample tables require the LES package.
- Sample Plate tables require the LES package and are used with an array resource that has been loaded using the Load Plate action.
NOTE:
⯈ Click here to view an example GIF of an operator completing a standard table input on the Tempo iOS app. ⯇
Table input field explanations
- Name/Prompt: All table input types require the procedure author to provide a name/prompt. Use this field to explain the purpose of the table to the operator.
- Identifier: Each table input must have a unique identifier; this is the internal system ID for this specific input. The system automatically attempts to create an identifier in the correct format when a procedure author completes the Name/Prompt field.
- Type: Select one of the table type inputs from the list (Standard, Sample, Sample Plate); this selection determines any additional fields that may display. For additional information, refer to the table below.
| Table type | Table configuration options | Additional fields |
|---|---|---|
| Standard | ⋅ Allow add/delete rows: If the operator should have the ability to add or delete rows from the table during execution, check this checkbox; otherwise, leave this checkbox unchecked. ⋅ Minimum rows: Use the + and - icons to add or remove rows from the table. ⋅ Add column: Add a new column to the table. ⋅ Column: more options: Expand the more options menu to delete or shift a column. | For each column, select the input or action to add from the following list, then complete any additional information required: ⋅ Value ⋅ Measure ⋅ Checkbox ⋅ Resource ⋅ Location ⋅ Date/Time Capture ⋅ Dropdown (Review the relevant section this article for more information about specific inputs.) |
| Sample | ⋅ Add column: Add a new column to the table. ⋅ Column: more options: Expand the more options menu to delete or shift a column. | For each column, select the input or action to add from the following list, then complete any additional information required: ⋅ Value ⋅ Measure ⋅ Checkbox ⋅ Resource ⋅ Location ⋅ Date/Time Capture ⋅ Dropdown (Review the relevant section this article for more information about specific inputs.) |
| Sample Plate | ⋅ Load Plate Action: Select a previously load plate action from this procedure template from the dropdown. ⋅ Add column: Add a new column to the table. ⋅ Column: more options: Expand the more options menu to delete or shift a column. | For each column, select the input or action to add from the following list, then complete any additional information required: ⋅ Value ⋅ Measure ⋅ Checkbox ⋅ Resource ⋅ Location ⋅ Date/Time Capture ⋅ Dropdown (Review the relevant section this article for more information about specific inputs.) |