Release r202622

What's new

This release contains the following new features:

• Compare versions of a record
• Readable and writable Xurrent properties

Compare versions of a record

The change history shows what changed in a single change set. It is now also possible to compare a record against any earlier version of itself.

Select Compare versions from the actions menu of an item to open the new comparison view.

The list on the left holds every recorded version of the record, identified by the moment it was recorded, the user who made the change and the fields that changed. The oldest version is labeled Before creation for records that the automator has tracked since they were created, and Before first recorded change for records that already existed when change tracking was introduced.

The two versions being compared are marked From and To, both in the list and above the comparison. Select one of them to make it active, and then either pick another version from the list, or use the arrow buttons to step to the previous or the next version. This way you can walk through the history of a record without leaving the view.

Sensitive values, such as passwords and tokens, are never revealed. The comparison does show whether such a value changed between the two versions.

Readable and writable Xurrent properties

In the Xurrent REST API, the properties that can be read from a fetched record are not the same as the properties that can be used to create or update one. Reading a request returns its notes, for example, while a note is added by writing note, a property that a read never returns. Other properties, such as reopen_count and resolution_target_at, can only be read.

The code editor now knows the difference. The data passed to create and update was previously untyped, so there was no completion for it at all. Code completion now offers the properties that the record type accepts on a write.

The types of the records returned by fetch, fetchAll and fetchFilter were corrected the other way around. They no longer list write-only properties, so completion on a fetched record offers only the properties that a read returns.

The Xurrent fields reference is generated from the same model and has been updated along with it. The properties of a record type are now listed under a Reading heading, for the properties that are returned when a record is read, and a Writing heading, for the properties that can be specified when creating or updating a record.

Other changes

This release contains the following smaller changes:

• Uploading attachments through the attachments and internal_attachments attributes is deprecated. These attributes write to the main rich text field of a record type, which is implicit: attachments ends up in note_attachments on a request, but in remarks_attachments on an organization. Use the explicit attribute of the rich text field itself instead, in most cases note_attachments and internal_note_attachments. For more information, see Attachments.
• Fix: webhook verification using OpenID Connect discovery, introduced in release r202620, did not work on the Xurrent demo environment. Webhooks sent from that environment carry a different issuer, which is now accepted as well.

Timeline

The expected deployment dates for this release are:

Environment	Date
Demo	Friday, September 4
Production	Tuesday, September 8

The deployment to the Production environment will be conducted outside of office hours (Central European Time Zone), usually between 8 and 10pm.