23.4

Crossfire

• Fixed empty elements not being present after conversion to XML, which occasionally caused the conversion to fail.

• Added a tooltip listing variable names reserved by the Crossfire system.

• Added functionality to edit the XmlSsStructure for message standards in a new advanced section.

• A new 'Built In' crossfire function called GlobalXPathSum. This will calculate the XPath sum from the root node of the message.

• Added a new SP for inserting message standards that include the interchange type.

• Added a new built-in crossfire function called "GlobalXPathSum". This is identical to XPathSum except it will always evaluate the XPath with respect to the message root node.

• Partner schedule threads are now displayed in order.

• Added AWS Transfer Family support to FTP/FTPS/SFTP transports.

• Changed the functionality for system test matching. Destination process system tests now have a name lookup and are required to match one from the sourcing process. They no longer match the order they are displayed.

• Updated the holiday checker to support looking forward to any number of business days.

• Removed reference to vulnerable JQuery version and fixed loading race conditions where pages would load with no content.

• Performance improvements to the bulk processing page.

• Fixed an occasional 'parameter error' when copying complex elements.

• Fixed accidental duplication of data element function lists, which often caused errors.

• Fixed UI bug which would open two windows at once when using the ID quick look-up.

• Fixed UI bug where the default sort on Message Notification is not by date, and also fixed the sorting arrow bug which is not shown on the date header.

• Fixed UI bug where the character limit in ReplaceChars in Message Standard is too small, and does not match the one in the database.

• Fixed an issue with the message lifecycle status when the messaging message fails.

• Fix an issue where certain Message Standard SG child nodes would disappear from the UI when an adjacent SG was added or removed.

• Fixed the bug where the destination process doesn't show KeepForDays, and the source one does not propagate to the destination.

• Fixed bug where the previous person forgot to add migrator for "ADMIN.MessageStandard_Copy.sql".

• Fixed bug when you opened up 2 or more schedule tabs, if you expand the schedule group on one of the tabs, it will show on the other tab instead.

• Fixed an issue where outgoing MSG.MessageArchives were displaying  'Received' as their status in the message lifecycle.

• Resolved some issues with system test matching, added support for multiple outbound and test outbound interchanges, and added the functionality to match results on test name. A full overview of changes can be found at the end of these release notes.

• Resolved an issue where it would allow the deletion of mapped data elements.

• Resolved an issue where it would only partially check if segment group children are mapped before deleting.

• Resolved a message lifecycle display issue when there are multiple outbound processes.

• Resolved a visual issue where the status of a failed message would be stuck in sending when viewing the lifecycle.

• Resolved a bug where message standard nodes would sometimes disappear when adding new segment groups to the tree.

• Resolved performance issues on the bulk processing tab. 

• Resolved a date range filter issue on the bulk processing tab.

• Resolved some issues with the process import.

• Increased Web Service timeout to 5 minutes, from 1 minute.

Messaging

• Multiple purposes can now be selected for certificates.

• Resolved an issue regarding the truncation of filename search filters.

• Message statuses are now updated when manually changing their number of failures.

• Updates to transports no longer overwrite the last modification time on their schedules.

• Removed the from/to column from the message lifecycle tab, to better hide private information. 

• Added a feature that logs the user who starts and stops the scheduler from the portal.

• Added a feature that allows the user to confirm resending outgoing archived messages by showing a popup.

• Fixed spelling mistakes which showed KB when the correct size was in bytes.

• Fixed bug which unnecessarily saved the last modified (date and user) when there were no changes.

• Fixed an issue where outgoing MSG.MessageArchives were displaying  'Received' as their status in the message lifecycle.

• Added a feature that checks for near-expiring certificates.

• Added functionality to the Incoming Web API transport to pick up 0-byte files, and an optional delay to be compared against the last modified time.

• Resolved an issue when creating transports with an existing name.

• Resolved a race condition that could occur when messages get a new lifecycle ID. It would visually cause the lifecycle of multiple messages to be merged into one.

• Added increased logging to transports when inserting message attachments.

• Added functionality to export transport routes and destination transports when exporting.

• Added functionality for file monitoring (both notification and deletion).

• Added caching to multiple points in the engine to improve performance. 

• Added functionality to fully configure transport type fields of type ComboBox from the UI.

• Added additional error logging to transports. When a transport type dependancy is missing, the error generated did not get inserted against a transport but now it will. 

• Removed reference to vulnerable JQuery version and fixed loading race conditions where pages would load with no content.

• Resolved some issues with the DeliveryTypeDetail functionality that could cause objects to be duplicated in the database.

• Added Default Inbound Queue Processing. Resolved issues with picking up inbound messages that would previously get stuck when the engine is turned off. Getting the inbound queue now pulls existing messages from the db as well as getting new ones.

• Added Encrypted tickbox to transports to add encryption for password fields as opposed to just hiding the password.

• Added a change where the TextBody of a MSG.Message is copied into the EDI.Interchange Body if the MSG.Message HTML Body is empty, when processing incoming messages.