Articles in this section

Celigo platform 2023.11.1 release notes

Tom Santiago
Updated

What's new and enhanced

AFE editor: auto-suggestions enhanced

The enhanced auto-suggestions feature eliminates the hassle of scrolling through endless lists by allowing you to easily find the helper or field you need, making handlebars expression writing even more straightforward and eliminating the need to navigate away from integrator.io to external help articles.

Here’s what this enhancement includes:

  • Convenient helper descriptions: Hover over any helper in a list to see a definition of its function, allowing for quick and easy selection.
  • In-app knowledge access: Detailed helper guides are presented within the platform, offering contextual help and assistance for writing expressions.
    • Syntax of the helper: Find the correct syntax without switching between windows.
    • Example usage: See how the helper works in practice.
    • Definition and details: Get a comprehensive understanding of what the helper does and its mandatory or optional arguments.

Introducing OpenAPI specification generation

With the introduction of OpenAPI specification generation, a standardized document is made readily available for exports, imports, and data flows, allowing you to seamlessly embed OpenAPI documentation into your product.

Why this is valuable:

  • Generate OpenAPI specs for exports, lookups, or imports: This standardized document allows you to integrate your Celigo operations into a wide range of applications with consistency and ease.
  • Readily available documentation: Obtain OpenAPI documentation effortlessly, saving time and eliminating manual documentation efforts.
  • Clear usage instructions: The generated OpenAPI specifications include request and response schemas, making it clear how to work with exports, lookups, and imports.
  • External accessibility: By providing a clear and standardized interface, consumers of your products are able to easily understand and interact with your integrations, without having access to your source code.

How does it work?

Whether utilizing exports, lookups, or imports within a flow or as standalone operations, generating OpenAPI specifications is simple. The OpenAPI spec considers filters, transformations, and hooks associated with your operations, ensuring accuracy and completeness.

For exports and lookups, request and response schemas are generated based on the configuration. For imports, the request schema is crafted from the import configuration. In case of mock data availability, response structures are based on that.

When OpenAPI spec generation is not possible, guidance will be provided to update the configuration.

Error management: error tagging, filtering, and sorting

Add tags to errors for easy categorization

  • Tags are created at the account level and can be used across integrations. Any user can create a tag, allowing for better collaboration among teams.
  • Tag multiple errors at once.
  • When applying a tag to an error, and when there are multiple errors with the same retry data key or trace key, tags are automatically applied to those errors as well, saving time.

Simplify the error search process with tag-based filtering

Filter errors by tags with the new filter icon in the Open errors tab.

Sort errors for easy batch selection

A new sorting feature in the Open errors tab provides the ability to choose from columns like Message, Code, Source, Classification, and Timestamp.

  • By default, errors are sorted by Timestamp, with the most recent errors displayed first.
  • When selecting a specific column, errors are sorted by alpha.
  • Errors are sorted in batches of 1,000. When you move to the next batch of 1,000 errors and apply sorting, the platform sorts the errors, including the current and the previous batch.

Test mode: accurate previews, script customization, and mock data flexibility

Preview data now matches selected source

When setting input filters on imports in flows that have multiple sources, the preview data will now correspond to the selected source. This ensures that the selected test run source is visible in downstream steps, allowing you to perform mapping, transformations, filters, and more.

Note: We currently do not support selecting a run source in enabled flows but you can run your enabled flow manually with a single source.

Adapt scripts for test runs with the testMode flag

The testMode flag allows you to customize scripts and observe the resulting behaviors in test mode without altering your production data. The flag is sent as input to all scripts supported by the platform and will be set to false by default.

integrator.io will handle errors and exceptions related to this flag by providing clear error messages or fallback behavior when needed.

The testMode flag is set to true in preview calls as well, enabling the hooks logic configured for test runs to be utilized during previews. This removes the risk of executing unnecessary code in your hooks.

More flexibility with mock data

Several improvements have been made to the way mock data is handled in test mode.

MySQL connector: bulk inserts, automapper support, and updated import types

  • Bulk insert: Recommended for large data volumes, use query type Use bulk insert SQL query to insert data in bulk, either by selecting a validated table name from a dropdown list or by referencing a dynamic lookup using handlebars expressions.
  • Automapper support: Allow the automapper to automatically fetch and populate columns, eliminating the manual effort of adding columns and the need to toggle between applications.
  • Import types updated: The default import type is Use bulk insert SQL query (recommended).

Enhanced file filtering in file transfer exports

These enhancements are designed to improve the file-transfer exports experience, reducing effort and simplifying the file selection process.

  • Expanded filtering options: When searching for files within a folder or directory in a file storage system, advanced filter options are now available, such as contains, does not contain, and more.
  • File size filtering: Prevent exporting empty files, or selectively choose files based on their size.
  • Flexible filter management: Easily tailor exports to meet specific criteria by adding or removing filters, building filter groups, or combining filters or filter groups.

Improved navigation in Celigo Marketplace

These changes are designed to make navigation of the Celigo Marketplace more intuitive and convenient.

  • Streamlined Marketplace home page: When you visit the Celigo Marketplace home page, the most popular assets like Templates and Integration apps will be shown right at the top, making it easier to access what you’re looking for.
  • Enhanced filtering: By application filters have been added to help you discover connectors, with quick access to the top ten applications.
  • Sorting options: Sort assets by Popular, Most recent, or alphabetically in both ascending and descending order.

What's fixed

Fixed data preview for oneToMany imports

Previous behavior: In the past, for oneToMany imports (row-based or record-based, whether pathToMany is set or not), the send feature would send all the child records to the application for processing and display the response of only one child record.

Changes made: Now, when previewing a oneToMany import, the platform will display information for only one child record. The same changes apply to row/array-based data, which will now show and send data for only one row, as well as when pathToMany is configured (record-based data).

Other changes

  • Flow steps using the Stripe connector would revert to the Simple view even if the HTTP settings had been configured, and any non-standard API response pattern values were removed
  • Following the Sept. release, some HTTP connections automatically switched the concurrency level to 25, and the changes weren’t reflected in the audit logs
  • NetSuite Journal update tasks and CustomForm (Name) import mapping failed when upgraded to SuiteApp SuiteScript 2.x
  • Custom list records generated errors in NetSuite webhooks
  • Lookups in HTTP request body for imports failed intermittently when batch size was greater than 1
  • The Entity record type was unavailable for selection from NetSuite saved searches regardless of permission settings

Support: Help Center updates

New connector articles

Revised connector articles

New integrator.io articles

Revised integrator.io articles

New integration apps articles

Revised integration apps articles

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.