Changelog version 7.1.1 - October 2020


We've added even more advanced calculation features.

Calculated selection fields

Yes, you read that correctly! We've found a way to make this highly requested feature a reality.

Selection list option values

You can now access a selected option's source values. For example, if there's a selection field based on the user list, you can now access the selected user's name, email address, user group name, etc.

Off spec check

You can access any selection or numeric value's spec check result in calculations.

All together now

Suppose an analysis set has a selection field called customer_ (based on a customer list) and a numeric field called volume.

You wish to have the selection field select a user (based on the user list) automatically set to the user named "Manager" if the customer has premium support (as stored in the customer list field called premiumsupport_) or if the volume is off spec. Otherwise, select the user named "Regular".

Just create a calculated selection list with the following calculation:

{customer_}.option.premiumsupport_ or {volume_}.offspec ? {"Manager"} : {"Regular"}

API enhancements and logging

This release also empowers developers and system integrators with new API features.

Bearer authentication

The API now supports the Bearer authentication standard. This enables you to send the authentication token in a request header, which increases security.

Note: this standard specifies that the token is sent in a parameter called access_token when passed in the URL or post body. To keep backwards compatibility, authToken is also supported. No changes are required for existing integrations.

Check out our GitHub repo for example code in four languages if you haven't already.

Minor improvements

  • Both storeResults and storeSpecificationVersion now support unix time stamps for dates.
  • You can download attachments with getResults.
  • getResults and storeResults provide/accept the internal id. This can help in cases where there's no other good key field.

Log files

Admins can now browse the API logs from within the application. (You'll find the link in the Management menu.)

Logs for message rule web hook calls are also available.

This should greatly help with debugging.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.