> 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/december-2025/december-5th.md).

# December 5th

**Changelog released on 2025-12-05**

Welcome to our latest release. We’ve fixed an issue where modifying Global List values in a Business Rule did not live-update the UI and resolved an occasional failure of searches on global list reference attributes when executed too quickly.

## Bug

1. **Search on global list reference attribute on entity sometimes fails when done too quickly:** The user is correctly shown what they are searching for in the global list attribute field.\
   (SP-1990)
2. **Business Rule does not live-update UI when modifying Global List values:** Fixed an issue where business rule updates to a global list reference attribute requires manual page reload. UI now updates when clicking “Save”.\
   (SP-1997)


---

# 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/december-2025/december-5th.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.