All release notes
share
4 min read

New release for Preferences - New Pref → DM workflow + Unlock Forms

The following has been released to the Test environments on April 9th and will reach production next week. (Except for the Preferences to Data Manager feature, which will be released to production at a later date, in coordination with customers, in order to reduce operational disruptions)

New features - Preferences to Data Manager

For new Scheduling Forms, all submissions will now end up in Data Manager. This means that there are some additional mapping that needs to be done in the Preferences Form Designer whenever a Form is created. For each element in the Form, you need to decide how those values should be used on the Activities.

Image #1

For more information on how this mapping works, please refer to this Academy article

For more information on how Data Manager works, please refer to this Academy article

If you do not have Data Manager enabled on your organisation, please contact support@timeedit.com and they will be able to help you out. Also, any user who needs access to Data Manager will also need to have this enabled for them.

If you are interested in a walkthrough of this new workflow, please join the Webinar on April 15th, or view a recording of the previous webinar

General Improvements

It is now possible to Unlock a Form, as long as it has no active Submissions. This means that all submissions need to be invalidated before the Form can be unlocked. This feature is very useful when testing forms that were generated from imported Activities in Data Manager.

Image #2

Bug fixes

  • Resolved an issue where sometimes the Max class size value would not auto calculate for imported Activities in the submission, even though the Auto calculation was turned on.
  • Resolved an issue where sometimes the Name of a recipient would not be correct after recipient import. Names are updated by the most recent import.
  • Resolved an issue where it was sometimes possible to select Dates for an Activity that was on a holiday, even if “Don't allow bookings on holidays” was turned on