specs/models/M_TABLE
Table
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).
It contains the following Models:
Tulip Table Metadata
| Item | Description |
|---|---|
| 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. |
| Apps | The apps that reference the table |
| 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 |
| QA-T700 | Table Queries : 02 / Query for an Archived Field |
| QA-T702 | Table Management : 05 / Table Columns must be named |
| QA-T703 | Table Queries : 07 - Unique value aggregation |
| QA-T704 | Table Management : 01 / Table name cannot be blank |
| QA-T705 | Table Management : 06 / Table Columns labels cannot be blank and ID cannot be edited |
| QA-T712 | Embedded Tables : 07 - Pagination in an embedded table |
| QA-T715 | Table Management : 04 / Cannot leave table name blank on edit |
| QA-T716 | Table Management : 12 / Table Record Data Validation |
| QA-T721 | Table Queries : 03 / Can't edit a saved Aggregation without clicking 'Edit' |
| QA-T841 | Embedded Tables : 08 - Displaying variable data source |
| QA-T923 | Embedded Tables : 03 / Only matching record placeholders can be selected |
| QA-T927 | Table Analytics - Filtering by 'Date Range' settings |
Requirements
| ID | Requirement |
|---|---|
| PLAT-8723 (238) | Ability to add equipment context to historize time series data |
| PLAT-8729 (260) | Ability to track equipment use in production execution by material unit and work order. |
| PLAT-8732 (258) | Ability to complete steps with process values that are not within the predefined limits if appropriate exception/deviation information and approval is entered |
| PLAT-8735 (293) | Track process execution of the Production Models by Apps |
| PLAT-8738 (291) | Provide sequence management of process steps so that Apps can get required information for execution of a specific process step |
| PLAT-8745 (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 |
| PLAT-8753 (18) | Provide ability to manage one or more master data definitions or models simultaneously |
| PLAT-8755 (16) | Manage the release to use of content based on approval status. |
| PLAT-8756 (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 |
| PLAT-8789 (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 |
| PLAT-8810 (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. |
| PLAT-8815 (154) | Ability to use process values from previous process steps in any procedural element or step workflow. |
| PLAT-8824 (42) | Ability to monitor and control data exchange on all interfaces with message and error logging. |
| PLAT-8834 (239) | Ability to capture (historize) alarm and event information from equipment |
| PLAT-8840 (456) | Ability to define and dispatch work orders for the different segments of the manufacturing operation. |
| PLAT-8841 (289) | Ability to exclude a work order from the dispatch list. |
| PLAT-8842 (185) | Ability to define quantity and capacity constraints for equipment |
| PLAT-8847 (119) | Ability to configure procedural elements for work on orders, materials or equipment in a workflow |
| PLAT-8848 (900) | Equipment & cleaning log - The system must be able to create logs for registration of use, maintenance, calibration & cleaning of equipment and rooms. |
| PLAT-8850 (118) | Ability to configure steps and states for work on orders, materials or equipment in a workflow |
| PLAT-8853 (426) | Ability to transfer sample material as defined in sampling plan |
| PLAT-8854 (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. |
| PLAT-8862 (127) | Disallow completion of work until all required processing steps have been performed. i.e. disallow batch close when there are incomplete processing steps. |
| PLAT-8864 (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. |
| PLAT-8877 (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.) |
| PLAT-8879 (288) | Ability to track dispatching of work orders and materials to production once they are released. |
| PLAT-8880 (278) | Dispatch priority of work orders and batches/lots can be controlled using predefined configurable dispatching strategies |
| PLAT-8881 (277) | Ability to view dispatching list by equipment. Ie for any element of the equipment hierarchy such as area, machine, work center, etc. |
| PLAT-8882 (276) | Work order have to be approved and released for production before any material can be started. Ie starting batches/lots |
| PLAT-8884 (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.) |
| PLAT-8886 (94) | Ability to view material dispatching lists in a content. |
| PLAT-8889 (188) | Standard non configurable material attributes must include quantity, UOM, status, expiration date, location, process step |
| PLAT-8892 (96) | Ability to view batch/lot dispatching lists in content |
| PLAT-8895 (180) | Ability to propagate material attributes to associated materials in the material tracking hierarchies. e.g. assigning material attributes to final product from intermediates. |
| PLAT-8897 (179) | Ability to assign material properties to any level of the material tracking hierarchy |
| PLAT-8898 (178) | Provide a configurable multi-level material tracking for batch, lot, plate/tray, well, unit, flask. |
| PLAT-8900 (136) | BOM shall include definition of quantities and UOM for each BOM element |
| PLAT-8908 (396) | Ability to track and list materials for a work order for reconciliation. |
| PLAT-8919 (407) | Ability to track of material waste and scrap as part of the production process execution. |
| PLAT-8923 (405) | Ability to manage and track material consumption as part of a process step. Material consumption may include processing, weighing, dispensing, etc. |
| PLAT-8927 (389) | Ability to track material movement history. Ie. path of material in the production process |
| PLAT-8947 (167) | As an operator I need to be able to identify equipment used in operation by a unique name, number or identifier |
| PLAT-8949 (164) | When building Apps, I want to be able to assign equipment to a location where it can be used |
| PLAT-8953 (50) | Disallow deletion of content that have been used in execution of a work order or material processing. |
| PLAT-8955 (49) | Provide a managed way to configure and maintain content including creating, copying, editing, making obsolete, and deleting. |
| PLAT-8959 (317) | Ability to track multiple dispensing of the same material continuously for different work orders or batches/lots as part of a campaign |
| PLAT-8960 (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. |
| PLAT-8963 (303) | Ability to track batch/lot and material rework based on the Master Recipe or material workflow configuration. |
| PLAT-8964 (261) | Ability to track equipment substitution during process execution. |
| PLAT-8969 (428) | Ability to adjust batch/lot and material quantities related to sample plan execution |
| PLAT-8971 (354) | Ability to track material association to work order and production order at all levels of material tracking hierarchy |
| PLAT-8974 (351) | All material tracking history will include date and time stamps |
| PLAT-8976 (350) | All material tracking history will include context of material hierarchy levels |
| PLAT-8979 (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 |
| PLAT-8981 (357) | Ability to track material consumption and use at all levels of the material tracking hierarchy. |
| PLAT-8990 (337) | Ability to track material consumption in a process step. Material consumption may include processing, assembly, weighing, dispensing, etc. |