After completing a setup for application or database connector we need to integrate the connector into Cellosign Template.

How does it work?

On template connector level Cellosign includes 4 firing options that represents a life span of a transaction in Cellosign:

1. PRESET: Fires when transaction is created
2. LIVE: Fires as user is engaging with the form
3. SUBMIT:  Fires when user submits the form
4. POST SUBMIT: T Fires after form is submitted

PRESET

Preset is initiated at time a session is created, given enough information injected into session, this setting can get data from your data source prior to engaging the end user.

Preset includes only lookup (Read) operation. To set Preset

1. Click on “Add Preset Connector”
2. Select source and Instance
3. Select Object (Table)
4. Define the query for lookup. Values for query can be retrieved from: a “label” injected into process or a form field or a fixed value
5. Define what happens case there are no results, one result or more then one result to match the query
6. Define which column to fetch from your object and to which form field value is incorporated into
7. Click save

Best practice is to use automated scenarios such as PRESET whenever possible. Given sufficient and unique data, Cellosign will be able to get data from your data source.

LIVE

Live connector is similar to PRESET with the difference that it requires the end user interaction with the form. A practical scenario is that at the stage of processing the form we are missing some data, most common in self service scenarios.

Note that although we have taken the necessary steps to secure your data source, the implementation should consider measure for protecting the data by requesting information known only for the end user. for example requesting only Account ID is not recommended.

To setup LIVE connector, follow instructions on PRESET and apply activation on field change or button.

• “Change” trigger occurs when a value of field is changed by end user, such as typing account name
• “Click” is triggered on a button click. If you have a button mapped on your form, select it as trigger

SUBMIT

This is where Create, Update, Delete and File uploading operations occur.

To setup SUBMIT operation:

1. Click on “Add Submit Connector”
2. Select source and Instance
3. Select Object (Table)
4. Select the operation: Create/Update/Delete/Upload files*
5. Define the query for matching the record. (Not relevant for Create). Values for query can be retrieved from: a “label” injected into process or a form field or a fixed value
6. Define what happens case there are no results, one result or more then one result to match the query
7. Define which table columns to update (Not relevant for Delete and file upload)
8. Click save

Query conditions

Each connector Lookup/Update/Delete requires a condition to match with the remote data source for which it will act upon [that is equivalent to SQL WHERE clause]. Condition for matching includes:

1. Data source to match i.e Account ID
2. Equation, i.e. Equal, true/false in case of boolean or contain/starts with in case of strings.
3. What data it will the compare with. i.e constant, values already applied to form
4. Apply order to Where clause in case we have multiple results

Fields mapping

This is the part when import of data is being made from remote data source into form. This functionality is relevant only for LOOKUPS [equivalent to SQL SELECT clause].

Fields mapping into form fields can be made:

1. As is, directly from database column
2. Converted using an editor

Data conversions

Conversion functionality is provided to Numbers and date-time data types.

To convert date time select the relevant date time column, select date format option and pick the required format from the list.

To convert number data type, select a number column:

1. Apply Ceil to round up to integer
2. Apply Floor to round down to integer
3. Select currency format to apply a number with thousands separator, with or without decimal point

Concatenation

Use CONCAT feature to consolidate values from different table column to one string, simple example: first and last name. Concatenation can also include fixed values to get result such as: “Name: FirstName Last name, ID: ClientID.”

Repeater

Use this feature when LOOKUP is configured to expect multiple results such: as All Account contacts. In this case we may use repeater to consolidate a string for as many contacts as the connector pulls from the database. See the example above, it includes a CONCAT and REPEATER on contacts first and last name.

Changes in integrations

Occasionally you will be required to move integrations from one environment to another or modify integration end points. Connectors in Cellosign holding the identifiers of an integration and when moving around this needs to be updates.

When changing the integration it becomes invalid in the template. You will be required to update the integration in the connector. Simply click on the connector’s edit button.

Select the source, instance and click fix.

In case of application connector as Salesforce make sure that the dataset is available as moving from one app to another you might not have the exact schema.