specs/models/M_CONN_FUNC
Connector Function
Connector functions are configured requests defined on connectors that apps can utilized for sending and receiving data to the source of the connector. They abstract over the specifics of SQL or HTTP to present a standard input and output signatures composed of known variable types. For example a function 'Get Work Orders' might have a signature such as:
INPUTS:
1. Status (string)
2. Customer (string)
OUTPUTS:
1. Array of work orders
- Delivery date (date)
- Part ID (string)
- Part count (number)App editors can use these functions in apps without worrying about complex issues such as authentication, networking, how to write queries, HTTP headers, etc. Defining how the inputs are used to retrieve the data, is different for SQL and HTTP connectors.
Fields for all connector functions:
| Name | Description |
|---|---|
| Name | The name of the connector |
| Is Saved | Once a connector is saved the inputs and outputs can no longer be modified |
| Inputs | The composition of variable types an app must provide to call the connector function. Data types include: Text, Integer, Float, Boolean, Datetime. |
| Outputs | The composition of variable types an app can expect to receive from the connector function. Data types include: Text, Integer, Float, Boolean, Datetime and arrays of these data types. |
| Activation Status | A boolean that determines whether the connector function is active or deactivated |
| Description | A text description provided by the person who created the function (optional) |
Additional fields for SQL connector functions:
| Field | Description |
|---|---|
| Use multiple rows | A boolean value that indicates whether the expected output is a single object matching the defined outputs, or an array of objects matching the defined ouput. |
| Query | The SQL query used to retrieve the data. The query can utilize connector inputs in its definition. More on SQL queries |
Additional fields for HTTP connector functions:
| Field | Description |
|---|---|
| HTTP Request Method | One of: GET, HEAD, POST, PUT, PATCH, DELETE more info |
| Authentication | If the authentication is unset at the connector level, it can be set at the function level. |
| Request Headers | A list of request header key/value pairs. These values can utilize input values. |
| URL Path | The path portion of the HTTP request. The path can utilize input values. |
| Query Parameters | A list of key/value pairs that are added to the query portion of the request URL. These values can utilize input values. |
| Request Body | The request body can be one of four types: JSON, form URL-encoded, plain text or XML. The request body can utilize input values. |
| Response Body | Whether the response body is JSON or XML. This setting determined how extracts are used to determine output values. |
| Outputs extractors | For HTTP connectors each output must also define the extractor for retrieiving the data from the body, header or cookie of the HTTP response. |
Tests
| ID | Name |
|---|---|
| QA-T57 | Variable Widget : 02 - Record View: Compound variables can be used with triggers |
| QA-T148 | Connectors : 02 - Add Function to SQL Connector |
| QA-T240 | Connectors : 04 - Add several functions to HTTP Connector |
Requirements
| ID | Requirement |
|---|---|
| 42 | Ability to monitor and control data exchange on all interfaces with message and error logging. |
| 57 | Allow integration of simple IIoT end-points for data input and capture |
| 58 | Allow integration of advanced IIoT end-points for interaction with equipment and collaboration with devices |
| 60 | Data from connected end-points can be visualized as simple metrics |
| 61 | Data from connected end-points can be visualized in graphical format such as gauges, indicator, dial, scales, etc. |
| 63 | Data from connected end-points can be sent to other connected end-points |
| 64 | Data from connected end-points can be sent to connected core systems (MES, QMS, PLM, LIMS, and Sample Inventory) |
| 65 | Data from connected end-points can be sent to other content |
| 93 | App has to provide navigation between process steps from external input. Ie. scanner, button, switch, I/O triggers, etc. |
| 100 | Ability to retrieve, examine, and view batch/lot and material attributes used in the processing step (e.g. potency), from external source. |
| 101 | Ability to use a scale and record scale readings like (but not limited to) Zero, Tare, Gross Weight, Net Weight |
| 149 | Ability to provide access to relevant documents such as SOPs at process step |
| 153 | Ability to configure actions for automaton system or equipment alarms by alarm severity |
| 371 | Ability to control automated equipment state (start, stop, pause, resume, etc.) during the execution of a process step. |
| 431 | Ability to automatically submit sample transfer order to external material system. |
| 433 | Material transfer orders to external system shall contain sample information (ID, name, description) and location information (room, storage equipment, location in equipment). Ie. room name, floor number, freezer id, location in freezer, etc. |
| 436 | Ability to query from externals system the available material in sample inventory. ie samples stored in freezers, incubators, etc |
| 437 | Ability to define and execute a material transfer order to issue material from sample inventory |
| 438 | Ability to define and execute a material transfer order to store material in sample inventory |
| 459 | Ability to add additional information about content in the content repository including description, installation instructions, and rating. |
| 836 | Ability to retrieve information from external a system of record so that Apps can get the required information for execution fo a specific process step. |
| 844 | Ability to transfer or send history records to external system of record. Record can be transferred in their entirety at the completion of a process or in parts as steps in the process are completed |