Versions
4.12.0
Supported Pages Components Guides
Released on: Wednesday 23 March 2022
General Improvements
- 1839 Enhanced transport mechanism for Flows and Flowlinks. In addition to synchronous and queues, also asynchronous is now supported. More info on the transport mechanism in Flows documentation and Flow links documentation.
- #1783 Redesign of the global variables on the Settings page.
- #465 Better default performance profile. Improving general performance.
- #1841 Add support for Constant (fixed values) and Groovy expressions for the setHeader/setHeaders component.
- Add JsonPath support for:
- #469 The setHeader/setHeader component.
- #1849 The contentRouter component.
- #1854 The filter component.
Components Improvements and Fixes
- Various fixes and improvements for the SQL Component:
- #455 Add a default column name when it's empty.
- #456 Using ${body} is now possible to use in a SQL query.
- #457 SQL Component now accepts all kind of operations.
- #458 Escape JSON strings, that may exist on a SQL query.
- #459 Support sha256 protected passwords for MySQL version 8.
- #462/#1817 Add TLS version into SQL Component, for MySQL databases.
- #1807 Migrate SQL component to React.
- #471 Invalid XML characters #1003 - new regex to validate column names.
- Various fixes and improvements for the HTTP Component:
- #1965 #138 New option to set a custom user agent.
- #1915 Fix retry mechanism for dynamic urls.
- #1911 Cast exception on HTTP Inbound call with the instance.
- #1900 HTTP connection resets - Include onException SocketException.
- #1823 FTP initial delay set to default of 60000ms.
- #1733 Throttling component - minimum time period validation.
- #491 Simple Replace component - Problem with blank response solved.
- #476 EnrichCurrentComponent - Add Use Error Route as option.
Other Changes/Fixes
- #1834 Flowlinks - add block and timeout arguments when using synchronous. (less timeouts when linked flow isn't started yet).
- #1775 Delay issue when sending messages from multiple flows using queues as transport mechanism.
- #1846 Installing an existing flow (undefined error).
- #485 Update jcifs library (for better support of the SMB-3 protocol and blocking of SMB-1 version).
- #482 Change the limit of jms max reconnection attempts to 10 instead of unlimited.
Migration
- From this release we start to modernize our technology stack. Our first step was to migrate the user interface. The Flow Manager, Tenant Manager, Instance Manager and Settings are migrated to the React Framework. Also various components were migrated. More in the next release.
4.11.2
Released on: Wednesday 30 June 2021
We reverted some changes that didn't work as expected which caused some components to behave in a weird way after a restart of the back-end.
4.11.1
Released on: Thursday 27 May 2021
Improvement
- #1690 We improved the memory allocation in the back-ends.
Bugfixes
- #1675 We fixed a bug that made it impossible to search on breadcrumbId's in the transactions of an installed flow.
4.11.0
Released on: Wednesday 12 May 2021
New features
- #1579 We updated Elastic Search to the latest version. This also means that the flow logging and tracing will be reset after updating to this version. In combination with the update we also improved the processes that store logging and tracing so that it will be faster and more reliable. The new version also introduces a lot of new improvements and bugfixes which will benefit the stability and reliablity of the system.
- #1629 + #1648 We updated ActiveMQ to the latest version and at the same time we also improved the configuration for it. The improved configuration will remove some warnings that were reported in the flow logging and it allows flows to properly reconnect their queues when a connection fails. The new version also introduces a lot of new improvements and bugfixes which will benefit the stability and reliablity of the system.
Improvements
- #1563 We made several improvements to the health checks:
- The flow bundles reports now also detects flows that failed to install or are still installing. This will also show up in our monitoring.
- The AMQ report now timeouts after 30 seconds, because when ActiveMQ is under heavy load it could take too long to get the information which would trigger a NGINX timeout. This ensures that the general health check always returns the other reports.
- The Dovetail version has been added to the instance report.
- #1636 We added a new option to the Excel to XML component that allows to disregard empty lines/sequences so that they are not included in ther resulting XML.
- #1645 We reduced the logging of some components so that the flow logging shows more useful logs. These components are:
4.10.1
Released on: Wednesday 24 february 2021
Improvements
- #1490 We made some improvements to the flow versions in the flow designer:
- Installed versions are fetched asynchronously instead of synchronously.
- The versions tab now has a loading indicator for fetching the list of flow versions and for fetching the installed flow versions.
- #1563 We made some improvements to the health reports:
- Response status is now always
200 OK
. - Ignore some warnings in the ActiveMQ report that are not important.
- Issues in a report are now returned inside an array instead of in a string.
- Response status is now always
- #1577 We added a new advanced option to the HTTP component that allows to decouple the Dovetail managed SSL certificates store. In very rare cases this could be necessary.
Bugfixes
- #1558 We fixed the encoding error of special characters in environment variables and encrypted global variables.
- #1606 We fixed a bug in the Throttling component and in the Retry mechanism of the HTTP Component that could cause the mixing of headers between exchanges.
4.10.0
Released on: Monday 1 february 2021
New features
- #1440 We added a new RabbitMQ component.
Improvements
- #1424, #1507, #1563 We improved the reports that are generated by the health check endpoints.
- #1571 Files placed on the server by the File component will now survive an update of Dovetail. This is enabled after updating to this version so updating from 4.9.0 to 4.10.0 will not keep the files, but updating from 4.10.0 to 4.11.0 will keep the files.
Bugfixes
- #1110 We now show the actual tracing setting of the installed flow in the Flow manager and not of the last saved version.
- #1545 We fixed a bug that caused an error in the Excel to XML component when the selected range contained empty cells.
- #1569 We improved the calculation of the pending exchanges. In very rare cases it was not accurate and could lead to pending exchanges not being processed by the Throttling component.
- #1413 We fixed a bug in the JSON to XML component that caused nested arrays to not be processed correctly and in turn this caused missing data in the resulting XML.
- #1334 We fixed a bug in the XML to JSON component that caused namespace attributes to not be removed properly which generated an error.
- #1564 We fixed the configuration for sending user creation and forget password e-mails.
4.9.0
Released on: Wednesday 9 december 2020
New features
- #1520 We added new EDIFACT transformations to the EDIFACT Standards to XML component and we also have new transformations from XML to EDIFACT Standards so we have created a new component for that.
Improvements
- #915 We made several improvements to the FTP Component:
- Add options to sort on name or data.
- Add option to only process a certain amount of files on each poll.
- Add option to move picked files to an error folder when there is an error.
- Add option to upload the private key file instead of specifying a path.
- Add option to switch between charset and binary.
- Allow both password and private key file to be specified for SFTP authentication.
- #1481 We added a lot of new UN/EDIFACT formats to the EDIFACT to XML component and the XML to EDIFACT Component.
- We made some improvements to the HTTP component:
- #1495 We added a new authentication method called
Mutual SSL
which allows to authenticate with API's via a password protected private certificate. - #1510 We added a new HTTP method
Delete with body
. - #1530 We deprecated the NTLMv2 Component and added a new authentication method for NTLM to the HTTP component.
- #1540 We improved the working of the retry mechanism.
- We improved the certificate validation of more advanced HTTPS URL's.
- #1495 We added a new authentication method called
4.8.9
Released on: Thursday 28 October 2020
Bugfixes
- We fixed two bugs in the Throttling component:
- #1499 A synchronous flow with a Throttling component could not be installed.
- #1508 The Throttling component now always needs a connection on the right to prevent mistakes which could lead to increased disk space usage caused by unprocessable messages.
- We fixed a two bugs related to the retry mechanism of the HTTP component:
- #1500 It didn't work properly in synchronous flows.
- #1505 The
Exclude headers
didn't work together with the retry mechanism. Excluded headers were not set back after the HTTP request.
- #1503 We fixed a bug that corrupted passwords with certain symbols in the SQL component. This caused the login to fail when it was running in a flow.
- #1511 We fixed a bug in the File,
FTP and Samba components
so that the
Delay
andInitial delay
fields are not validated when theForce inbound
is set toYes
. - #1512 The File, FTP
and Samba components in older flows will get a proper
default value for the
Force inbound
field. - #1514 We fixed a styling bug that caused the tenant dropdown to be overlapped by the validations sidebar in the Flow designer.
4.8.8
Released on: Thursday 15 October 2020
Improvements
- We improved the calculation of the completed, pending and failed exchanges in the statistics for the Flow Manager. The statistics are calculated in the background and not on demand. This decreases the load time of the Flow Manager when many flows are installed. This also means that the shown statistics can be a bit "older", because they aren't calculated on demand. The statistics can still be requested on demand for each flow by going to the details of a flow.
4.8.7
Released on: Tuesday 29 September 2020
New features
- #1411 We added new connection settings to the HTTP component so that the throughput can be increased/decreased depending on how many messages the endpoint can handle. The defaults of these settings are set in the server configuration so we can increase/decrease them when needed. When we do this before the deploy of this release all HTTP components will get the new defaults, but when we change it after the deploy of this release only the new and not opened HTTP components will get the new defaults.
Improvements
- #1464 Now we show
Loading...
instead ofundefined (#undefined)
while the data of a flow is being fetched on the flow details page. - #1471 The navigation bar is now sticky. When you scroll down on longer page (e.g. flow manager, settings,...) the navigation bar will stay at the top of the screen.
- #1220 + #1300 We improved the Throttling component. The messages are now stored in a queue in ActiveMQ instead of in memory. This reduces the memory consumption of the component when throttling many messages. Because of this change simple expressions don't work anymore in the Max requests field.
Bugfixes
- #1463 We fixed a bug that caused warning messages from ActiveMQ to show up
in the flow logging for components with exchange pattern options that are set to
One way
. - #1464 We fixed a bug that caused an error message to show up in flow details page when switching tabs while the details were still loading. This error message should only show up when flow data is not loaded correctly, but in this case all flow data still loaded correctly.
4.8.6
Released on: Friday 11 September 2020
New features
- #1304 We added a
pending exchanges
flow statistic to the Flow manager tables. This will show you how many messages each flow is still processing. This also replaces the high load notifications. - #1381 The HTTP component has a new user interface that provides better support for the user when configuring the component. It also has a new retry mechanism that can be turned on to store and retry requests that failed because the HTTP endpoint was unavailable.
- #1443 It is now possible to increase the amount of concurrent connections that each HTTP component can open. This increases the throughput of all HTTP components that are running in flows. Please note that this has to be configured by us in the server configuration and needs a redeploy to apply it to all running HTTP components.
Improvements
- #1380 We improved the user interface and user experience of the
File component, FTP component
and the Samba component.
Only the settings that apply will show up now to avoid confusion. This provides
better support for the user when configuring the component. The component can
either be inbound or outbound based on how it is connected to other components
in the flow. There is also a new option
Force inbound
that can be used to consume files in the middle of a flow without putting it below an Enrich component. - #1408 The format of the Inbound HTTP URL's has been changed for better compatability with planned changes in Dovetail. The older formats are still supported, but are not shown in the UI anymore.
- #1410 We added automatic cleanup of stale messages in queues of ActiveMQ. Messages that stay in a queue for 24 hours will be removed.
- #1166 The max body size of the Inbound HTTP component has been increased from 1MB to 10MB. We also made it possible to increase this by changing a configuration setting in the server configuration. Please contact us if you need a higher body size.
Bugfixes
- #1391 Support special characters in the password of the Samba component.
- #1438 The NTLMv2 component now also supports HTTPS URL's.
4.8.5
Released on: Monday 18 May 2020
Improvements
- #1186 We added a new
Exclude headers
option to the HTTP component. It allows to exclude specific headers from the exchange so they are not included in the HTTP requests. - #1199 The Failed Exchange component
doesn't retry failed exchanes by default anymore. We set the
maximumRedeliveries
to0
. - #1241 The HTTPS URL's of the Inbound HTTP
now don't include a specific port anymore and look nicer. This also improves the
support for applications that don't support setting specific ports on URL's.
- Attention: existing (old) URL format still works so it is not necessary to change the existing URL's. See Reaching the webservice in the Inbound HTTP documentation.
- #1248 Better response status handling in the NTLMv2 component. The correct response status is returned when there was an error.
- #1312 Properties modals of components that have an updated UI can now also be stretched vertically instead of only horizontally.
- #1326 We updated the Samba Component:
- It can now be properly used in combination with the Enrich component.
- It now supports version 2 of the SMB protocol.
- #1347 When the Recipient component is set
to
Request reply
it now indicates which recipient will be used as response to the caller. - #1358 The input labels are a bit bolder in the component properties modals with an updated UI.
- #1364 We made two improvements for the
Excel to XML component:
- The XML Node names don't have to be unique anymore.
- Invalid XML characters will be filtered out from the header row values
automatically, when the
Has header row
option is enabled.
- #1371 Remove some AMQ settings which limited the amount of components that could be used in a flow.
- #1377 We made some small improvements in the SOAP component:
- Higher connection and socket timeouts when fetching WSDL's for slower SOAP services
- Better logging related to the SOAP WSDL cache.
Bugfixes
- #999 We fixed the format of the datetime values of the
Last completed exchange
andLast failed exchange
in the details view of a flow in the flow manager. - #1114 The password editor in the Tenant Manager mail settings doesn't show the passwords in plain text anymore.
- #1288 The root tag and array element name validations in the JSON to XML Current component are now only executed when the correspondig inputs are visible.
- #1249 We fixed a bug that caused Dovetail to set session cookies with a fixed expiration date in the browser. This could lead to users not being able to login after some time.
- #1346 We fixed the behaviour of the Recipient component
when it is set to
One way
. The incoming body will be properly returned now.
4.8.4
Released on: Wednesday 1 April 2020
Deprecations
- #1244 We removed the Bol component, because it still used the deprecated API of Bol.com. The Bol API is now simpler so a custom component is not necessary anymore.
Improvements
- #1306 We added the following new marketplace regions to the
Amazon component:
- Netherlands
- United Arab Emirates
- Saudi Arabia
- Singapore
- #1322 We now import the groovy-json module so its functions can be used in the Script component.
Bugfixes
- #1247 We fixed the URL of the NTLMv2 component. Whitespaces are now allowed in it.
- #1248 We fixed the error codes of the NTLMv2 component. It now returns the correct error code when the request failed.
4.8.3
Released on: Wednesday 18 March 2020
Bugfixes
- #1293 We fixed a bug in the Split component related to the changes we made for the exchange pattern option. Along with this we also made some other improvements related to exchange patterns.
4.8.2
Released on: Tuesday 17 March 2020
Improvements
- #1273 The Email component now supports binary body as an attachment.
- #1293 The components with an exchange pattern option now give back
a response to the caller before being routed as an
One way
exchange.
4.8.1
Released on: Friday 6 March 2020
Breaking
- #1141 The Excel to XML component
now generates
excelCol
elements instead ofexcelRow
elements when thetranspose
option is enabled.
Improvements
- #1282 We added an exchange pattern option to the Content Router component
- #1141 The Excel to XML component has a new option so that the header row of an Excel document can be used to name the XML elements.
Bugfixes
- #1223 + #1283 We fixed the manual validation of expressions in the Content Router component and the Set Headers component.
- #1277 We fixed a bug which caused some Groovy Scripts to fail after restarting the back-end.
4.8.0
Released on: Wednesday 27 february 2020
New features
- #1155 We addded new components to consume files from and upload files to Google Drive: the Inbound Google Drive component and the Outbound Google Drive component.
Improvements
- #354 We updated our Camel version to
2.23.4
. - #1168 The Split component now sets some headers on each splitted message which can be helpful. Information about these new headers has been added to the Split component documentation.
- We added an Exchange pattern option to the Split component.
- #1252 The XML JSON current component has a new option to remove the root object from the JSON output.
4.7.2
Released on: Monday February 3 2020
Improvements
- #853 We improved the
Inbound e-mail component with a new
Content
option that allows you to process both the body and attachments of an e-mail.
Bugfixes
- #1242 We fixed a bug in the Outbound Flow Link component that caused wrong behavior when used at the bottom of a Split component.
4.7.1
Released on: Thursday January 23 2020
Improvements
- #1154, #1174, #1188, #1202 #1214 #1230 Multiple improvements for the new XML JSON components:
- XML to JSON: add a new type hint
array
. - XML to JSON: XML attributes are prefixed with
@
in the resulting JSON. - XML to JSON: XML attributes other than
type
also show up when XML node hastype
attribute. - XML to JSON: fix bug that caused XML nodes with name "type" to not show up or weird JSON output.
- JSON to XML: The name of the root tag can now be customized.
- JSON to XML: JSON with a root array is now supported.
- JSON to XML: new option to change the name of the array elements in the resulting XML.
- Refactored the back-end code for improved performance.
- XML to JSON: add a new type hint
- #1053 We improved the processing of attachments for the
Inbound email component. When content
option
attachments
is selected it will also process the body when there are no attachments in an email. - #1206 The Recipient component now always shows the order of how messages are routed and it has a new option to determine the routing behavior.
Bugfixes
- #1148 FTP components with the FTPS protocol now support SSL Session reuse which is required by some FTPS servers since it also improves security.
- #1190 Give the Split component a fixed exchange pattern. This ensure that the component always has the same expected behavior. In some flows the components before a splitter could set a different exchange pattern which caused the splitter to changes its behavior.
4.7.0
Released on: Friday November 15 2019
New features
- #165, #789, #1058, #1083, #1106 We divided the Flow link component into a Inbound flow link component and a Outbound flow link component. We did this to make it easier to use and fix some issues with it. The original Flow link component is now deprecated.
- #973 We added an S-flag parameter to the Replace component that enables the dotall mode.
- #1176 We added an exchange pattern option to the Inbound HTTP component, so it would work better together with the new flow link components.
Improvements
- #343 We improved the memory settings for ActiveMQ which results in better overall stability.
Bugfixes
- #1080 We fixed the CRON input of the Scheduler component so that the selected day is also the day on which the scheduler will run. For example: you had to schedule a CRON job on Wednesday if you really want to run it on Tuesday.
4.6.1
Released on: Wednesday September 25 2019
Bugfixes
- #988 We fixed the bug that caused errors in the
Set Global Variable component when the
message body contained the dollar symbol (
$
). - #1145 Regression: the fix for slow saves in the flow designer was omitted by mistake in release 4.6.0 and is now added back.
4.6.0
Released on: Thursday September 19 2019
New features
- #1022 New Excel to XML component. It allows you to transform parts of Excel files into XML. Checkout the documentation to learn more.
- #173 New and improved JSON to XML and XML to JSON components. These should provide better transformations for XML and JSON and solves some issues. The old JSON to XML and XML to JSON components are deprecated and will be removed in a future release.
- #1023 Two new endpoints for sending/receiving HL7 messages:
Improvements
- #1057 We improved the tracer and fixed some issues along the way:
- The order of transaction messages is now correct. They follow the order in which the messages were sent between the components.
- It is faster. Heavy flows now won't be affected when they have tracing enabled.
- It doesn't interfere with flows anymore. In some situations the tracer could change the behaviour of a flow.
4.5.7
Released on: Wednesday September 18 2019
Bugfixes
In this release we fixed two bugs for the Inbound HTTP component:
- #1091 The validation for the endpoints is improved. It now ignores
differences in casing. For example:
test
will be the same asTEST
. When two flows would be installed with these endpoints, only one of them would get called. - #1103 The combination of an environment variable as
Endpoint
andMatch prefix?
set to true would cause an error when validating other Inbound HTTP components. This error would cause most of the Inbound HTTP components to become invalid in the other flows.
4.5.6
Released on: Wednesday September 12 2019
Bugfixes
- #1082 We fixed an exception caused by the Replace component that occured when it processed an exchange before it was sent to an HTTP component.
- #1123 We fixed a bug that occured after saving a flow. In some cases this could cause the user interface to completely freeze causing the page to become unresponsive.
4.5.5
Released on: Tuesday August 6 2019
Improvements
- #865 The validations of the Set Headers component and Content Router Component in the flow designer has been improved. Expressions with environment variable placeholders will be validated in the same way as expressions without environment variable placeholders.
- #865 The tooltip that shows up when hovering environment variable placeholders now shows the value of the environment variable for each environment. Before it only showed the value for the test environment.
- #1035 The tooltip that shows up when hovering environment variable placeholders now works better when there are multiple environment variable placeholders. It now shows the values for all the placeholders.
- #1047 We have made several improvements in the amount of threads Dovetail uses on the server.
Bugfixes
- #1002 We fixed the alert that appeared when leaving a flow that has unsaved changes. It showed the code instead of executing it.
- #1039 We fixed an issue where the connection test of the SQL component could fail when it shouldn’t because of special symbols in the username, host, password or database name.
- #1033 We fixed an issue with the EDIFACT to XML component where it could generate some errors while processing exchanges.
4.5.4
Released on: 13 June 2019
Bugfixes
- #1019 Due to the upgrade of Camel it handles Byte Order Marks differently. This caused issues in the FMUTA component resulting in missing output. This has been fixed now together with the radio button that didn't seem to work properly.
4.5.3
Released on: 7 June 2019
Improvements
- #1012 + #1013 Update some front-end dependencies to fix security vulnerabilities.
Bugfixes
- #303 We upgraded Camel again to version
2.22.4
to fix a bug related to the FTP component when SFTP is used.
4.5.2
Released on: 5 June 2019
Improvements
- #995 We improved the validation of the endpoint in the Inbound HTTP component
- #986 We improved some statistics of the health check:
- ActiveMQ check now also returns the status
FAILING
if things are really going wrong - The flow bundle report now also reports if there are stopped flow bundles
- The thread counts are checked better now and will return
TROUBLING
orFAILING
status when reaching certain tresholds
- ActiveMQ check now also returns the status
- #991 We improved the caching of the JavaScript files and CSS files in the browser.
- #299 We upgraded Camel to version
2.22.0
Bugfixes
- #286 + #298 We fixed some bugs and refactored some code in the SOAP component
- #300 We now also support the
BEGIN
SQL operation in the SQL Component so it can be properly used with theOracle 12c
database type - #801 We fixed a bug that caused the copying and pasting of a Recipient Component to not work properly. It would cause an error when trying to install the flow that contained the pasted recipient.
- #949 We fixed a bug that made it possible to create flow groups with duplicate names.
- #975 We fixed the password validation when activating a new user. Some passwords were marked as invalid while they were valid to use.
- #976 We fixed the bug that would cause a new split component to be replaced with a deprecated split component when a flow was imported.
4.5.1
Released on: 7 May 2019
Bugfixes
- #964 We fixed a bug for the SQL component
which made it impossible to connect to a SQL database of the type
SQL Server
. - #909 We fixed some logic of some components which should resolve the problem that some flows would not be restarted after a deployment or server restart.
- #971 We improved the
Override
File type in the Enrich component so it throws a useful exception when the body that comes out of the bottom route is empty.
Improvements
- #292 We added thread count and peak to the Karaf report of the health API.
4.5.0
Released on: 17 April 2019
New Features
- The NTLMv2 component now supports simple expressions to create dynamic URL's.
Improvements
- We improved/added the threadpool settings which should increase the stability of the Dovetail system.
- We split our queueing system per environment so asynchronous flows from test can't take down the queueing system of the production flows anymore.
4.4.1
Released on: 19 April 2019
Bugfixes
- #964 We fixed a bug in the SQL component
that made it not possible to connect with a database of type
SQL Server
.
4.4.0
Released on: 12 April 2019
Deprecations
Starting from this version there is a deprecated version of the Split component, because the new version also has the improved Aggregation strategy which can change default behavior.
New Features
- #166 It is now possible to see the logs and transactions of uninstalled flows in the flow manager.
Improvements
- #938 We added two options to the Inbound HTTP component which improve the usability.
- #826 We added the
completionCountTimeout
option to the Aggregate component so you can also set a timeout for thecompletionCount
option.
Bugfixes
- #918 We fixed the behavior of the new Enrich component when a FTP component is connected to the bottom.
4.3.3
Released on: 8 March 2019
New Features
- #806 The SQL component now supports
IBM DB2
andIBM Informix
databases.
Improvements
- #867 The Split component now also puts aggregated tags around a single aggregated message.
- #898 The FTP component now has passive mode enabled by default.
- #268 The Inbound HTTP component and HTTP component now have support for multiple open connections at a time.
- #847 We improved the ActiveMQ check in our health monitor.
- #891 We now allow more special characters in the endpoint of the Inbound HTTP component
Bugfixes
- #800 We removed the
recordSeperator
option from the CSV to XML component
4.3.2
Released on: 4 February 2019
Deprecations
- #797 Starting from this version we deprecated the
Enrich component and the
Aggregate component, because new versions are
available which have different behavior. The
new version of the Enrich component now
also puts
Enriched
XML tags around single message enriched bodies for XML. The new version of the Aggregate component now also putsAggregated
XML tags around single message XML aggregations.
Bugfixes
- #845 We fixed a bug in the Content Router which could lead to a lot of persistent data in the queueing system.
- #819 We fixed a bug which caused some components to accept multiple incoming connection lines. We don't support this yet, so we removed it to avoid confusion.
- #849 Since 4.3.1 the Throttling component dissapeared from the component library. It is now available again and we added some preventive measures to prevent this from happening again.
- #855 + #856 We fixed a bug in the Enrich component which caused it to not output any message when it had no connections on the right.
- #866 We fixed a bug in the tracing which could cause some exceptions during flow execution.
4.3.1
Released on: 9 January 2019
New Features
- #770 We added the possibility to add an authentication token as an HTTP header in the SOAP component, so WSDLs that need one can be accessed.
- #253 Add support for
${bodyAs(String)}
in the global variable components and the SQL component.
Improvements
- #818 We removed the deprecated split component. Deprecated split components in flows will be migrated to the current split component.
Bugfixes
- #837 We fixed a rare bug that could block the installation of a flow when it contained an empty environment variable.
- #812 Some flows could not be moved to other flow groups.
4.3.0
Released on: 12 December 2018
New Features
- #147 New! Revised Front-End Technology, we updated some technologies used for representing dovetail in the webbrowser which will result in better stability and more features in the future.
- #149 We added the functionality to validate components regarding their positional connection, which means we can now do more specific validations to help the user design their flows.
Improvements
- #168 Because our users had a difficult time figuring out which installed flows where using tracing, we added the value in the Flow Manager page.
- #197 We improved our login system by not bothering users to login every now and then, if you want to prevent any unwanted access you can just log off manually. With this we also got rid of our back-end token validations which often caused trouble.
- #761 Don't open the Flow Manager in a new tab when navigation from the version tab.
- #150 When adding a new rule in the content router component, the new rule will have the same expression type of the previous expression.
- #794 We improved the validation message of the Inbound HTTP component so it is more clear what is allowed and what not.
- #786 FlowLink components will be empty now when you import them via a flow import.
- #183 When a flow fails to load due to an internal server error the flow designer will not break anymore.
- #689 It is now possible to use the Scheduler component, which is set with a repeat count, in front of the following components:
- #246 We improved our health API, so we can retrieve more detailed statistics for our monitoring.
Bugfixes
- #144 Fixed an issue where the Two Factor Authentication QR displayed the wrong environment.
- #684 Fixed an issue where Dovetail would load in some icons from
http
instead ofhttps
causing some browsers to complain about unsecure scripts. - #696 Fixed an issue where underscores weren't allowed in the Script component.
- #712 Before today it was possible to mess up the aggregation by deleting some headers, this has now been solved.
- #762 Fixed an issue where the save button wouldn't turn active when changing an empty environment variable.
- #747 Fixed an issue in the mail component which caused some parts of a header to show up in the body.
- #183 Fixed an issue where flows with incorrect data would break the flow designer when they were opened.
- #795 Fixed an issue in the enrich component which could trigger the flow to keep hanging in a stopping state on uninstall.
- #777 Fixed an issue in the replace component which caused replacing of linefeeds to not be possible anymore.
- 787 The FlowLink component will now properly set the target flow when you open the properties view for the first time.
- 684 Fixed a bug which caused some browsers to show warnings on the login page about unsecure scripts.
4.2.8
Released on: 13 March 2019
Bugfix
- #268 The Inbound HTTP component and HTTP component now have support for multiple open connections at a time.
4.2.7
Released on: 31 January 2019
Bugfixes
- #866 We fixed a bug in the tracing which could cause some exceptions during flow execution.
4.2.6
Released on: 13 December 2018
Bugfixes
- #777 Fixed an issue in the replace component which caused replacing of linefeeds to not be possible anymore.
4.2.5
Released on: 20 November 2018
Improvements
- #234 We added the ListOrders operation in the Amazon Component with which users can retrieve order without the need of scheduling reports.
- #235 We added the ListOrderItems operation in the Amazon Component with which users can retrieve order items from a specific Amazon Order.
- #236 We migrated the
Region
property in the Amazon Component towards aMarketplace
property which should be more specific for Amazon.
Bugfixes
- #237 Fixed an issue where the Simple Replace Component could stop working under a severe load of items.
4.2.4
Released on: 8 November 2018
Improvements
- #713 Fixed an issue where the Soap Component
would get stuck waiting for a reply in a
synchronous
flow when the Soap Endpoint would not return any data.
Bugfixes
- #218 Fixed an issue where the Soap Component
would fail to generate the correct request body for message parts with
type
attributes. - #220 Fixed an issue where the SQL Component
would return a different result for the
Test Connection
action than calling the flow in real time.
4.2.3
Released on: 7 November 2018
Bugfixes
- #215 Fixed an issue where the Replace component
would always return an empty body in
synchronous
flows.
4.2.2
Released on: 6 November 2018
New Features
- #151 New! Simple Replace component, this components finds simple expressions in a message body and interpolates them. For more information read the documentation page.
- #175 New! FormToXml Component, this component allows transformations from the URL Form Encoded body to XML. For more information read the documentation page.
Improvements
- #150 When using the Content Router component the new rules will automatically mirror your previous settings.
- #181 Support replacing character for line breaks, and tabs.
- #187 When using the override strategy you won't lose any headers that you had before the enrich started.
- #683 We improved the NTLMv2 Component so it can now load responses bigger than 2MB.
- #709 When using a MySQL Database with a server timezone that represents more
than one timezone Dovetail will automatically default to
UTC
for you. - #732 It is now possible to have environment variables with blank values.
Bugfixes
- #204 Fixed an issue with the XML to Edifact component where transformations would fail on a certain occasion.
- #686 Fixed an issue with using a flow component in the error route causing the validation message to not have a title.
- #711 Fixed an issue where the preview function didn't work in the Get & Set Global Variables Components.
- #719 Fixed an issue with the environment variables table which would incorrectly add an extra row.
- #722 Fixed an issue where you couldn't switch tenants in the instance manager view.
- #724 Fixed an issue where the settings table in the components would be bigger than the model.
- #726 Fixed an issue where you couldn't delete your account, simply because we didn't want to let go.
- #734 Fixed an issue where the encrypted key icon wouldn't show up when using custom environments.
4.2.1
Released on: 25 October 2018
Bugfixes
- #196 We fixed an urgent issue where queues were shared across the production an test environment causing flows to behave inappropriately.
4.2.0
Released on: 18 October 2018
New Features
- #643 New! With this version we support multiple environments, rather then
just
Production
&Test
. This can be arranged in a few clicks with the Dovetail team. - #886 New! Static environment variables, these variables are automatically
filled for every new, and existing flow, prefixed with
self.<variable>
. See more. - #972 New! NTLMv2 Component, this component allows users to call webservices with NTLMv2 authentication required. For more information read the documentation page.
- #991 New! Load notifications on flow basis, that's right when a flow experiences
high load it will be showed in the flow manager. The thresh holds for
critical
andwarning
notifications can be adjusted on the fly by the Dovetail support if desired. - #1013 New! PDF component, this component allows users to generate pdf files based on a template. For more information read the documentation page.
- #106 & #871 New! Throttler component, this component allows users to throttle batches of incoming messages. For more information read the documentation page.
Improvements
- #273 Whenever installing a flow that would fail to install in the back-end, the user would receive no notification whatsoever. We have now enabled notifications from the back-end which push possible errors during installation to the user in the form of a notification.
- #542 When using the Recipient component, it's now clear in which order the endpoints will be executed when the flow is put synchronous.
- #667 When using the Remove Headers component
Dovetail wil automatically exclude the
breadcrumbId
header as it is used to track transactions in the tracing log. You can still remove this by explicitly name it in the exclude pattern. - #974 When having a flow that produces alot of tracing, the tracing flow will be stopped when the limit of a hundred transactions is reached. This relieves the tracing / indexing mechanism from some unecessary load.
- #983 You can now have flows with the same name in different groups!
- #1007 We added the possibility for migrations on already installed flows, this gives us the opportunity to make big improvements without having to re-install ever flow by hand when the release goes live.
- #1015 We took the queue'ing mechanism outside of our back-end which will improve reliability, plus on failure we don't have to restart our back-end / flows, only the queue'ing mechanism.
- #1032 & #1033 When linking to a specific flow with the Flow Link component, it now lists the flow group behind it, as of #983 flows can be named the same cross-groups.
- #150 We added support for simple expressions in the rules of a Content Router component.
Bugfixes
- #171 Fixed an issue where the user export couldn't be downloaded.
- #666 Fixed an issue where the on hover function wouldn't show the environment variable's value in the FLV, Content-Router and Set Headers component.
- #687 Fixed an issue where the
Get Shipments
method of the Bol component wouldn't accept any parameters. - #993 Fixed an issue where the delete button would be still active, when the flow was actually installed.
- #998 Fixed an issue where the
test connection
button in the SQL Component would return a different value then when used installed. - #1004 Fixed an issue where on succesful login, your failed attempts count wasn't reset, causing you to reach your max failed attempts too soon.
- #1018 Fixed an issue where the flow versions / validations sidebar glitched when switching between flow and settings tab.
- #1019 Due to a recent change in table styling for dynamic environments, the tables properties views were not shown correctly, this has been fixed.
- #1030 We fixed a bug that caused the environment switcher to show the wrong value when looking at the flow manager.
4.1.5
Released on: 30 December 2018
Bugfixes
- #258 We fixed an issue with the Bol component
where the
weekYear
would be sent to the bol.com API instead of the currentYear
attribute causing trouble in the last and first week of a new year.
4.1.4
Released on: 23 October 2018
Bugfixes
- #192 We fixed an issue where header variables, like
${header.x}
, wouldn't get interpolated in the Bol component.
4.1.3
Released on: 27 September 2018
Improvements
- We fixed an issue which caused some bundles, related to the EDIFACT and EDI components, to not be properly started after an environment restart.
4.1.2
Released on: 13 September 2018
Improvements
- #1020: We added support to dynamically override properties in the SoapComponent by providing a specific header. You can read more in the updated documentation of the SOAP Component.
4.1.1
Released on: 12 September 2018
New Features
- #944: Messages that originated from the main flow or tracing are now labeled appropriately in the flow logging
- #547: Environment variables are now stored encrypted in the database.
- #865: Now it is also possible to store global variables encrypted in the database.
Improvements
- #951: Switching between flow and flow component mode in the designer now only reloads the necessary parts of the UI.
- #955: A new icon has been added to flow components in the component library that redirects you to the designer of that flow component version.
- #973: We updated all the component links to Dovetail Academy to include the application version so you'll always see the correct documentation.
- #914: We improved the unlocking of flows, so flows won't be locked when nobody is actually in it.
- #965: Add multiple region support to the Amazon component.
- #935: Add information about the Amazon XSD's in the Amazon Feed documentation
- #949: Add validation to the password field in the login form.
- #784: Flow and component notes are now included in a flow export and will be included on a flow import.
- #865: Global variables that are created in the settings tab no longer get
a default value of
Unassigned
. Instead they are empty on creation.
Bugfixes
- #977: We fixed a bug in the Inbound email component
that prevented the use of an environment variable in the
port
field. - #919: We fixed a bug that prevented the use of special characters like
&
in the version remark of the install flow dialog. - #957: We improved the switching of tenants so everything is reloaded properly in the flow designer.
- #947: We fixed a bug that prevented a user to sign in when their password contained special characters.
- #943: Flow logging is now properly showed for all log levels.
4.1.0
Released on: 30 July 2018
New Features
- #605: We added a big feature called Flow Components. With Flow Components you can save a flow as a component that can be used in other flows. For a full explanation you can read the guide.
- #922: We added two factor authentication. You can enable it via your account details.
Improvements
- #946: We made it possible to use the Remove variable component as the last component in the flow.
- #903: We reduced the body size of tracing from 1MB to 250KB.
- #934: We added XPath 2 support to the Set Headers Component.
- #930: Back-end time-zones can be specified per server.
- #907: We added IFTMBF D08A Edifact Standard to the Edifact Standards to XML component.
- #832: We added more information to the validation messages of the log component.
- #875: We upgraded Karaf to the 4.2.0 production release.
Bugfixes
- #937: We fixed a bug that caused the Remove headers component to not be visible in the component library.
- #936: Fixed an isue where some components that used Camel Dataformats could not be used in the error route.
- #929: Switching tenants could sometimes break the flow designer.
- #942: We fixed an issue which prevented to create a user via the tenant manager.
4.0.12
Released on: 3 September 2018
Bugfixes
- #1025: Fixed an issue in the Http component where chaining multiple dynamic http components would result in the first url being overwritten in every component.
4.0.11
Released on: 26 July 2018
Improvements
- #989: Removed the
dynamicUrl
field in the Http component allowing theURL
field to contain static and dynamic URLs.
Bugfixes
- #989: Fixed an issue in the Http component where URL parameters would not be sent to the endpoint correclty.
4.0.10
Released on: 26 July 2018
Improvements
- #987: Allow custom certificates to be imported for the Soap componentwithout being removed on reboot.
4.0.9
Released on: 4 July 2018
Bugfixes
- #968: Fixed an issue where the Enrich component would wrongly normalize the incoming XML, causing it to fail its own validation.
4.0.8
Released on: 28 June 2018
Bugfixes
- #928: Fixed an issue where the Scheduler component caused a stop of transactions.
- #967: Fixed an issue where the FlowLink buttons in the Tracing wouldn't redirect to the right environment.
4.0.7
Released on: 21 June 2018
Improvements
- #964: Allow empty username, password in the smtp settings when the smtp server is configured to authenticate on ip-basis.
4.0.6
Released on: 8 June 2018
Bugfixes
- #931: Fixed an issue with the Soap component that caused a wrong default namespace to be assumed when there were no namespaces defined in the context.
4.0.5
Released on: 8 June 2018
Bugfixes
- #962: Fixed an issue that caused the back-end to crash when flows were de-installed when it had in-flight messages.
4.0.4
Released on: 30 May 2018
New Features
- #896 + #906: When HTTP or Email endpoints use custom SSL Certificates, we can now import these into our back-end without having to restart it.
- #898: New! Oracle 12c Database connection support, for the SQL component. It means literally what it says, you can now connect to your Oracle database from within Dovetail's SQL component.
Improvements
- #895: We saw that the tracing storages
on some servers were growing a lot faster than we expected, therefore we changed the
tracing values so you can choose to keep
them less than one day. The new values are:
1 Hour
,4 Hours
,12 Hours
,1 Day
and1 Week
. - #897: When creating a new Tenant it was always a bit difficult to create the first flow, it needed some refreshes before it could be found. This issue has now been resolved, and as an improvement Dovetail asks to create a first flow if none are found.
Bugfixes
- #847: Fixed an issue where it was unable to create new users due to the email textbox being disabled.
4.0.3
Released on: 7 May 2018
New Features
- GDPR: Added the
Edit User Details
link to your profile view where you can edit your account details, delete your account (and all associated data) and request an export of all your data that Dovetail currently has on you. - GDPR: Added restrictions on the session cookie Dovetail uses to remember who logged in. These restrictions make sure only your Dovetail instance can access these.
- #812: When transforming XML to JSON we often got the question why everything
is by default a string, and
null
values were automatically an empty array ([]
). We added an option so you can specify in the source XML the type of value it contains so the component knows this when it transforms it into JSON. See the documentation for more information. - #842: We added a health check API to Dovetail so we can monitor it more specific and more accurate.
- #852: We added a favicon to Dovetail.
- #861: Looking at the new Split component a
few questions were raised on the
TimeoutExceptions
, we decided to make the timeout for asynchronous flow configurable in the flow settings tab, and add an option to split parallel. For the parallel option read the documentation for more information.
Improvements
- #887: Added support for Office 365 SMTP Mailbox in the Tenant configuration.
- #891: Whenever an exception occurred in the bottom route of the Enrich component, it was not logged into the Flow logs, and no failed exchanges were displayed. Backwards compatibility-wise we decided to just log it in the flow logs, instead of letting the exchange go to the error route as it could break current installed flows.
Bugfixes
- #800: Fixed an issue where chaining wiretaps directly after each other would cause the flow to misbehave.
4.0.2
Released on: 20 April 2018
Improvements
- #820: When using the CSVToXML component we added the functionality of removing any XML forbidden characters in the CSV Headers.
- #876: When specifying limits on production installs per tenant, you can now use
-1
to set it to infinite.
Bugfixes
- #873: Fixed an issue where the Recipient component would sometimes keep ghost connections in the background, causing the flow to misbehave.
- #877: Fixed an issue where the Samba component would not work due to the dependency not being available for the Dovetail 4.0.1 version.
4.0.1
Released on: 17 April 2018
Warning
- With this version, all flows need to be reinstalled manually. This is unavoidable because of the fact that we "reinvented" the way we gather statistics about flows (not related to data, just numbers).
New Features
- #269: We added the functionality to copy and paste components with their config preserved. This can be between flows, but unfortunately not between tenants as that would be some sort of security risk. For more information read the documentation page.
- #591: New! Amazon Component, this component allows users to integrate with the Amazon Marketplace. For more information read the documentation page.
- #608: Superadmins can now specify the number of flows that a tenant is allowed
to run in production. This can be configured in the
Instance Manager
.
Improvements
- #329: When scrolling through your versions in your Flow Designer it is now possible to click on the environment of an installed version to go to its flow manager details page.
- #677: When connecting flows through the
FlowLink
component you often got duplicated tracing in both flows. This issue has been resolved and you should only see the components of the current flow. - #689: When tracing a flow that is connected to a
FlowLink
component, tracing will add a link to the calling and receivingFlowLink
so you can easily navigate through the tracing. - #741: We added the functionality to override properties in the Bol.com component with headers. This allows users to create dynamic values and pass them to Bol.com, read the documentation (example) for more information.
- #755: When creating a new flow, the flow group that you were currently in will now be selected by default in the popup view.
- #775: We made several improvements in the usage of the Content-Router, which should now be more easy to use.
- #778, #799, #845: With 4.0.0 introducing the validation message tab, we were inspired with a lot of ideas and opportunities which we all tried to implement in this version. We added information messages and warning messages to help you in designing better flows.
- #803: We added the Tenant's
creation date
andlast updated
to the instance manager view. - #854: We now support more HTTP method calls in the HTTP component! We added:
HEAD
,PUT
,DELETE
andPATCH
.
Bugfixes
- #740: Fixed an issue where after registration, the redirect to the Flow Manager would not happen because of the activation token still being in the URL.
4.0.0
Released on: 29 March 2018
Warning
- With this version, all flows need to be reinstalled manually. This is unavoidable because of the fact that we "reinvented" our whole back-end system and upgraded several systems for better reliability and performance!
New Features
- #181:
FTPS
is now available as FTP Protocol in the FTP Component. - #462: New! Validations tab. In addition to our validations and pre-install checks in the Flow Designer, we now added a validations tab that shows you the exact validation message per component. Making it easier and faster to debug your flow. Check the documentation for more information.
- #544: Dovetail now uses the new Apache Karaf 4.2.0.M2 release.
- #682: Dovetail now uses the new Apache Camel 2.21.1 release.
- #711, #813: New! Dovetail Tracer. Previous to this version we used an Apache Camel tracer to trace our message's through the flow. Unfortunately, we discovered that this Tracer was unreliable and deprecated in the new Apache Camel versions. The new Dovetail Tracer is 100% asynchronous and will never interfere with your main route. Important to note is that the Dovetail Tracer will always show the message going into the selected component, whereas before it showed the message leaving the selected component.
Improvements
- #610: XPath 2 function are now fully supported again in all XPath expressions.
- #696: Improved the experience when clicking flow versions , by not automatically scrolling back up the versions but staying on the version you clicked.
- #766: This version will have revised component icons.
- #767, #768: Improved security of our routing between our local proxy and back-ends, now all using SSL.
- #777: Expression validations are now run with the same validator which results in better and more consistent validation results.
- #795, #786: We renamed the IftminToXml component to EdifactStandards component for a better user experience, and also added more standard Edifact transformations. This component still only works one-way, from a standard Edifact to XML.
- #797: For security reasons we decided to not show potential stack traces in the response of the Inbound Email Component. We do however show a small message to give a clue about what might be wrong. The full stack trace remains available in the logs tab in the Flow Manager.
- #787, #806: Due to an upgrade of the Java Mail library in Apache Camel we had to improve/update some configuration files to make the Inbound Email Component work again.
- #810: We now removed the deprecated Soap Component in favor of our new Soap Component.
- #813: We have made huge improvements to the Soap Component generating reliable automated tests which result in improved performances and wider support of WSDL variations.
Bugfixes
- #286: Fixed an issue where environment variables would not show/validate correctly in the
Error Route
. - #749: Fixed an issue where the operation in the Soap Component would not be sorted alphabetically.
- #773: Fixed multiple issues regarding importing and exporting flows.
- #785: Fixed an issue where flows containing a "&" in their names could not be installed.
- #833, #843: Fixed an issue where importing a flow which contained a deprecated component didn't get properly deprecated.