Release 2025-01 (2025.1)

The first release of 2025 is a smaller release which brings improvements in the Assets module and the Asset+ approvals.

Assets

Email notifications for Asset approval requests

It is now possible to modify the default notifications for Asset approvals.

This allows you to customize the mails users receive in the approval cycle.

Reduce the number of notifications

DOQMIND previously sent frequent emails to many stakeholders during approval cycles. To reduce email clutter and prevent users from receiving notifications about their own actions, we have decreased the number of emails sent during each cycle. Then initiator of the approval will also receive mails at the end of each cycle.

Asset+ notifications will be sent according to the following table:

Keep cancelled Asset+ approvals visible

The history of approval cycles is accessible in the asset details modal. Previously, only completed and ongoing loops were displayed. With this release, cancelled approval loops and their status up to the point of cancellation will also be available.

Baskets

Our previous release introduced a new basket center. Based on feedback provided, a number of improvements have been made to this module:

Link details

In the ‘Links’ tab of the basket window, you can now see the details of each individual link via the context menu. These details include, amongst others, the message provided, the email addresses that were put in CC.

Improvements for orders

Following the last release, the basket content would lock, preventing any further actions. To both send a basket and create an Athena order from the same basket, duplication was necessary. In this release, you can create an Athena Order from a basket that has already been sent, or send out a basket for which an order has been created. However, once the basket expires, no further actions are possible.

Baskets expire 30 days after an order has been created, or at the expiry date specified when the basket was sent.

Projects

View right

Previously, users with access to the project could have a 'read only' right, which restricted all other rights. This restriction has now been changed to a 'view' right. All users with access to the project module will need at least this right. Existing users have been automatically granted this right.

Generic improvements

Other improvements

The system now clearly indicates the type of user in the logs and dropdowns. A user can be internal(int.), external(ext.) or remote (rem.)

Bugs fixes

Additionally, the following bugs were fixed: