# May 12th

**Changelog released on 2026-05-12**

This release introduces several usability and performance improvements across the platform, including support for importing metadata to assets, adjustable page sizes for global list values, and improved overview of translated content through a new field translation overview. Business rule execution has also been optimized to run in smaller batches for better stability and performance. In addition, the release includes a range of bug fixes addressing workflow state handling, dashboard permissions, date rendering issues, file template display problems, and various UI inconsistencies to improve the overall user experience.

## Enhancement

1. **Support importing assets with metadata to media library:** You can now map metadata for assets when importing. (SP-1548)
2. **Adjust page size for global list values:** User can now adjust the page size when looking at global list values in a global list. (SP-2359)
3. **Business rules: RuleSetup execute items in batches:** Fix an issue where business rules could run on to many items at a time. Will run in smaller batches now. (SP-2519)

## Bug

1. **User can delete workflowStates being used by business rules which result in errors:** Fixed a bug where the user could delete workflowStates that is being used by business rules. The user is now given an error if they attempt to delete a workflowState being used by a business rule. (SP-2487)
2. **Unsaved changes dialog showing in edit dynamic category query view while there are no unsaved changes:** When setting up or editing for dynamic category queries, users will not see an “Unsaved changes” dialog if there are none when navigating away. (SP-2495)
3. **Saving file template causes visual bug:** The file field mappings on file templates are now displayed correctly when updating the template. (SP-2504)
4. **Cannot leave edit mode when on shared dashboard without permission to manage:** User who does not have permission to manage shared dashboard will now be taken out of edit mode allowing them to use/view the shared dashboard. (SP-2507)
5. **LastModified is not updated on asset updates:** Fixed a bug where if the user updated an asset then LastModified would not be updated. (SP-2508)
6. **DateTime sub-attribute shows 'Invalid date' if set to a date in the past when used in a list:** Fixed a bug where DateTime sub-attributes would show 'Invalid date' if set to a date in the past when used in a list type attribute. (SP-2510)
7. **Global list with no display/backoffice rendering set and empty value in first subattribute renders unnecessary comma:** Fixed a bug where global list with no display/backoffice rendering ser and empty value would render unnecessary comma. (SP-2525)

## Task

1. **Adjust widgets to make them easier to distinguish from each other:** Widget titles are clearly distinguishable and correctly associated with their content, reducing user misinterpretation. (SP-2364)
2. **Add rich text editor(RTE) to app description:** App description for apps in App store are now rich text editors. (SP-2404)
3. **Mark as dirty from extension point on data model:** From an external tab, section or property it is possible to notify the PIM if content is dirty or prestine, ensuring the display of unsaved changes dialog when navigating away from current tab/content. (SP-2491)
4. **Add info of previous fields in changeset for Variant updates:** When triggering webhooks for update variant events, previous product Id and previous Variant Group Id are now included in the changeset when a change to product or variant group is made. (SP-2514)
5. **Copy catalogue including dynamic categories can be slow:** Copying a catalogue with dynamic categories is now faster. (SP-977)

## Feature request

1. **Overview of translated content on fields.:** It is now possible to see an overview of translated content on a selected field. This can be done via the context menu shown, when right-clicking on a field while on an entity. (SP-2529)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.struct.com/changelog/may-2026/may-12th.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.