What’s the issue?
In specific circumstances, using the Update Activities button can affect data in fields that use form-to-form pre-population. This occurs when a form is updated to a newer version while a work step is still in progress. To be clear, this issue:
Only affects fields that are configured to pre-populate from previous forms.
Only occurs when the Update Activities button is used.
📌Note: In most cases, customers have this feature turned off by default and only enable it when needed, which is what we recommend.
What’s happening?
When the button is used, Mosaic re-applies all pre-population logic across the form. This can result in:
Data that has been updated in the current workstep is being overwritten with older data from the source form.
Fields are being cleared if no source data exists.
🤓Tip: This behaviour has been present since early versions of Mosaic, but only occurs under the specific conditions described above.
What are we doing?
We are reviewing this functionality and the various use cases around it to decide whether changes need to be made and what these will be.
What should you do in the meantime?
Consider whether you need the Update Activities button. If not, set the system property enableUpdateActivitiesButton to false.
If you need to use the Update Activities button, ensure users always output the form to PDF before updating, so they have a reference copy.
Make a note of any relevant fields that are not set to print (these will not show on the PDF)
Review the form against the PDF carefully after updating, with particular attention to any pre-populated fields.
📌Note: If you don't use this feature, no action is required.