> 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/july-2025/july-23rd.md).

# July 23rd

**Changelog released on 2025-07-23**

Welcome to the latest changelog. Empty values are now allowed when matching attributes in business rules. The option to manually run business rules has been restored and a global list value ID rendering issue is fixed.

## Bug

1. **Wrong rendering of id in global list value:** The id shown in meta information about global list values now correctly shows the id of the global list value instead of the global list. (SP-1580)
2. **Manually run business rule functionality missing:** It is now possible to run a business rule manually by hovering the mouse over the trigger and clicking the 'Run manually'-button. (SP-1590)
3. **Match attribute does not allow empty values:** Empty values are now allowed when using the 'Match attribute'-condition in business rules. (SP-1591)


---

# 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/july-2025/july-23rd.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.