Release date: 5 September, 2024
The ShareLogic Unifi 4.3 release includes a number of important updates to help improve the Unifi experience and fix some known issues.
Fixed the trigger business rule template code so “undefined is not a function” errors are no longer generated.
Please check your Unifi trigger business rules to ensure that the logExecute function does not have superfluous parentheses () at the end. These can be easily accessed from the navigator > ShareLogic Unifi > Administration > Trigger Rules.
Several domain related updated including inbound receipts now use the correct domain from the transaction instead of the user.
Dataset cleanup will now remove old inbound attachments from the Dataset whenever the related Bonded Attachments are cleaned.
Snapshots are now controlled by a new system property “Enable Snapshot” which is disabled by default. The property must be enabled before user testing for automated integration tests to be generated from the bonds.
The debugging property “Core Debug Mode” is now deprecated. Instead, full logging is enabled with the “Trace Mode” property.
Fixed inbound JSON datasets.
Two previously deprecated system properties have been re-purposed in this release. If you have a very old installation, please check that they have been updated and revert to the latest version if necessary. x_snd_eb.snapshot.enable /sys_properties.do?sys_id=a001502e1bd991106eefea4cbc4bcb8a x_snd_eb.designer.auto_diagnostic /sys_properties.do?sys_id=9901502e1bd991106eefea4cbc4bcbd6
The 'Core Debug Mode' system property has been deprecated. Enabling Trace Mode is the equivalent of setting 'Core Debug Mode' to "Trace".
New fields on Datasets can now be configured for Coalesce during creation.
Improved the integration dashboard diagnostic that checks and validates versions of Unifi, hotfix, and global utility.
Dataset clean-up now also removes attachments used to send and receive Dataset data.
A system property has been added to disable integration diagnostics being run automatically when viewing an integration dashboard in Designer.
The Script Include containing integration diagnostics can now be modified.
Updated the Bond cleanup logic to prevent errors generated by one cleanup from stopping the entire cleanup process.
Integration diagnostic checks that the system property glide.businessrule.async_condition_check
is set to false.
Limited the number of duplicate bonds being checked during diagnostic to 20. A custom limit can be defined with the system property x_snd_eb.diagnostic.duplicate_bond_limit
.
Introduced a new system property to control snapshots. Snapshots are now disabled by default. This property must be enabled before testing to allow Integration Tests to be generated.
Added Process message and Send message columns to the Dataset list view in Designer for easy navigation.
Diagnostic now checks for the use of current in message scripts
Any open submenus are now automatically hidden when collapsing the sidebar in Designer.
Fixing an integration diagnostic issue from the integration dashboard will now automatically update the counters.
Support for inbound JSON processing has been addressed. Please make sure to update to the latest Global Utility for this (including versions 4.0, 4.1, and 4.2).
Improved inbound REST API processing to help identify catastrophic internal errors caused by external scripts and cross scope access issues for scoped applications dependent on Unifi.
All references to gr in the standard Unifi field maps have been removed.
Fixed payload formatter UI Action script so XML parse errors are simply ignored.
Sets the requests domain to that of the transaction when processing a receipt.
Test result chart colours now correctly match the labels.
Updates the HTTP Request domain to be the same as the transaction when processing the inbound receipt.
Removed extra parentheses from automatically generated trigger rules.
The domain of a datastore is always the same as that of the record it is attached to.
Fixed the Active/Inactive field filter on the fields list shown in a message. Selecting Active will show only active fields belonging to the message while selecting Inactive will show both inactive fields and integration-level fields which are not yet included on the message.
Fixed $stage generation in import set transform maps to use only u_ field names.