specs/models/M_APP_VER_VAR
Variable
Widgets and triggers utilize variables of specific types to determine user interaction and application flow. There are three categories of variables in apps:
- Primitive - a single value such as integer, text, or user
- Custom object - a variable with named attributes, each of which is a primitive
- Array - an ordered list in which every item is of the same type. The type can be either a primitive or a custom object.
The primitive variable types in apps:
| Variable Type | Description |
|---|---|
| Boolean | a true or false value |
| Color | a value that encodes the standard RGBA standard used in webapps |
| Number | a numeric value that can have a decimal value |
| Image URL | A string that represents the web address of an image file |
| Integer | A numeric value that cannot have decimal values. |
| Interval | A duration in time saved in milliseconds. |
| Text | A string value. |
| User | A user in the Tulip system. The user model includes custom fields (see 09 People Management) |
| Datetime | A specific date, time and timezone. |
| Station | A station where an app is used, as determined by the "Stations" page |
| Machine | A Machine that was outputting data as defined on the Machine Details page. |
Furthermore, each variable type can also be saved as an array of that type, for example 'Boolean array' or 'Color array'.
Tests
| ID | Name |
|---|---|
| QA-T56 | Variable Widget : 01 - Simple variables in canvas can be changed to compound variables |
| QA-T57 | Variable Widget : 02 - Record View: Compound variables can be used with triggers |
| QA-T157 | Input Widgets : 01 - Boolean widget |
| QA-T458 | Variable modal : 01 - Create and modify a variable |
| QA-T459 | Variable modal : 02 - Variables need to have unique names |
| QA-T460 | Variable modal : 03 - Managing variables created within the app |
| QA-T461 | Variable modal : 04 - Variable's parameters |
| QA-T462 | Variable modal : 05 - Managing variables on the modal |
| QA-T463 | Variable modal : 06 - Deleting variables |
| QA-T477 | Input Widgets : 02 - Text widget |
| QA-T478 | Input Widgets : 03 - Number widget |
| QA-T479 | Input Widgets : 04 - Single Select widget |
| QA-T480 | Input Widgets : 05 - Multiselect widget |
| QA-T481 | Input Widgets : 06 - Date picker widget |
| QA-T482 | Input Widgets : 07 - Camera widget |
| QA-T513 | Timer Widget : 02 - Target Time Configuration |
| QA-T568 | Dev Mode - Variables and Table Records |
Requirements
| ID | Requirement |
|---|---|
| 12 | Ability to assign and notify multiple users for a given approval workflow of all content. |
| 22 | Ability to configure collections of user/reason codes to be used for classification of events and data during execution and defined in master data and model elements. |
| 27 | Provide a managed way to define label templates and formats with process and operation specific parameters. Ie. parameters are replaced with specific values when labels are processed for printing during process execution |
| 66 | Tulip can be used in environment where operators wear gloves. i.e. sterile or clean areas where the operator is gowned up and has gloves on |
| 70 | Tulip has to display the current batch/lot currently being worked on |
| 77 | Ability for content to display relevant process and production data as a metric. Ie. number, gauge, indicator etc. |
| 78 | All contents have to guide operators thru the process steps in an easy intuitive manner. Ie. easy navigation between process steps |
| 102 | Ability to display sampling plan requirements to user |
| 133 | Ability to parameterize a process and production model definitions. Ie. create generic definition using parameterization that are substituted by specific production order information prior to release to production. |
| 154 | Ability to use process values from previous process steps in any procedural element or step workflow. |
| 179 | Ability to assign material properties to any level of the material tracking hierarchy |
| 253 | Disallow steps from completing until the correct material, material quantity, has been consumed or identified |
| 301 | Ability to re-execute process step respecting any constraints of the process step configuration in the process flow. |
| 302 | Ability to re-execute process step with override of constraints of the process step configuration in the Master Recipe or material workflow. In such a case an extra e-signature can be required. |
| 326 | Ability to route and disposition materials based on sampling plans Eg. hold or future hold materials until sample testing results are available |
| 327 | Ability to route and disposition materials based on results of sample testing (off-line) and/or quality testing (in-line) Eg. hold, reject, scrap, or release materials based on sample result |
| 330 | Ability to automatically or manually log an exception when data is not within configured limits and tolerances. Disallow process completion until exceptions have been logged with configured e-signatures and any authorized overrides have been processed e.g. supervisor signature, scrap, etc. |
| 350 | All material tracking history will include context of material hierarchy levels |
| 385 | Ability to track equipment location for mobile equipment. The equipment log will include the equipment's location history or path. |
| 407 | Ability to track of material waste and scrap as part of the production process execution. |
| 427 | Ability to track material attributes during production operations with associated capabilities to browse their history and their trending e.g. temperature, assays, etc. |
| 464 | Ability to perform analysis on batch/lot and material history records. Ie query history records based on any attribute of the material |