Theme
- Deployment times for Test Integrations have been improved
- EDI File Viewer
- Notifications Warning
- Quality of Life Improvements
- Email addresses on Flow source connections
- Files and Systems settings in Flows have been split out
Deployment times for test integrations
Integrations can be tested before they are added to a Chain.io License. In an effort to provide time to test Flows in an integration, the Chain.io platform formally set an expiration time of Midnight GMT for all Integration Flows in your workspace that were not attached to a license.
This feature has been improved by extending the time Integration Flows can be enabled without being added to a License. Each License tier has their a specific time interval which is a follows:
- Connect License - 24 hours
- The flows in any unlicensed integration will be disabled twenty-four hours from the time they were enabled.
- Transform License - 48 hours
- The flows in any unlicensed integration will be disabled forty-eight hours from the time they were enabled
- Enterprise License - 72 hours
- The flows in any unlicensed integration will be disabled seventy-two hours from the time they were enabled
Users will now see a warning at the top of Unlicensed Integrations which indicates the time interval for the enabled Flows. In the Integration Settings, users will also see a column in the Flow Table labeled Disables At which indicated when the respective Flow will be disabled
Why we made the change
Initially having the Integration Flows disabled every evening at midnight GMT was causing issues for some of our customers in different global locations. To remedy this problem we have now made all Integration Flows, that are not part of a License, have a time limit that is set relative to when they were enabled for testing. This time limit is based on the type of License your organization has in place.
This should allow customers ample time to test their Integration Flows for implementation into their workflow.
EDI File Viewer
As an enhancement to our in-portal file viewer, users now have the ability to view EDI(*.edi) files in a readable and consumable format.
Why we made the change
We understand that it is important to see all of the files related to an Integration Flow. While Flows supported EDI files in the past, functionality for viewing those documents was not very user friendly. This improvement makes it easier to view the contents of EDI files in the portal.
Notifications Warning
When setting up an Integration Flow, if a user has not included any settings in the Notifications area of the Flow configuration, a warning message will now appear when the Flow is deployed, warning the user that they are deploying a flow that does not have notifications set up.
Why we made the change
Within Integration Flows it is important for users to understand that if notifications are not set, any failure or issue with a Flow could go undetected unless a user logs in and actively searches for Flow executions with errors or issues.
This improvement reminds the user that they should set up notifications before deploying their Flow, so that they or others in their organization can be notified about Flow executions that have addressable issues.
Quality of Life Improvements
We’ve implemented a couple of small quality of life improvements across the app to help your experience.
- Flows that use an email address for Source connections will now display the email address that is used as the source.
- Source Systems and Source File Types have been split out into their own sections in Flow configurations.