EDELOG 6.28 | EDELOG Docs

New Features

Data columns can now contain a collection of nested records ("Record Collection"). Records of a collection can be created from templates and are edited directly within the parent record.
A new JSON column type allows storing and filtering JSON values. JSON paths such as $.errors[1].code can be used in filters.
Sync services can now be managed in the new database settings, including a new assistant for creating sync services, access to the sync job logs and the option to delete sync services.
Columns can now be duplicated in the new database settings.
The modern object picker is now fully available.
Status columns can now be used to color entries in the timeline view.
Activities can now reference existing data records.

Portals now provide built-in dynamic groups. Enforced filters can now be applied per dynamic group and company, and access to data records of other companies is denied.

A new "Admin" role has been added.
Roles can now be assigned in the permissions overlay, and permissions that are not covered by any role are highlighted.

A central button for creating workflows has been added to the workflow settings.
Workflow actions can now output JSON values.

The legacy database settings have been migrated to the new Data Explorer settings, including columns, templates, permissions, workflows, name appearance and the Expert Directory. Settings that have not yet been migrated are available in a dedicated "Legacy Settings" section.
Technical names of data columns are now generated automatically.
Switching between databases in the database settings now keeps the current view.
Data fields are now rendered as disabled if the current user does not have write access.
The data record preset of a template is now applied when creating a new child record.
Notifications for hidden child records are now redirected to the parent data record.
Live updates of data types are now synchronized in real-time.
The status settings now offer an icon editor.
Emails in the activity feed are now rendered more reliably, and activities can be submitted using a shortcut.

It is no longer possible to create new Classic automations. Use workflows instead.

Calculated permissions are not updated reliably.
Inherited viewer permissions are lost when removing a higher role.
The cursor jumps while typing in array values of the JSON input.
JSON values are deserialized twice.
Filters containing JSON paths with arrays cause errors.
The required validator of checkbox columns does not work.
The data editor does not apply read-only mode and its height differs between main and sidebar editor.
Dynamic groups handle errors incorrectly and are not loaded in the settings.
Switching a view in the settings reloads the whole page.

Users cannot change their language in the user settings.
Dark mode does not work correctly in customer portals.
Visible data fields are not taken into account when creating a data record in the customer portal.
Unsaved text changes of rich text editors persist after canceling the edit.
Images can be pasted into rich text editors even though no upload is configured.
The timeline view sends invalid event payloads.