A Tulip Table is a simulated database table that the user can create and edit in order to store complex data. The fields are user created and completely customizable except for a required ID field (see Table Field for more details).

From a technical standpoint, a Tulip Table is essentially a wrapper around a Postgres table. However, we also store some metadata about Tables described below.

It contains the following Models:

Tulip Table Metadata

Name	The display name for the table
Description	Short description of the table added by the user
Last Modified	A timestamp of the last time someone edited the table shape. Adding or editing a row does not count.
Hidden	“Deleting” the table in the UI only soft deletes it. Tables that are soft deleted can later be restored.
Created By	The user that initially created the Table
Created At	The date and time that the Table was initially created
Deleted By	The user that deleted the Table
Deleted At	The date and time that the Table was deleted

Tests

ID	Name
QA-T80	Table Management : 01 - Create a table
QA-T81	Table Management : 02 - Delete a table
QA-T82	Table Management : 03 - Restore a deleted table
QA-T83	Table Management : 04 - Edit a table's name and description
QA-T84	Table Management : 05 - Add columns to a table
QA-T85	Table Management : 06 - Edit a table column
QA-T86	Table Management : 07 - Edit a table column description
QA-T87	Table Management : 08 - Delete a table column
QA-T88	Table Management : 09 - Restore a deleted table column
QA-T89	Table Management : 10 - Reorder table columns
QA-T90	Table Management : 11 - Resize table columns
QA-T92	Table Management : 12 - Create table records from the table detail page
QA-T93	Table Management : 13 - Sort table records by column in table view
QA-T94	Table Management : 14 - Load multiple pages of table records in table view
QA-T241	Embedded Tables : 01 - Embed a Tulip Table in an app
QA-T242	Embedded Tables : 02 - Sort an embedded table
QA-T243	Embedded Tables : 03 - Connect an embedded Tulip Table to a Table record
QA-T244	Embedded Tables : 04 - Filter an embedded table
QA-T245	Embedded Tables : 05 - Handle deleted fields in embedded tables
QA-T246	Embedded Tables : 06 - Handle a Tulip Table change in an embedded table
QA-T396	Widgets - Digital History Record Widget
QA-T397	Table Links : 01 - Creating Table Links
QA-T398	Table Links : 02 - Linking Records via Details Page
QA-T399	Table Links : 03 - Linking Records via App Triggers
QA-T400	Table Links : 04 - Deleting Linking Columns
QA-T464	Tables CSV Import : 01 - Import to table
QA-T466	Tables CSV Import : 02 - Import feature data handling
QA-T467	Tables CSV Import : 03 - Import from export
QA-T570	Table Queries : 01 - Create, Edit, Delete a Query
QA-T571	Table Queries : 02 - Query Configuration
QA-T572	Table Queries : 03 - Create, Edit, Delete an Aggregation
QA-T573	Table Queries : 04 - Aggregation Configuration

Requirements

ID	Requirement
16	Manage the release to use of content based on approval status.
18	Provide ability to manage one or more master data definitions or models simultaneously
42	Ability to monitor and control data exchange on all interfaces with message and error logging.
49	Provide a managed way to configure and maintain content including creating, copying, editing, making obsolete, and deleting.
50	Disallow deletion of content that have been used in execution of a work order or material processing.
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
94	Ability to view material dispatching lists in a content.
95	Ability to view material information for a batch/lot in an App. Information includes all material as part of a material hierarchy, ie. cohort, plate, well, etc.)
96	Ability to view batch/lot dispatching lists in content
118	Ability to configure steps and states for work on orders, materials or equipment in a workflow
119	Ability to configure procedural elements for work on orders, materials or equipment in a workflow
124	Ability to define procedural elements in process and material workflows that can be repeated in sequence, ie configurable number of iteration of the same step both min. and max. number of iterations.
125	Ability to define conditions to route process between steps in the workflow. These conditions can be based on state change in other steps or time constraints, equipment status, critical alarms, completion of other steps or defined timers.
127	Disallow completion of work until all required processing steps have been performed. i.e. disallow batch close when there are incomplete processing steps.
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.
136	BOM shall include definition of quantities and UOM for each BOM element
154	Ability to use process values from previous process steps in any procedural element or step workflow.
178	Provide a configurable multi-level material tracking for batch, lot, plate/tray, well, unit, flask.
179	Ability to assign material properties to any level of the material tracking hierarchy
180	Ability to propagate material attributes to associated materials in the material tracking hierarchies. e.g. assigning material attributes to final product from intermediates.
185	Ability to define quantity and capacity constraints for equipment
188	Standard non configurable material attributes must include quantity, UOM, status, expiration date, location, process step
238	Ability to add equipment context to historize time series data
239	Ability to capture (historize) alarm and event information from equipment
258	Ability to complete steps with process values that are not within the predefined limits if appropriate exception/deviation information and approval is entered
260	Ability to track equipment use in production execution by material unit and work order.
261	Ability to track equipment substitution during process execution.
274	Ability to start processing for work orders by starting to track material (batches, lots, units, etc.). Tracking information should respect tracking hierarchy (kits, trays, wells, flasks, jigs, etc.)
276	Work order have to be approved and released for production before any material can be started. Ie starting batches/lots
277	Ability to view dispatching list by equipment. Ie for any element of the equipment hierarchy such as area, machine, work center, etc.
278	Dispatch priority of work orders and batches/lots can be controlled using predefined configurable dispatching strategies
288	Ability to track dispatching of work orders and materials to production once they are released.
289	Ability to exclude a work order from the dispatch list.
291	Provide sequence management of process steps so that Apps can get required information for execution of a specific process step
293	Track process execution of the Production Models by Apps
295	Verify that all required data has been entered and collected as prescribed by the step on completion. Disallow to progress on execution path if verification fails
303	Ability to track batch/lot and material rework based on the Master Recipe or material workflow configuration.
309	Ability to track use of one source material or load-carrier used for multiple orders Eg. bulk material that is used for different products.
317	Ability to track multiple dispensing of the same material continuously for different work orders or batches/lots as part of a campaign
329	Verify entered data is within configured limit and tolerances as configured in the Master Recipe or material workflow process step, and material model. Allow authorized override of this constraint based on configuration
337	Ability to track material consumption in a process step. Material consumption may include processing, assembly, weighing, dispensing, etc.
347	Ability to track all WIP materials at all material hierarchy levels including batches, lots, and materials. Ie. material tracking history will include all activities performed on materials including issue, consumption, processing, mixing, assembly, movement, transfer, etc.
350	All material tracking history will include context of material hierarchy levels
351	All material tracking history will include date and time stamps
354	Ability to track material association to work order and production order at all levels of material tracking hierarchy
357	Ability to track material consumption and use at all levels of the material tracking hierarchy.
363	Ability to track and maintain forward and backwards batch/lot and material genealogy at all level of the material tracking hierarchy. Ie view, analyse and query material genealogy
389	Ability to track material movement history. Ie. path of material in the production process
396	Ability to track and list materials for a work order for reconciliation.
405	Ability to manage and track material consumption as part of a process step. Material consumption may include processing, weighing, dispensing, etc.
407	Ability to track of material waste and scrap as part of the production process execution.
426	Ability to transfer sample material as defined in sampling plan
428	Ability to adjust batch/lot and material quantities related to sample plan execution
456	Ability to define and dispatch work orders for the different segments of the manufacturing operation.
900	Equipment & cleaning log - The system must be able to create logs for registration of use, maintenance, calibration & cleaning of equipment and rooms.