Changes in Execute 21.1.222

Most dates in Execute are actually Date + Time and those come with automatic timezone conversions. Sometimes, however, you just want a plain old date that will always show the same thing regardless of what timezone you are in. For that, we’ve added a new Unzoned Date/Time setting to Date Fields in the Field Configuration screen.

When a date field is set to Unzoned, users will never see a time component for that field, and the value will never be subject to automatic timezone conversion.

For example. In the screenshot below, Date 1 is a normal date field, and Date 2 is a new unzoned date field.

A new setting (inactivateMissingRecords - off by default) was added to synchronizations to automatically inactivate records that are no longer found in the source dataset.

If you would like to enable this in an existing sync, you can add the following to the IDocumentSynchronizer component.

<inactivateMissingRecords>true</inactivateMissingRecords>

Note: Be careful when using this feature as it can/will quickly inactivate records in Execute that are no longer found in the source system. If the source data is a table (populated by a scheduled job such as the replicator) make sure that the table is filled before letting this sync run! As always, it is strongly advised to run this in TEST before doing this in PROD.

See plugins_available\integration\synchronization\synchronize_document_data.config.sample for more documentation.

To improve performance when viewing Change Tracking for documents with a LOOONG history of changes, we have modified the default behaviour to only show/load detailed history for 6o days.

If you’d like to see the full history, there is a handy “Load History” button which will load everything, just as before.

We’ve done our best to make sure it’s clear when you are viewing a partial history (or searching partial history) to avoid any confusion.

Here is how it all looks.