- May 2017 (version 3.5.1)
- May 2017 (version 3.5.3)
- June 2017 (version 3.6.1)
- June 2017 (version 3.6.2)
- July 2017 (version 3.7.1)
- July 2017 (version 3.7.2)
- August 2017 (version 3.8.1)
- September 2017 (version 3.9.1)
- September 2017 (version 3.9.2)
- October 2017 (version 3.10.1)
- December 2017 (version 3.12.1)
- Cloning. You can now clone integrations, data flows, stand alone flows, and connection types. For more information, refer to Cloning in integrator.io.
- For establishing a REST API connection, you can now use the Custom Authentication Type.
- For HTTP imports, JSON media type is now supported.
- For the REST API application type, the Skip Argument paging method is introduced.
- The View link when clicked offers you a dynamic list of which records that failed. Earlier, you had to expand the parent flow and then view the list of errors from Export or Import, if any.
- Single session for integrator.io users. You will no longer be able to login into multiple browsers and systems at the same time.
- xHandlebar intelligence has been added to JSON and XML document builder for FTP and HTTP imports.
- Data loader now supports JSON, XLSX, and XML files as well. Earlier, it supported only the CSV files.
- The HTTP connection has a new OAuth 2.0 authentication type.
- For Amazon S3 connection, a new field Ping Bucket has been introduced.
- Improvement in the UI for Integration Marketplace.
The following is how the UI appears now when you click on a tile in the Integration Marketplace.
The following sections describe the enhancements made in integrator.io 220.127.116.11 release.
1.1. Data Loader
You can now upload a CSV file of size 100 MB. Earlier, the file size was restricted to 20 MB.
1.2. NetSuite Export and Import
Revenue Element is now available under the Record Type drop-down list box on the Export and Import pages for NetSuite.
1.3. HTTP Connection, Export, and Import
A new field named as Ping Error Path is added on the HTTP connection page, whereas an Error Path field is added on both the Export and Import pages for an HTTP connection. This field fetches the specific text that is present for an error. For example, the Ping Error Path or Error Path field may contain value like, /ErrorResponse/Error/Message/Text().
1.4. Export and Import Pages
While creating a data flow, you can now provide Name and Description for your Export and Import. These exports and imports are also made available in Orchestration.
1.5. IO Account
You can now change the email ID of your IO account.
Note: When you change the email, a confirmation email is sent on the updated email.
1.6. Integration Restore
You can now restore the deleted integration with the help of the Restore icon in a single click. This option restores all connection types and data flows present in the integration.
Earlier, though it was possible to restore a deleted integration, it was a manual two step process to restore the deleted integration. The steps involved downloading the deleted integration's template, and then manually reinstalling the template in IO. In addition, earlier the manually restored integration used to stay in the Recycle Bin for 7 days, but now it is removed from the recycle bin as soon as the user restores it using the Restore button.
- You can choose an existing connection or configure a new one.
- For NetSuite and Salesforce, you will also have to install the bundle that appears while you are restoring the integration.
1.7. Field Mapping Settings
You now get a pre-populated list of date formats in the Export Date Format field for mapping fields of the Date data type.
1.8. NetSuite Import
For multi-field mapping type, JOIN is now available for NetSuite Import.
1.9. Amazon MWS Connection
While creating an Amazon MWS connection, you can now add or edit an existing IClient using the + and Pencil icons.
2. Issues Addressed
The following issues are addressed in integrator.io 18.104.22.168 release.
- For Orchestration, the export fields now appear automatically on the mapping page.
- In the integrator.io trial version, you can now enable and disable a data flow with ease. Earlier, when you attempted to enable a disabled data flow, you would land on the Sign Up page
1.1. Sign in Page
After signing up on integrator.io, you will now be redirected to the Sign in page automatically.
Earlier, the Sign in page was not presented after successful sign up.
1.2. New Fields
The Debug Mode checkbox is now introduced for NetSuite and Salesforce connections.
1.3. Async Helper
A data flow that has Async Helper configured can now be downloaded as a template.
1.4. Getting Started Page
The all new Getting Started page lets you explore different core product offerings with ease.
- In Orchestration, you can now configure multiple exports using the Add Next Export option under Page Generators.
- In orchestration, Parent and Child Exports are now supported. In the following image Export 2 is a child export of Export 1.
- In Orchestration, you will now be able to share the orchestrated flows and connections.However, if you don't share all the connections used in the orchestrated flow, you will be unable to edit the orchestrated flow.
- You can edit only those Exports or Imports of which connections have been shared with you.
- You can run the data flow only when all the connections involved in the orchestrated flow are shared with you.
1.6. New Adapters
For HTTP and REST API connection types, you can now establish an Asana, Box, Dropbox, or DocuSign connection using OAuth 2.0 as the Authentication Type.
1.7. HTTP Connection Type
1. For an HTTP Connection Type that has Basic as Authentication Type, you can now enter HTTP headers using the HTTP Headers button.
2. While establishing an HTTP connection, the Base URI field now has stricter validations. An error is returned immediately before the request is sent to the server eventually increasing efficiency.
1.8. FTP Data Flow
The files on the Dashboard of an FTP data flow, which are also available for download, now have the filename and extension same as that of the server. Earlier random numbers for the file were generated, which made identification of the downloaded files difficult.
1.9. Field Mapping
While configuring a data flow, on the mapping screen, you can now sort an array of characters alphabetically, and an array of numbers in an ascending using the Multi-Field Field Mapping Type.
1.10. Outdated integrator.io
The integraor.io app now gets refreshed automatically after every 30 minutes to check whether you are using the latest version of integrator.io. This helps us prevent any issues that occur due to an old version of integrator.io.
The following image describes the message that appear in case you are using an outdated version of integrator.io.
- Sign Up Process. Improved the sign up process. For more information on the sign up process, refer to Signing Up for integrator.io.
- New button. The new What's New button in the UI now takes you to the latest release notes.
- Establishing Connections. You can now establish connections successfully even if your connection data contains an array.
- New fields. For a data flow that involves an HTTP connection, the following fields are now made available:
- Last Page Status Code
- Last Page Path
- Last Page Values
- Webhook Providers. We have Travis as a new addition to the list of Webhook providers.
- Production and Sandbox environments. You can now switch between Production and Sandbox environments with ease. To get this feature enabled, please get in touch with Celigo Support.
- For an HTTP import, you can now map fields using static and dynamic lookups. For more information, refer to HTTP Import: Static and Dynamic Lookup.
- Canceling Data flow execution. From the dashboard, now when you cancel the flow execution, the execution gets canceled immediately. Earlier, in spite of canceling the data flow execution the entire data from the Export used to get exported.
Note: The execution of the data flow gets canceled immediately. However, there could be an increase in the number of pages exported because by the time you canceled the data flow execution some amount of data was already exported.
- Parallel execution of data loader flows. When using Data Loader, you no longer have to wait for your first data loader flow to complete. We now execute all the data loader flows in parallel. Therefore, even if any of your data loader flow gets stuck, it won't hamper the execution of the other data loader flows.
- Retrying data flow execution. For retrying data flow execution, you can select the checkbox beside the data flow name and select Retry. Earlier, you had to expand the data flow and select the export or import to retry.
- NetSuite Adapter. On the Mapping screen, the login process of the NetSuite adapters has been improved, and you can also preview the data for NetSuite sub-tabs.
- FTP Export. For a data flow that involves exporting multiple files using an FTP export, you can now download all the files from the dashboard. Earlier, only the first file use to get downloaded in spite two or more files being selected.
- Basic NetSuite Connection. Now when you establish a Basic NetSuite Connection, you will be asked to enter Email and Password only. Once you validate the NetSuite credentials using the Validate button, the Environment, Account, and Role fields are filled with appropriate data.
- The integrator.io URL is now much more secured. Anyone who tries to encode the URL is now given an error message.
- You can now publish your connectors on the Marketplace if the allowedToPublish property has been set to true for your integrator.io profile. Please contact Celigo Support for enabling this feature.
- Chargify, SurveyMonkey, Stripe, and Zuora have been introduced as new Adapters.
- For Orchestration, you now have the oneToMany support for exports present in Page Processors.
- Handlebar support for static lookups.
- On the mappings page, the Discard If Empty field has been introduced. This field discards export fields that have an empty string.
Note: The Discard If Empty field does not work for a NetSuite import.
- For REST API connections, to enhance security, you are no longer provided with encrypted connection details in the debug logs. Earlier, when you downloaded debug logs from Menu > Connections, you could see connection details in an encrypted format.
- In Orchestration, Webhooks, Distributed, and Simple exports are no longer available on the Page Processors section.
- While performing a static mapping, the Export Field and Import Field column headers now also include the application name as shown in the following image.
- Async Helpers can now be shared and can be used in templates.
- For HTTP imports, XML support has been introduced.
- Both Production and Sandbox accounts will have the same license, provided you have license for both Production and Sandbox accounts. For example, if your Production account has Standard license of 8 Flows, your Sandbox account will also have a Standard license of 8 Flows.
- IO is now safe against the Billion Laugh attack.
- Data flows using the Docusign Adapter now run without throwing any errors.
- For a data flow, when fields were added using Settings > Field Mappings, integrator.io was unable to save the fields.
- Export preview error for NetSuite is now resolved.
- When using Orchestration, you can now export attachments from your Export applications. For example, if you are exporting data along with attachments from NetSuite to Salesforce, you will have to create a NetSuite export in Page Generator, and then create another NetSuite export under Page Processors, where the Application is selected as Blob.
Note: You can export attachments from an export that is under Page Processors only.
In the following image, you can see that data is exported from NetSuite under Page Generators. Under Page Processors, you can create another NetSuite export that exports attachment with the Application type as Blob. On the import side, you create 2 Salesforce imports, one for importing data into Salesforce, and the other of the Application type as Blob for importing the attachment.
- On the NetSuite Export page, Server Script Log is now available in the Record Type drop-down list box.
- On the mappings page, the Discard If Empty field , if selected, also discards fields that contain NULL.
- The How Should the data be mapped? section is now introduced for an Import in Orchestration. In addition, this change is also made for Standalone Imports.
- When the data flow is executed, the content-type header is added dynamically (in the back end) based on the Connection Media Type.
- The Define Search Criteria button has been introduced for NetSuite exports.
- In Orchestration, you cannot use a real-time export under Page Processors. A real- time export has to be the first export under Page Generators.
- In Orchestration, when a Parent job is canceled, the child jobs are canceled automatically.
- Improved UI for:
The login page.
The Forgot Password page.
- Issues related to the Walmart adaptor are now resolved.
- Issues related to NetSuite saved searches that contained the SUMMARY TYPE as Group are now resolved.
- You no longer have to raise a separate request for enabling Orchestration for the Standard edition of integrator.io.
- You can now connect to NetSuite Sandbox 2.0 using a basic connection.
- For REST API, Token and LinkHeader paging methods have been introduced.
- The Sample Response Data field has been added on the Import page. This field has to be filled up manually, and all the fields of the Sample Response Data are made available on the Response mapping page.
- On the dashboard, when you select one or more jobs for marking them as resolved or to retry, the following UNDO message appears.
- For establishing a Salesforce connection, a new drop-down list box called as OAuth2 Flow Type has been introduced.
- Google Contacts, Google Mail, and Google Sheets are the new Adapters introduced.
The following image describes the API endpoints available for Google Contacts.
The following image describes the API endpoints available for Google Mail.
The following image describes the API endpoints available for Google Sheets.
- Support for PostgreSQL has been introduced in integrator.io.
Note: As of now, you can only connect to PostgreSQL and export the data.
- The concurrency level for NetSuite has now been increased to 25.
- Issues pertaining to the NetSuite export with Document as the record type are now resolved.
- Issues pertaining to an HTTP export of type CSV having multiple rows per record are now resolved.
- In Orchestration, for a Salesforce real-time flow, issues pertaining to Opportunity and OpportunityLineItem are now resolved.
- The Webhook application type now supports all XML content types.
- Token authentication is now supported for the Webhook application type.
- Data Flows is now renamed to Integration Flows.
- For a token based HTTP connection, Base URI and Media Type fields are now moved up the order in the UI.
- The following is a list of new Adapters:
- Production and Sandbox environments are now available for a Shipwire connection.
- Async import flows are now supported in the IO Sandbox environment.
- You can now clone an integration to a Production environment or a Sandbox environment.
- You can now clone a Flow to a Production environment or a Sandbox environment.
- Now when you delete an integration, the UI clearly states that it is being deleted.
- Issues pertaining to Magento and NetSuite data flows are now resolved.
- Flow scheduling issues have now been resolved.
- integrator.io now supports export of data from MySQL.
- User Management and Transfer Ownership.
- EDI Support.
- jsonEncode is a new helper method introduced for use in handlebar expressions.
- While importing data using an HTTP application, you can now use the Composite method as well.
- For REST API applications, Patch is now available as a method for importing data. For example, GitHub uses the Patch method.
- On the Home page, legacy integration (Unification) tile(s) will appear disabled if one or more of their connections are offline. You can click the Connection Down! link present in the disabled tile to make the necessary changes for restoring the connection(s).
- Authentication Fail Status Code, Authentication Fail Path, and Authentication Fail Values are the new fields added for the HTTP connection type.
- The Borrow Concurrency From feature is now available for all the connection types.
- While resolving an integration error, the Undo pop-up now appears for 7 seconds instead of 3 seconds.
- For the Free tier, the 4-pack add-on is now available for the Orchestrated flows.
- Date Format and Time Format fields have been introduced at My Account > Profile.
- On the integration dashboard, the Clear button is added to Pick a Date Range.
- On the Integration Settings page, when a flow's link is clicked and if the flow's connection is inactive, the link to the connection pops up immediately.
- The following image is an illustration of how the link to the connection would look like if the connection of the flow is inactive.
- An error occurred if an apostrophe was present in the import data. This issue is now resolved.
- Issues pertaining to the use of Dynamic Mode have been resolved.
- The ESOCKETTIMEOUT error has been resolved.
- Issues with the NetSuite Shipping table are now resolved.
- Empty query clause error has been resolved.