Release Notes v2025.09
The new MARMIND v.2025.09 offers the following changes:
General
1 | Bookmarks on startpage | The bookmark tile on the start page now displays the responsible person defined in the bookmark instead of the creator. |
Details
1
| Bilinguality | Language chosen for field "Name" when creating new formats | Per default, user language is now used when filling out the field "Name" in the dialog of creating new formats in a bilingual environment. |
Plan
1
| Checkbox for deactivation of background color of calendars | The defined background color for a working days or important days calendar, which is normally shown as a background color overlay in the Plan module, can now be deactivated with a checkbox in the admin section. |
Grid
1
| Bulk-add KPI to objects | The “Add Key Figure” function has been added to all KPI columns in the grid, allowing a key figure to be added to multiple objects simultaneously. |
Dashboard
1
| Improved usability in the Diagram Wizard | Change to the order of tabs on page 4 “Preview” – the “Data” tab is now first in line and opens directly. In addition, the grouping type for new charts is set to “None” by default so that users can see a preview immediately upon opening. |
2 | 100% Bar Charts | Users can now visualize metrics as percentage-based bar charts. Each bar represents the percentage share of the total (100%), and the sum of all bars always equals 100%. Tooltips display percentage values, and axes indicate percentages clearly. |
Budget & Costs
1
| Budget & Cost Grid: Hide empty rows | A new “Hide empty rows” option has been added to the Budget & Cost Grid under a new “Display” menu in the toolbar. By default, all rows remain visible, but enabling this option will limit the grid to rows where costs are entered. Hidden rows reappear dynamically as soon as new costs are added, without requiring a refresh. The setting applies to all grouping views and can be saved in bookmarks. |
2
| Pre-filled Period Field when Creating Costs | When creating a cost item from a tree object (e.g. campaign, project, action), the start date of the object is now automatically pre-filled in the period field of the cost creation dialog. If no start date is defined or lies outside the available planning period, the system defaults to the current month - same as before. This behavior does not change when creating costs directly in the Budget & Cost grid; the selected grid cell still defines the pre-filled period. |
3 | Removal of the Old "Cost Grid" View
| As announced in the August release notes 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. |
Workflows
1
| Copying/synchronizing campaigns: Enhancement for workflow checks | Workflow is enhanced to be able to check whether an object creation was based on the copy function and/or synchronization.
Workflow is enhanced to be able to check from which original entity the object was copied or synchronized. Information of original entity where object was copied or synced from is available to the workflow scripting so that Mindscript can also be used to check the source entity. |
2 | Workflows: DataTable now respects “Lock Entity” | When a workflow locks an entity, DataTable are now also read-only (like other fields). Users can no longer edit the table while locked. |
Custom Fields
1
| New Custom Fields: Validation improvements | For the new Custom Fields, all admin-defined rules (min/max, length, RegEx, lookup limits) now always successfully block saving/auto-save until valid. Existing invalid values remain saved but once edited they must pass validation. |
2 | New Custom Fields: Improved validation styling | In the new Custom Fields, validation has been improved overall. Both the design and the feedback for invalid inputs are now clearer and more consistent. |
3 | Admin: Consistent naming for "Name" & "Description" | Previously, admin screens used inconsistent labels (“Name” vs. “Description”). We’ve standardised them across all creation/selection views, list headers, and error messages: “Name” becomes “Technical name” (internal identifier) “Description” becomes “Display name” (shown to end users). |
4 | Custom Fields reload on category change | When changing an object’s category, its Custom Fields now reload automatically so the correct set for the new category is shown. |
5 | New Custom Fields Now Live on Staging | The new Custom Fields are now live for everyone in the staging environment. This upgrade improves performance, slight design changes, and lays the technical foundation for upcoming features. Existing functionality remains unchanged, but you can already explore newly introduced features:
Rollout to live systems is currently planned for the October release. |