Breaking Changes
As part of the fix to prevent the item dependency chain from being reset when default values and filtering have been configured we have introduced breaking changes to the way in which the dependency change is validated. We now ensure that if a field is used as a key then the value will now be imported and if the field has not been changed dependent fields will not be prefilled. Previous behaviour is no longer supported.
Plan
No changes
Manage
No changes
Create
No changes
Enrich
No changes
Approve
No changes
Distribute
No changes
Measure
No changes
Adapt
Field Overview Health - To understand the breaking changes and where configuration may no longer be supported we have introduced validation tools to evaluate "Prefill Automatically" and "Default values" configuration within Site Configuration > Health > Field Overview.
Bug Fixes
A fix to ensure that add new item button displayed on a dashboard respects module configuration.
A fix to prevent when end-users have configured a calendar widget without filters resulting in 200K+ items being loading and overloading the system. As part of this fix, we have introduced a hard limit to max load 1000 items onto each calendar widget to avoid the system being overloaded in case of incorrect widget configuration.
A fix to prevent the item dependency chain from being reset when default values and filtering have been configured. We now ensure that if a field is used as a key then the value will now be imported and if the field has not been changed dependent fields will not be prefilled. Previous behavior for default values and filtering has been adjusted and may no longer be supported.
A fix to Proofing Insights to support scrolling when the number of commenters exceeds the height of the screen.
A fix to ensure that a guest user can perform status change when the module contains group access restrictions
A fix to spreadsheet view to ensure that dependent fields are updated dependent on changes to parent fields
A fix to ensure that the item in the inline module can be created successfully when it contains a dependent field referencing a calculation field in the parent module