EDELOG 6.3

Major New Features

Advanced Database View "Table" with Linked Fields

Edelog now has an updated database view "table" that incorporates many usability enhancements as well as new features to drive your daily work.

A major part is the ability to display data fields of other databases linked to a data record.

Since also the visualization of data inside the table has changed, we're reaching out for feedback before rolling out these changes to all other database views and other places we're currently using the old data table.

The new data table includes these changes:

• Columns can be resized by draging the space beetween the columns

• Columns can be automatically resized by double clicking the space between the columns

• Data now longer uses multiple lines when being displayed inside the table, since overflowing content is simply hidden

• Header and footer rows of the new table are now fixed when scrolling

• The footer column – for now – displays the current amount of records being displayed in the table. In the future we'll be adding support for aggregation functions (like average, min, max, count, etc.) per column.

• Visualization of different data types have been improved:

  • Boolean values are now more distingishuable

  • Date & time and numeric values are now aligned right

  • Files are now displayed inline as link for direct access to the file

  • Users and groups are now displayed with their profile picture only to be more compact. The user or group's name is displayed on mouse over.

  • Status now also display's the status's icon

• Columns that are sortable are more distingishuable from non-sortable columns

Linked fields can be added to your table view through its view settings. When added, linked fields will display the linked database's value of the target field.

New Login and Identity Settings

With the transition from Edelog 5 to Edelog 6 we've transitioned from password to magic link authentication. While this drastically improves the ease of use for the large proportion of Edelog users, for some users and use cases this solution is not as suitable as we've originally intended.

Therefore, we're re-introducing password-based authentication alongside magic link authentication in Edelog 6.3.

With this change we've updated our user management system that has been around since the first release of Edelog.

The new user management system is more modular and can be extended with custom authentication methods (like OAuth or LDAP) by hosting providers and configured by organization administrators. For this we're planning to release an Identity Provider SDK in the next months.

The new login and identity settings include these changes:

• Password-based authentication is re-introduced

• Users and administrators can configure identity settings per user

• Password-based authentication supports two-factor authentication

• Magic link authentication now includes the ability to authenticate via a one-time code that is sent via email as well as the already known link for direct authentication

• Magic links / one-time codes can only be used once within 10 minutes

Added New Global Search Interface

Edelog's global search interface has been updated in a significant way. You are now able to browse through all search results (not only the first 15 results).

Furthermore, you can filter search results by data origin.

The new search interface also saves your latest searches on your computer for quick access.

New Features and Non-Breaking Changes

Removed Data Object Variations

Data object variations have been removed from Edelog. All existing variations and variation tree views will automatically be migrated into their own database during this update.

The reason behind this is that the current implementation has many different problems that could not be addressed in the way data object variations are currently implemented. An example is that a variation setting of a data record could not be changed after the data record has been created.

This update also removes the "Variation" information in a data record's meta view.

Updated Subordinate Data Record Behavior

The behavior of subordinate data records has been updated. When creating a subordinate data record, its parent now has to be assigned to a link field. The link field will automatically set when creating a subordinate data record.

The subordinate data records now behave like regular linked data records: There association with their parent records can be removed and changed.

Subordinate data records won't be removed anymore if their parent is removed.

During this update necessary association fields are automatically generated if not already present.

Updated Database View "Hierarchy"

The database view "hierarchy" is no longer bound to subordinate data record. Instead of that, all self-referencing link fields can be used to create a database view "hierarchy".

Redirect Building Blocks in Portal Builder

Portal Builder has a new building block type "Redirects" that can be used to redirect a user to a given URL.

Other Changes

• Added a configuration option for app policy secondary name in the app's settings page.

• Portal Builder's database access permissions can be configured more granulary.

• FQN can be changed for users and groups

• It is no longer required to specify an email address when creating or updating a user

• App policies are now sorted by tile/name in an app's settings page.

Bug Fixes

• Fixes a problem that causes an app's permission settings to be not usable when a large quantity of app policies is available.

• Fixes a problem that caused date formats to always be rendered in the American date format.

• Fixes a problem that causes Portal Builder database access permissions to display a blank dropdown field under certain circumstances.

• Fixes a problem that causes deletion of data objects to take unexpectedly long.

• Fixes a problem that causes some user interfaces to be inaccessible on smaller monitors.

• Fixes a problem that causes some form labels to be rendered in the wrong location when a toggle input is used.

• Fixes a problem that causes editing policies to throw an error if a policy's secondary name has been specified.

• Fixes a problem that causes references to users or groups not correctly being removed if the user or the group is removed.

Developer Notices

• Many environment variables have been added to control Edelog's features and startup behavior (like automatically migrate the database on startup).

• Data object variation APIs have been marked as obsolete. They still exist but will no longer return any data. These APIs will be removed with Edelog 7.

• The data filter "parentDataObjectId" has been removed

• Advanced data filter statements now support "is NULL" comparisons by using the value "NULL" or "null" in equal or not equal comparison statements

• APIv4 /sessions/login is deprecated in favor of /sessions/authenticate

• OAuth password grant and /sessions/login has an updated behavior when being accessed if the user has two-factor authentication enabled: In this case, the user is required to append the two-factor authentication token to the password.

• Many APIv1 routes have been removed:

  • OAuth response

  • OAuth token

  • Reset password request

  • Route to reset passwords

  • API no longer can change a user's password

• The classic Edelog interfaces for resetting user passwords and associated emails have been removed.

• For hosting providers: Some commonly used user and organization management tools have been added.