Tonkean Feature Updates - May 2020

What’s New In May
 

We’re always working hard to make Tonkean more powerful and easier to use. Here are a few of the big improvements we made this month.

1. Multi-value Dropdowns
2. Tabular forms
3. Brand new Formula Editor
4. Custom Data Retention Configuration
5. HTTP Upload Action
6. Custom Data Sources - Outgoing Authentification Configuration
7. Many new Data Source integrations!
8. Three new formulas!

Features
 

Multi-value Dropdowns

Before: Dropdown fields only supported one selected value.

After: The new dropdown field allows you to define whether the number of choices the user can set will be single/multiple.

How does it work?

• Create a new dropdown field.

• Select “Multiple” for the number of choices.

• Define whether users can add options to the dropdowns.

• Set options manually or take the options from another field.

• That’s it, the field is now configured and is ready to use in the live report and forms.

Tabular Forms 

Before: A form question only supports a single answer.

After: There is a new type of “Collect inner items” form, which allows the user to provide multiple answers to the same question in a tabular view. Each answer will be saved as an inner item under the parent question.

How does it work?

• Create a new update form.

• Select “Collect inner items” as the Form Type.

• Set the question you wish to ask the user.

• Define the fields the user should be filling in for each answer.

Formula Editor

Before: Formula editor used to be a text-based editor that only allowed expert users to write advanced formulas

After: The new formula editor allows all users to build complex formulas in an easy way. Here’s how: 

• Empowering the user to explore all the available functions

• Validating and showing the required function parameters and suggesting relevant values 

• Allowing a basic function view within a complex formula (for example, a regex viewer for a regex find function)

How does it work?

• Create a new formula field.

• Start filling the empty placeholder by selecting Formula/Field/Manual Value

For example, let’s build together a formula that generates the date of an email that was sent to our Module in a specific format.

1. Add a new formula field.

2. Fill the placeholder with a “To Date” Function.

3. Start filling the function parameters placeholders:

   1. For the input placeholder, we will select the email “Send Date” Field.

   2. For the Date Format, we will select one of the preset values: “MM/dd/yyyy”

   3. For the Zone Id, we will select one of the preset values: America/Los_Angeles

Now when the formula is set we can easily improve it; we can:

1. Revert changes.

2. Wrap existing values with other functions.

3. Replace/Clear/Delete existing values.

Data Retention

Before: Data sources were being saved for a pre-set number of days.

After: We added a new capability to our data sources configuration; now you can easily define what entities you wish to collect and for how long this data should be saved.

How does it work?

• Select a specific data source and click on the “Edit” button.

• The new data retention settings will be located under the authentication box.

• Select the relevant entities you wish to collect.

• Define for each of the entities their time to stay: Indefinite/X days to stay

HTTP Upload

Before: There was no way to upload files using the flow.

After: We added a new action called “HTTP Upload” that allows users to send an HTTP request with the desired attachment from a data source storage/public URL/Upload File.

How does it work?

• Add a new action to the flow.

• Select HTTP Upload.

• Set the upload URL.

• Select one of the file sources:

  • Existing storage (connected data source of type Google Drive/Dropbox/Ironclad) and define which file to select or;

  • A public URL that the file will be downloaded from or;

  • Upload a file from your computer.

Custom Data Source Outgoing Configuration

Before: The user would have to configure authentication headers for every custom data source action.

After: We added a new capability to our custom data sources; now you can easily define how every action authentication will look. No more needing to hard code headers in an individual outgoing action.

How does it work?

1. Define a base URL that every action path will be derived from.

2. Add authorization to your requests, define relevant headers, and encrypt the value. Now every request will include those headers.

New Data Source Integrations + Actions

• New Data Sources

  • Smartsheet workspace

  • Ironclad

  • Jira - Customers (Jira Service Desk)

• New Data Actions

  • Asana 

    • Duplicate task

    • Add Owner

    • Add to section

  • Outlook

    •  Send mail

  • Smartsheet workspace

    •  Move sheet to folder

    •  Copy all rows to another sheet

Formulas

1. Reduce Aggregation - We added a new aggregation of type “Reduce.” Use this aggregation to get multiple matching items in one result concatenated by a separator. For example: let’s assume our items in the module represent folders in GDrive. Using this function, we can save in one field all the file names under this folder.

2. XML Path - Will return the value(s) of a given XML path from the XML content.

Format: XmlPath(, )

Example #1: XmlPath("<note><to>Ben</to></note>",  "$.to")

Output #1: Ben

3. Generate Unique ID  - Will generate new randomly generated id of type Number/String(GUID).

Format: UniqueId()

Example 1: UniqueId(“String”)

Output: cd4e11bd-34fe-4011-bb55-d75eaba9a57b

Example 2: UniqueId(“Number”)

Output: 6760879240802974