​
What’s new? 🆕

​
Rendering

Form Elements improvements:

  • Default Value Handling: Defaults are applied only when no existing value is found, and set upon first display (with specific exceptions).
  • Data Consistency: Form elements now save data in standardized formats based on type for improved reliability.
  • Smart Defaults: Clear fallback behaviors for elements like switches, sliders, and checkboxes when no value is present.
  • Synchronized Inputs: Linked form elements (e.g., input + slider) stay in sync with automatic value adjustments within set limits.
  • Dynamic Dependencies: Form elements can dynamically adjust based on related components’ values for greater flexibility.

​
Merge conflicts

  • Improvement: merged version is now selected after a successful merge in versioning modal.

​
Bug fixes 🐞

​
Merge conflicts

  • Fixed an issue that caused conflicts involving notification and document templates to fail.
  • Fixed an issue where merges failed when a deleted configuration parameter was updated on a branch.
  • Fixed an issue that resulted in duplicate substitution tag keys appearing in the merged version.
  • Fixed an issue where merges failed due to the same dependency being added to both the source and target branches.
  • Fixed issues related to workflow conflicts.

​
Rendering

  • Fixed an issue where documents from the media library were not loading correctly when added as a file preview in a user task.

​
Integration Designer

  • Fixed issue causing a 400 error when adding an enum mapper to the body tab due to incorrect data validation.
  • Fixed issue where the last attribute in the objects table was not visible at higher zoom levels due to UI rendering constraints.

​
Known issues 😢

We’re aware of a few quirks during merge conflicts and are working to fix them. Here’s a quick rundown:

​
Additional information

For deployment guidelines and further details, refer to:

Deployment guidelines v4.6.1

Migrating from v4.6.0:

Migrating from previous versions