specs/models/M_CONN

Connector

A connector is a configuration that defines how an app can read and write to an external data store through the functions defined by that connector. Only users with the connector admin role can create, edit and delete connectors. Tulip supports two types of data sources for connectors:

  • HTTP Connector - A datasource that is accessed through the https protocol.
  • SQL Connector - A database that is accessed with an SQL query.

Connectors and application lifecycle

Because connectors connect Tulip to outside data sources, it is important that users are able to set up multiple Connector Environments based on the publication lifecycle of the app version implementing a given connector. For example, if the app writes to the data source, a user would want the development version of an app to connect to a different database than the published version of the app. If the connector only implements read only functions, the connection might be the same for development and production versions. Tulip allows for 3 different ways to configure environments for a connector:

  1. Production Only - the same connection configuration is used for development versions, published version, and pending version.
  2. Production & Development - Production is used for published apps, and the development and pending version of apps use the development configuration.
  3. Production, Staging & Development - Production is use for published apps, development is used for development, and staging is used for apps that are pending approval.

Fields:

FieldDescription
NameThe name of the connector. Usually this will be the name of the data source the connector is connecting to.
DescriptionAn optional blurb of text telling other users the intended use or other key info about the connector.
ImageAn optional image representing the connector
TypeHTTP or SQL
Activation StatusA boolean that determines whether the connector function is active or deactivated
Connector Environments Configuration1 of the 3 options for connector environment configuration
List of connector functionsThe connector functions for this connector

Tests

IDName
QA-T127Connectors : 05 - Clone, Edit, Delete, Restore Connectors
QA-T147Connectors : 01 - Add a SQL Connector
QA-T148Connectors : 02 - Add Function to SQL Connector
QA-T239Connectors : 03 - Add an HTTP Connector
QA-T240Connectors : 04 - Add several functions to HTTP Connector

Requirements

IDRequirement
57Allow integration of simple IIoT end-points for data input and capture
58Allow integration of advanced IIoT end-points for interaction with equipment and collaboration with devices
100Ability to retrieve, examine, and view batch/lot and material attributes used in the processing step (e.g. potency), from external source.
215Ability to receive production order from a system of record with associated material list
350All material tracking history will include context of material hierarchy levels
354Ability to track material association to work order and production order at all levels of material tracking hierarchy
357Ability to track material consumption and use at all levels of the material tracking hierarchy.
363Ability 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
388Ability to track material inventory and its physical location.
389Ability to track material movement history. Ie. path of material in the production process
390Ability to track materials associations using the material tracking model. Ie. track physical material in tray location, trays in batches (Cohorts).
392Ability to track materials handled in load-carriers.
393Ability to track loading of material to a load-carrier and its location within the load carrier. Ie. material in a well, plate, flask, tank, tote, etc.
394Ability to track unloading of material from a load-carrier
396Ability to track and list materials for a work order for reconciliation.
405Ability to manage and track material consumption as part of a process step. Material consumption may include processing, weighing, dispensing, etc.
406Ability to consume by pre-configured unit of measure (UoM) quantities such as weight, volume, etc.
428Ability to adjust batch/lot and material quantities related to sample plan execution
836Ability to retrieve information from external a system of record so that Apps can get the required information for execution fo a specific process step.
856When an individual executes a series of signings during a single, continuous period of controlled system access, the first signing shall be executed using all electronic signature components; subsequent signings shall be executed using at least one electronic signature component that is only executable by, and designed to be used only by, the individual.
857Ability to print configured labels for sample materials