> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/changelog/september-2026/september-22nd.md).

# September 22nd

**Changelog released on 2026-09-22**

This release includes two new features along with several improvements and bug fixes across Struct PIM.

Highlights include support for classifying variants in categories, federated Azure AD autologin, API improvements, and a number of usability and stability updates across search, business rules, webhooks, filtering, and the dashboard.

## New Feature

1. **Add support for classifying variants in categories:** (SP-2627)
2. **Support federated autologin from Azure AD:** (SP-983)

## Enhancement

1. **Created/Modified missing on Catalogue in API:** Catalogue now have Created / Last modified available through API. (SP-2954)
2. **Format background task elapsed time as hours, minutes and seconds:** (SP-2964)
3. **Zip files tries to create thumbnail resulting in an error:** (SP-3223)
4. **Add new folder directly from a global list:** (SP-460)

## Bug

1. **Sort order in entity search not matching order in tree:** (SP-2382)
2. **Webhook trigger other segments than selected :** (SP-3178)
3. **Business rule: Remove on complex sub-attribute fails when the entity has no value for the complex attribute:** Business rules that remove values on a sub-attribute of a complex attribute no longer fail on items that have no value for the complex attribute yet (SP-3183)
4. **Required subattribute can be submitted empty:** (SP-3195)

## Task

1. **Improve accessibility on dashboard widget fly-out:** Improved accessibility for dashboard widgets. (SP-2684)
2. **Internal Id filter should be text field across product, variant and variant group:** Internal id filter has been changed from min and max number field to a text field where it is possible to paste a list of internal ids. (SP-3171)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.struct.com/changelog/september-2026/september-22nd.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.