Release Notes v2025.08
The new MARMIND v.2025.08 offers the following changes:
General
1 | Responsible User Assignment in Bookmarks | The process for saving bookmarks has been enhanced to ensure that only users with the appropriate contextual access may be designated as responsible within bookmarks. |
2 | New Marmind Logo | As part of Marmind’s recent brand refresh, the updated logo has been applied across the system - this affects only instances without a custom logo. |
To-dos
1
| To-do checklists | Predefinition of participants per to-do possible | The configuration of to-do checklists in the settings has been expanded In addition to the responsibility, it is now optionally possible to define participants per to-do using the custom roles |
Budget & Costs
1
| Budget & Cost Grid: Improved Cost Column Structure | The column structure of the budget and cost grid has been revised to provide greater transparency regarding cost types and their statuses.
|
2
| Workflows: Notify the tree object responsible of budget values | It is now possible to configure notifications to the individuals responsible for the "Parent objects" of budgets through the budget workflow. |
3 | Announcement: Removal of the Old "Cost Grid" View
| With the upcoming Marmind September release on September 11, the legacy "Cost Grid" view in the Budget & Cost module will be removed and will no longer be available. As part of this change, all existing bookmarks related to the "Cost Grid" will also be deleted.
The "Cost Grid" had been marked as deprecated for some time, and we have now decided to fully retire it. All functionality previously available in the "Cost Grid"—and much more—is already available in the "Budget & Cost Grid". If you have any questions, please contact your Project Manager at MARMIND. |
Custom Fields
1
| Help tooltips for new Custom Fields | Bilingual (EN/DE) help tooltips can be added by administrators to fields in the new Custom Fields. A tooltip icon is displayed next to the field name, and hovering over it reveals the full text. This feature is not present in the previous version of Custom Fields. |
2 | Custom Fields reload on category change | When an object's category is changed, its Custom Fields automatically reload to display the set corresponding to the new category. |
3 | Custom Fields: Warn users when leaving with unsaved changes | A warning appears for users when they attempt to navigate away or close the window with unsaved edits in Custom Fields. |
GraphQL
1
| API/GraphQL: Condition-based visibility for groups & panels (only new Custom Fields) | Condition based visibility for groups and panels can now be read and updated via GraphQL (Only for new Custom Fields). |