> 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-8th.md).

# September 8th

**Changelog released on 2026-09-15**

Welcome to the latest update! This release adds richer image actions and previews, improved variant import and grouping, workflow-state conditions for webhooks, internal ID search in the media picker, and better navigation for variants. We’ve also included several fixes around task lists, deleted-entity conditions, and variant group validation.

## Enhancement

1. **Open image directly from table view:** Hover any image in entity table to get a thumbnail and actions for maximize, download and go to asset (SP-2286)
2. **Create / Edit variant groups during variant import:** (SP-2506)
3. **Further image detail on entity thumbnail:** Hover on thumbnail on Entity editor now displays an overlay with actions for maximize, download and go to asset. (SP-3030)
4. **Conditional triggering based on workflowstate on webhooks:** Added conditional trigger option “In Workflow State” for product and variant updates on webhooks. (SP-3097)
5. **Add support for searching in internal ids in media picker:** (SP-3126)

## Bug

1. **Task list widget is clickable in edit mode:** (SP-2999)
2. **Conditions related to deleted entity missing criterias like Not Equal, Not contains:** (SP-3001)
3. **Variant group groping attributes validate variant model and not only variant group model:** (SP-3101)

## Task

1. **Maximize images on products:** Right click any asset reference to access new action maximize (SP-2689)
2. **Add 'Go to product'-breadcrumb under variants where the product is unclassified and has no title:** Added a ‘Go to product’ breadcrumb on the variants of unclassified products which does not have a title/name. (SP-3127)


---

# 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-8th.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.