EDELOG 6.6

Major New Features

Redesigned Activities

With Edelog 6.0 we introduced Activities as a new way to track associated information along data records.

While Edelog's Activity system was always designed to help teams communicate better, the Activity experience was focused on a technical log.

Edelog 6.6 changes this. We're introducing many new features that will improve your daily work with Edelog:

Users can now use emojis to react to activities and quickly exchange thoughts about posts, emails, and other information inside the activity feed.
Users can comment on activities to discuss topics.
Activities can now be pinned to a data record. Pinned activities will always be displayed on top of the activity feed.
Activities can now be assigned to more than one data record. This allows users to attach posts, emails, and other information to another data record without copying data from one place to another.
Activities are now automatically grouped by month, making it easier to track the time progression inside the activity feed.
Activities can now be filtered by type.
Activities can now be marked as hidden.
Activities can now be individually assigned to a permission level. This will make it easier for users who also use Portal Builder, since it can now be precisely defined which activities are also available to external users.
Other users can now be mentioned inside comments or posts using the "@"-sign. Users who are mentioned will receive a notification.
Linked data records will now be displayed with better previews, that can be configured per database.
Linked forms are now displayed with better previews, including a status indicator.

New Expert Directory App

Expert Directory is a new app that enables you to create expert profiles and automatically create expert groups.

Expert profiles can be configured to include all necessary information about a person (e.g., contact data, skills, availabilities, locations, etc.).

This information can then be used to automatically create expert groups, that can be configured to include experts matching a defined criteria list. For example, you can create a group that contains all service technicians with a certain set of skills who are located in a certain country.

Behind the scenes, Expert Directory creates user groups that can be used to assign all experts to a given data record.

Additionally, with the "Expert Selection" database extension, users can now browse through all experts of Expert Directory directly from within Data Explorer. With this, you can – for example – find the right expert to solve a problem directly from within a service ticket.

New Features and Non-Breaking Changes

New Data Sheet Time Scheduler

Edelog 6.6 includes a new time scheduler data sheet. This data sheet can be used to schedule assigned users and groups and quickly browse and find available resources.

This new data sheet can be added to any database directly from within its settings.

Improved "Send Mail" Automation, New "Send Notification" Automation

The "Send Mail" automation has been improved. It now features a full editor to compose outgoing messages. Furthermore, you can now use email addresses of linked users as destination for emails.

With the new "Send Notification" automation, you can use Edelog's automation system to send notifications to Edelog users. Like the "Send Mail" automation, linked users can also be used as target.

Other Changes

The references data sheet now also includes a create button, if the user has sufficient permissions to create new data records in the target database.
Forms app: Classic forms are now displayed using their title, if configured.
Some configuration fields are now optional when creating new database views, e.g., additional fields for tiles views.
Groups linked to users/groups fields of databases can now also receive notifications if the field has been configured to send notifications.
Form Builder app: Users without sufficient permissions will now see an info dialog instead of automatically being redirected to the Forms app.
Data sync services will now also support users/groups fields.
Classic Forms: Print settings will now also be displayed for "Headline" and "Description" task types.
Users can now choose to always receive notifications via email, even if they're online.
Data Layer: Reassignments of the same value are now ignored and therefore won't trigger creating activities.
When creating new data records, users can use the new "Create + New" button to immediately create another new data record.
User/group settings now feature a "Force Logout" button that can be used to terminate all sessions of a user/all users within the group.
Objects/users/groups can now be deselected from within the single-select object/user/group input.

Bug Fixes

Fixes a problem that prevented users from leaving the editor of the Wiki app.
Fixes a problem that prevented users from opening data records from within the "Variation Tree" view of data records.
Fixes a problem that displayed the wrong database title field inside the database settings.
Fixes a problem that causes notifications to display a data record's ID as title instead of the actual title field.
Fixes a problem that causes "Classic Form" activities to sometimes be linked to a wrong user.
Fixes a problem that prevented the "Edit Filter" sidebar not to disappear if another filter has been set. This has been reported as being confusing since the "Edit Filter" sidebar would still display the previously used filter.
Portals: Fixes a problem that prevented portal users from editing activities.
Portals: Fixes a problem that prevented portal users from accessing a data record's activity feed even if the necessary permissions have been set.
Fixes a problem that causes an error being displayed when accessing a data record's title immediately after its creation.
Fixes a problem that causes dropdowns to display the wrong element being selected under certain circumstances.

Developer Notices

Apps can now access Activity APIs if they have the permit DATABASES::WRITE_ACTIVITIES.
Apps can now be defined to be run with system privileges. This is done using the ENV variable SYSTEM_LEVEL_APP_NAMES .
Edelog Core Server now requires Ruby 2.7.4.