Deta Base

The Deta Base connector Service used to define a connection required for associated actions and start events. Examples include Salesforce and Box. Method of integration to cloud services, business applications and content stores. is used to create connections for Deta Base actions A tool for building the processes, logic, and direction within workflows..

The following actions are available:

Use the Deta Base actions to store and retrieve strings in a Deta base. Create, update, delete, and retrieve data items in/from a simple base or a structured object (schema) that is dynamically read from Deta Base. Then use the Nintex Workflow Cloud Integration action, Query JSON, to extract and use JSON data from those strings.

Deta Base schema item actions rely on the

Important: 

Use the Nintex Workflow Cloud Integration action, Query JSON, to extract and use JSON data from connector actions. The Nintex Workflow Cloud Engine v1 does not read data retrieved from connector actions as JSON data. The Engine v1 interprets JSON data as the following key/value pair: "key" => "value", whereas valid JSON would be: "key" : "value". Query JSON will not work correctly in Nintex Workflow Cloud Engine v1 environments. If data you retrieve has the => symbol between key/value pairs, contact Nintex support to find out about the Engine v2 roll-out.

Create a Deta Base connection

You can create connections from the Automate or Designer page.

Permissions

Permissions enable you to manage access for other users to use, edit, and delete connections.

  Use

Edit

Delete

Assign
permissions

Owners

Users

Note: By default, users with administrator role will have the same rights as a Connection owner.

Create a Deta Base data source

Use the Deta Base data source to create a drop-down list of Deta Base data items.

Example:  To allow users to select a specific property value from schema data or an item's data from a data/JSON item in a form, add a drop-down list of data or schema items to the form using a Data lookup control A form control that allows users to select from a drop-down list of values that have been fetched from a third-party service.. The Data lookup control uses a Deta Base - Get schema items or Deta Base - Get data/JSON items data source to list the items available in a Deta Base base in the drop-down.

You can create a data source to:

  • Get data/JSON items: list all the data/JSON items in a Deta base.
  • Get schema items: list all the schema items in a Deta base.

Each data source is configured for a specific project base. You can create as many data sources as you need.

Deta Base data source fields

When you create a Deta Base data source, you can configure some additional fields to specify which items the data source should retrieve.

Section

Field or selection

Description

Add new data source Operation Displays the operations available for the selected Connector. The following fields are displayed:
  • Deta Base - Get data/JSON items:
    • Items per page: The number of items to retrieve per page. Only this number of items are returned. When used with the Last item key field, you can specify which page of items to retrieve. For example, imagine there are 100 items in the base and you set the Items per page to 10 but leave the Last item key field empty. The first 10 items will be retrieved. If you put the tenth item's key into the Last item key field, the next 10 items are retrieved.
    • Last item key: The last data/JSON item's key from the previous page of items.
  • Deta Base - Get schema items:
    • Items per page: The number of items to retrieve per page. Only this number of items are returned. When used with the Last item key field, you can specify which page of items to retrieve. For example, imagine there are 100 items in the base and you set the Items per page to 10 but leave the Last item key field empty. The first 10 items will be retrieved. If you put the tenth item's key into the Last item key field, the next 10 items are retrieved.
    • Last item key: The last data/JSON item's key from the previous page of items.

Considerations

Note: 

The images below are examples taken from Deta Base. For information on Deta Base like how to create a base, see the Deta Base documentation.

  • Deta treats data as a string. You must ensure that JSON data you put into Deta Base is well-formed JSON to be able to use retrieved data in workflows.
  • The Nintex Workflow Cloud Engine v1 does not read data retrieved from Deta as JSON data. The Engine v1 interprets JSON data as the following key/value pair: "key" => "value", whereas valid JSON would be: "key" : "value". Query JSON and Deta Base schema item actions will not work correctly in Nintex Workflow Cloud Engine v1 environments. If data you retrieve has the => symbol between key/value pairs, contact Nintex support to find out about the Engine v2 roll-out.
  • The Deta Base data/JSON actions interact with standard Deta bases which contain only a key and a data column.

  • To use Deta Base schema actions with Nintex Workflow Cloud, you must first have a base called ntx-schema set up in Deta Base. The ntx-schema base must consist of a key column and a column for a schema object. Each base that you want to interact with using schema actions in Nintex Workflow Cloud must have an entry in the ntx-schema base.
  • The ntx-schema key field must be the base name and the schema object must contain the schema definition for that base. This image shows an example of a schema definition with properties, nested properties, and required properties:

    The base described by the schema above might look like this:

    With an example of the likes array:

    And an example of the profile object:
  • The key column in the base example shown above is common to all bases. The key is auto-generated if you do not specify one.
    Note: 

    If the key contains URL unsafe or reserved characters, make sure to URL-encode the key. Otherwise, it will lead to unexpected behavior.

  • In the context of the Deta Base connector in Nintex Workflow Cloud, schema item actions interact with the schema fields as shown in the images above, and data/JSON item actions interact with the data field in a base.

    Data/JSON base in Deta.