# August 12th

**Changelog released on 2025-08-12**

Welcome to this release: Category children loopup has been optimized for large catalogues, the “Product updated changeset” webhook now includes PreviousCategories and AI Translation handles max request sizes more graciously. We’ve also made improvements to image previews, search and fixed multiple bugs.

## Bug

1. **Search do not remember selected page size:** Page size is now persisted when navigating away and back to the search page. (SP-1400)
2. **System texts/translations in Publications module:** Text in publication module has been changed to align with the rest of the PIM. (SP-1433)
3. **Workflow color-swatches missing from search:** Workflow color-swatches are now present on the search page when using the 'Workflow state' column. (SP-1442)
4. **Insert progresslog in db during the background job run:** Progresslog is now correctly inserted into the database during background job runs. (SP-1486)
5. **PIM\_PrimaryCategory is not migrated:** PIM\_PrimaryCategory from V3 is now mapped to the master catalogue when migrated. (SP-1567)
6. **Clicking "See more" on a notification changes page:** Clicking see more on the notification changes page now unfolds the notification instead of navigating to the entity. (SP-1593)
7. **No preview of video and documents when creating a user-task:** Preview of video and documents now work when creating a user-task. (SP-1596)
8. **Missing image preview on asset attributes on global lists:** Images added to asset attributes that are subattributes of a complex in a global list, did not show a preview image. (SP-1600)
9. **Categories don't show up as subscribed entities in the Notification center:** Subscribed to categories are now present in the Notification center. (SP-1630)
10. **Workflow state in search is shown as text, not a graphical element:** Workflow color-swatches are now present on the search page when using the 'Workflow state' column. (SP-581)

## Task

1. **Optimize category children lookup for large catalogues:** Category children lookup in large catalogues is now faster. (SP-1111)
2. **Null reference on reference attribute:** Having a reference attribute with 'Allow multiple' would sometimes cause it to have a null reference. (SP-1133)
3. **Sortorder on variationdefinition is not taken into account if fetching multiple:** When fetching multiple variation definitions, they did not follow the correct sort order. (SP-1182)
4. **Attributes - mandatory list attribute can be empty:** A list attribute with a complex subattribute marked as 'mandatory' was allowed to be empty. This is no longer the case. (SP-1197)
5. **Read-only identifiers is empty after creating entity through UI:** Read-only fields are now not allowed in the creation wizards or for identifiers. (SP-1200)
6. **AI Translation: Handle maximum request size limit:** The AI Translation now handles requests that exceed the maximum request size limit. (SP-1230)
7. **Update 'Product updated changeset' to also include 'PreviousCategories' (webhook):** The field 'PreviousCategories' has been added to the 'Product updated changeset' in webhooks. (SP-1343)
8. **External DAM folders should be available for asset-reference upload folders:** When dragging an asset into a asset-reference field the asset will be uploaded to the selected folder, which should match folders of the used external-DAM. (SP-1572)
9. **Indicate which folders are private in the folder-picker:** Private folders in the folder-picker now visually looks the same as everywhere else. (SP-998)

## Feature request

1. **RTE uses same text font and font size as normal text attributes:** Text fields using the rich text editor has been changed to use the same text font and size as normal text attributes. (SP-1556)


---

# 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/august-2025/august-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.