Celigo platform 2023.9.1 release notes

What's new

Introducing Transformation 2.0

Transformations allow you to modify source records before being processed by your flows. Simplifying complex source records before being processed by your flows is often a best practice for making flows easier to build and maintain. The new transformation 2.0 functionality addresses all the pain points and shortcomings of transformation 1.0 and makes transforming records much easier to visualize, build, and test.

Key features:

• Make targeted changes to input records: You no longer need to redefine the entire output record structure, and it is now possible to make targeted changes to input records, while keeping everything else in the input record as-is.
• Remove fields: Effortlessly remove unwanted fields from the input record.
• Create complex data structures: You can define brand new records from scratch, and now there are 2 specialized modes to create record vs row[] based data.
• Access to custom settings: You can access custom settings in your transformation rules.
• Handlebars and lookup support: You can use handlebars expressions in your transformation rules to build complex field values, or define static lookup tables to translate field values between systems.

Auto-recovery for rate limit errors

• Automatic error resolution: integrator.io’s new intelligent error recovery procedure automatically handles rate limit errors, saving you the time and effort it takes to perform manual troubleshooting.
• Take control: Whether you decide to enable or disable auto recovery for rate limit errors, you’re in control of your integration process.
• Detailed audit logs: Track the recovery procedure in your audit logs, following along as settings are adjusted and requests are retried. 

New universal connector: JDBC

Scheduled to be released on October 10th

• Establish JDBC-based connectivity with your on-prem databases, regardless of the availability of dedicated connectors.
• Use your own JDBC driver to connect to your legacy database systems.

Enhanced debugging capabilities for flow test runs

Keep the feedback coming, we’re listening.

• NetSuite SuiteScript hooks are now supported for test runs, allowing you to see how the scripts are modifying the incoming data. 
• For mock data fields, the option to Populate with canonical stub has been added allowing you to simply copy/paste your JSON mock data, removing the need to manually format the data.

Left navigation redesigned

• We’ve improved the accessibility of important features like Flow builder.
• The simplified menu definitions mean you don’t need to hover over an icon to understand what it does.
• You’ll see faster load time thanks to the consolidation of options.

Enhanced configuration for HTTP connections

JWT Bearer authentication is now supported for universal OAuth 2.0 connections:

• Generate secure JWT tokens using signature methods such as RSA-SHA and HMAC-SHA.
• Invoke APIs securely using JWT tokens, ensuring efficient data exchange between systems.

UI enhancements for Amazon Redshift and Microsoft SQL cloud connections

Enhancements for Amazon Redshift and Microsoft SQL cloud connections.

• Effortless mapping: Select your destination table effortlessly from a dropdown list that retrieves data directly from your connection settings. This list not only includes tables from your connection settings but also comprehensively covers all tables in your cluster and databases, eliminating the need to modify your connection details.
• Seamless mapping: Allow the automapper to automatically fetch and populate columns, eliminating the manual task of adding them and the need to switch back and forth between integrator.io and Redshift.

For Microsoft SQL, this update applies only to cloud-based connections. Agent-based connections will receive the same update in a future release.

Improved experience for running scripts

New postResponseMap scripts on lookups will run per page of data.

• Consistent experience: postResponseMap scripts on lookups now run exactly as they do on imports, so you can expect the same behavior from all of your scripts.
• Streamlined operations: Iterate through each child record to perform any necessary calculations without the need for additional flow steps.

Things to remember:

• Existing scripts (prior to this release) will continue to run for every record or every child record, and they cannot be forced to run per page. 
• Existing scripts that are cloned will still run for every record or every child record. 
• If you want your existing scripts to run per page, you must copy the script text, create a new script, and paste the text of the old script into the new.

integrator.io will now automatically detect connector application

• Upon establishing a connection through the universal HTTP connector, integrator.io will automatically recognize any endpoint for which a prebuilt option exists.
• Once the universal HTTP form is saved and closed, your endpoint will display the prebuilt connector name if one exists. When reopened, you will be presented with the simple form view for the prebuilt option.
• To customize your connection further, you can always toggle to the HTTP form view. Any configuration initially set up in the universal HTTP connector form will transfer over.
• You’ll also see this enhancement apply to your existing HTTP connections over time as we release periodic updates to detect endpoints for which there are prebuilt options.

Clearer insights into account endpoint usage

We’ve simplified your view of endpoint utilization.

• See your usage clearly: Under the Subscriptions tab within My account, you can now easily view the exact number of endpoints you’re using against your endpoint entitlements.
• No more surprises: Worried about exceeding your endpoint limit? Don’t be. integrator.io will prompt you when you’re building a flow that will exceed your maximum endpoints, preventing any unexpected hiccups.

Additional hmacOptions fields

We’ve added three additional hmacOptions fields for including signatures in an API request body:

• hmacOptions.headers: Path to parameters sent in the request header.
• hmacOptions.bodyParametersMap: Path to parameters sent in request body.
• hmacOptions.urlParametersMap: Path to parameters sent in request URL.

New connectors

Find complete instructions and popular integration scenarios – along with connector resource enhancements – at Celigo platform connectors 2023.9.1 release notes.

What’s fixed

• After initially editing error retry data, the errors displayed incorrectly when reopened
• NetSuite File Cabinet file transfers caused errors when a lookup attempted to retrieve the files as BLOBs
• Flow schedules without a start time ran as expected but displayed incorrect run times
• Branched flows with a lookup experienced abnormally long run times and were unexpectedly canceled
• In real-time Salesforce flows, changing the connection cleared the base URI value for the environment, causing the flow to fail
• Handlebars expressions in a mapping lookup couldn’t be interpreted for NetSuite SuiteScript 2.0, when the import had a delete operation
• One-to-many lookups failed when using postResponseMap hooks
• NetSuite vendor sublist imports were overwriting the first line instead of adding a new line

Highlight: you report it, we fix it

FTP JSON files were not processing handlebars that were sitting outside of an {{each}} code block. Your feedback brought this issue to our attention. We made changes to handlebars written before or after an {{each}} code block. The expressions are now processed with the file, but only if the expression includes custom settings and does not include records fields as input (data) outside the {{each}} code block.

Who this is for?

Anyone creating FTP imports with JSON files.

What’s required of you?

When creating an FTP import with JSON that includes an {{each}} code block within a handlebar template, be sure to include custom settings and to omit handlebars which have fields based on records.

Celigo University

If you have any feedback about the courses, please email university@celigo.com.