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
Where UsedList of Apps using a connector
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 : 01 - Duplicate, Edit, Delete, Restore Connectors
QA-T147SQL Connectors : 01 - Add a SQL Connector
QA-T148SQL Connectors : 02 - Add Function to SQL Connector
QA-T239HTTP Connectors : 01 - Add an HTTP Connector
QA-T240HTTP Connectors : 02 - Add several functions to HTTP Connector
QA-T567Dev Mode - Environment and Player Settings
QA-T581Connectors : 02 - Environment Configuration
QA-T656Workspaces : 08 - Connectors across the workspaces
QA-T725HTTP Connectors : 04 - Extractors for Non-Json Formats and Cookies
QA-T726SQL Connectors : 03 - Verify different SQL Servers
QA-T727HTTP Connectors : 03 - OAuth 2 Admin/Operator
QA-T728HTTP Connectors : 05 - Non-2xx Responses
QA-T729HTTP Connectors : 06 - HTTP Connector Functions perform the same with TLS on/off
QA-T731HTTP Connectors : 07 - OAuth 2 send request data as JSON
QA-T793Connectors : 03 - Filtering and searching connectors
QA-T794Connectors : 04 - "Where Used" app links
QA-T795Connectors : 05 - "Where Used" app links on different workspaces
QA-T796Connectors : 06 - Connector functions search and "Where Used" app links
QA-T802Connectors versioning : 01 - Connectors in published apps
QA-T810HTTP Connectors : 03 - OAuth 2 Admin/Operator
QA-T840HTTP Connectors : 08 - URL encoding function

Requirements

IDRequirement
PLAT-8869 (856)Continuous signing sessions require two signature components for first signing but only one (secret) component for subsequent signings.