Release Notes v2025.02

1 

Archived objects in the plan 

Archived objects are now displayed in italic font in the plan. 

2 

Display Work Calendar Description in Info-Box Menu 

The description of work calendars is now displayed in the Info-Box menu when the "Info-box > Description" option is enabled in the Display menu. This improves clarity. 

1 

To-dos | Improvement in the use of checklists 

The use of to-do checklists with context restrictions has been improved. Users now receive an indication if no to-do checklists are available for a specific context. 

2 

Automatic Tag Update When Changing "Belongs-To" in New To-Do Dialog  

Tags are now automatically updated to match the selected parent element when the "Belongs-To" field is changed in the "New To-Do" dialog. This ensures that users always work with the correct set of tags, improving efficiency and accuracy. 

1 

Changeable periods when linking costs 

In the pop-up for linking costs/actuals, you can now also adjust the period (month/year) of the individual line items, if you have the rights to do so and the budget planning area's settings allow this. 

2 

Bugfix | Filter by object search shows all results 

If you set a filter on a specific object in the B&C module (tree view) using the object search field, all existing sub-contexts are now also displayed under the search result. This was previously limited to 1x level under the search result.  

1 

Extension of workflow function "Lock entity" 

The “Lock entity” workflow function has now been made available for all tree objects. It can be used to lock (or unlock) the entire DETAILS form of objects (including custom panels) on the client side using a workflow step. In the subsequent release, this locking of fields will also be implemented in the Grid and Plan module. 

1 

Bilinguality for custom description fields 

Custom fields of the type “Description” now also support bilinguality. 

2 

Bilinguality - Teaser texts 

Teaser texts of custom fields that support them can now be entered in German and English. 

3 

Mindscript extension for assets 

The file extension and the following standard fields of assets can now be queried via Mindscript - see also Mindscript documentation “...marmind.com/help/mindscript#entity-Attachment”:  

• Rights valid from  

• Rights valid until  

• Does not expire  

• Dimensions (for images and videos)  

These new Mindscript attributes can also be used in the workflow, e.g. for checking them during the upload process. 

4 

Mindscript extension for key figures  

You can now use Mindscript to access key figures (KeyFigureItems) of objects in the tree. This also works in combination with expressions such as “Parent" or "InnermostInitiative". (See Mindscript documentation). 

1 

SQL performance improved  

We have optimized SQL queries as follows to make MARMIND more performant:  

• Query Execution Speed-Up: Optimized query execution plans to reduce latency and improve overall database responsiveness. 

• Index Optimization: Introduced intelligent indexing strategies, reducing unnecessary scans and improving lookup efficiency.  

• Optimized Joins & Aggregations: Enhanced join and aggregation operations, minimizing resource consumption while maintaining result accuracy.  

• Better Query Caching: Implemented smarter query caching mechanisms, reducing redundant computations for frequently executed queries.  

2 

GraphQL: Read Cost center and Entity on cost objects 

The GraphQL API has been extended to support the reading of entities and cost centers for cost objects. 

3 

GraphQL: Support for linking of costs and actuals via purchaseOrderMappings 

Support for purchaseOrderMappings has been implemented in GraphQL, including the ability to add or remove linked costs and actuals via mutations. Linked objects are now directly readable within purchase orders via the attributes mappedCosts and mappedActuals. The following mutations have been added:  

• createPurchaseOrderMapping to link purchase orders  

• removePurchaseOrderMapping to remove an existing link 

4 

GraphQL: Validation of SyncLookupLists Arguments 

Added validation to ensure consistency in SyncLookupLists arguments, preventing issues caused by mismatched prefixes and names (e.g., "Strategy_goal" vs. "Strategy goal"). This avoids unintended behavior during synchronization. 

5 

Create, write and delete mutations via GraphQL API  

The GraphQL functions have been extended. It is now possible to create, write and delete mutations via the API. The read function was already available.