Widgets and triggers utilize variables of specific types to determine user interaction and application flow. There are three categories of variables in apps:
The primitive variable types in apps:
|a true or false value
|a value that encodes the standard RGBA standard used in webapps
|a numeric value that can have a decimal value
|A string that represents the web address of an image file
|A numeric value that cannot have decimal values.
|A duration in time saved in milliseconds.
|A string value.
|A user in the Tulip system. The user model includes custom fields (see 09 People Management)
|A specific date, time and timezone.
|A station where an app is used, as determined by the "Stations" page
|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'.
|Variable Widget : 01 - Simple variables in canvas can be changed to compound variables
|Variable Widget : 02 - Record View: Compound variables can be used with triggers
|Input Widgets : 01 - Boolean widget
|Variable modal : 01 - Create and modify a variable
|Variable modal : 02 - Variables need to have unique names
|Variable modal : 03 - Managing variables created within the app
|Variable modal : 04 - Variable's parameters
|Variable modal : 05 - Managing variables on the modal
|Variable modal : 06 - Deleting variables
|Input Widgets : 02 - Text widget
|Input Widgets : 03 - Number widget
|Input Widgets : 04 - Single Select widget
|Input Widgets : 05 - Multiselect widget
|Input Widgets : 06 - Date picker widget
|Input Widgets : 07 - Camera widget
|Timer Widget : 02 - Target Time Configuration
|Dev Mode - Variables and Table Records
|Ability to assign and notify multiple users for a given approval workflow of all content.
|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.
|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
|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
|Tulip has to display the current batch/lot currently being worked on
|Ability for content to display relevant process and production data as a metric. Ie. number, gauge, indicator etc.
|All contents have to guide operators thru the process steps in an easy intuitive manner. Ie. easy navigation between process steps
|Ability to display sampling plan requirements to user
|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.
|Ability to use process values from previous process steps in any procedural element or step workflow.
|Ability to assign material properties to any level of the material tracking hierarchy
|Disallow steps from completing until the correct material, material quantity, has been consumed or identified
|Ability to re-execute process step respecting any constraints of the process step configuration in the process flow.
|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.
|Ability to route and disposition materials based on sampling plans Eg. hold or future hold materials until sample testing results are available
|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
|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.
|All material tracking history will include context of material hierarchy levels
|Ability to track equipment location for mobile equipment. The equipment log will include the equipment's location history or path.
|Ability to track of material waste and scrap as part of the production process execution.
|Ability to track material attributes during production operations with associated capabilities to browse their history and their trending e.g. temperature, assays, etc.
|Ability to perform analysis on batch/lot and material history records. Ie query history records based on any attribute of the material