External ownership of Custom Data Objects available to SQL Server and PostgreSQL databases

Custom data objects can now be maintained in a database external to the SmartIQ cloud architecture, transferring responsibility of data to appropriate stakeholders. The implementation of the feature is done via the SmartIQ, SQL Server and Postgres data connectors via Custom Table data object.

Regardless of the type of data connection (SmartIQ, postgres or sql server) the feature creates a table in the source and maintains its records. For more information on maintaining records see Writable Data Objects.

For Sql Server and PostgreSql databases (i.e. databases managed externally to the SmartIQ cloud) note the following:

• The user provided in the connection string must have permissions to create tables/columns
• The default schema for the aforementioned user will be used for table creation
• Tables are named randomly by the smartIQ application
• Each custom table has a created/updated date for each record
• Deletion is a soft delete approach whereby if an individual record is deleted the only change to the record is its date deleted column
• The created, updated and deleted columns are for DBAs only and do not make their way back to the application
• Where columns in the database are set as encrypted the data is impossible to decrypt without the SmartIQ application

Custom Data Objects display Active/Pending Delete counts

SmartIQ Custom Data Objects will display the number of records active and pending delete.

SmartIQ External Event Support

Workflow External Events exist to have a workflow wait for external processing before continuing on. SmartIQ External Events waits for the completion of another SIQ project.

Using the Prepare form action, create a form that the SmartIQ External Event, it will react to the completion of another form. SmartIQ will send events back under the following circumstances so the External Event Response can be set as:

form-complete - occurs when the launched form is completed through to Finish
form-terminated - occurs when the launched form is terminated using Manage Workflow UI, RESTAPI or by escalation

Functionality only works within the same Tenant. Terminating a parent form doesn't clean up forms created for the External Events

Column text alignment options

Columns have a new text alignment options under the new alignment property, available in the inspector panel under appearance.

DocuSign 'Joint Agreement Network Id' action input

The DocuSign Create Envelope action has been modified to support a new 'Joint Agreement Network Id' input. This new input is optional and is exclusive to only Carbon Copy recipient types. It also corresponds to the LinkedAccountConfigurationId property within a DocuSign payload's Carbon Copy recipients array. Only one instance of this input can be added per recipient.

Document Viewer List Constrained Width option

When using the Document Viewer question, displaying a document list (does not apply to inline viewer), by default the width of the list is constrained to 650px. After customer feedback this isn't always appropriate and so a new property on this question type has been added, called Constrained Width. By default this is enabled, but simply uncheck the option to force the document list to take up the full width of its parent container.

Docusign 'Excluded Document Name' action input supports list(s) of documents

The DocuSign Create Envelope action's Excluded Document Name input now supports inputs containing either a single document name or a list of document names. These lists support commas, semi-colons, and pipe delimiters ( ',', ';', '|'). Multiple instances of the input is also still supported.

New Hidden Data question block type

A new Data sub block has been added called Hidden Data, to add Hidden Data directly into a project, or to change an existing visible data block to hidden. Simply change the question type to Hidden Data it in the title of the Inspector panel.

The "Visible" checkbox in the Inspector Panel has been removed for data questions, as this feature replaces that option completely. Existing projects using hidden data will automatically see those data sources as a "Hidden Data" block type.