> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/support/releases/appcontrol-2026/2026.5.0.md).
# 2026.5.0
***
**Upgrade Notes**
To support the detection of AI components, the central repository has been upgraded. Complete the following steps after upgrading.
1. Go to Administration > Repository and click 'Force Update Repository'. This process will take a long time and may time out in the UI. Check 'Running Now' in the environment information for your AppControl environment in the Mendix Cloud to confirm when it has completed.
2. After the repository has synced, go to Administration > System Logs / Tools > System Tools > Database Actions > Upgrades and click 'Update AI Components'. This may also take a long time and may time out in the UI. Check 'Running Now' in the environment information for your AppControl environment in the Mendix Cloud to confirm when it has completed.
***
**New Features**
\[POLICIES] COMP\_0013 — App uses AI components. A new policy check has been added that detects the presence of AI components within Mendix apps.
\[INSIGHTS] AI Component. A new column is available in the Components tab that shows if a component uses AI. This feature helps to support you with AI governance.
\[CORE] Add enable/disable toggle to apps list in system configuration. Administrators can now bulk enable or disable groups of apps directly from the system configuration apps list.
***
**Improvements**
\[CORE] Improve scalability of policy engine. The policy engine has been updated to handle larger app portfolios more efficiently.
\[CORE] Rename Ignored Checks to Accepted Risks. The "Ignored Checks" concept has been renamed to "Accepted Risks" across the platform for clarity.
\[POLICIES] Add additional release information. The release page now includes additional information to improve traceability and auditing.
\[POLICIES] Add Marketplace vulnerability information to the repository. Marketplace components are now enriched with vulnerability data collected from the Mendix Marketplace.
\[POLICIES] Detect updated policy settings in pipeline. The ‘Check Policy’ pipeline task now identifies when policy settings have changed since the last scan. If the policy has changed recently the revision to be deployed will be rechecked.
\[UX & SUPPORT] Remove save button from App Group Manager page. The App Group Manager page now auto-saves, removing the need for a manual save action.
***
**Resolved Issues**
\[CORE] Endless loop in app checker when looking up module name. Fixed a loop condition that caused the app checker to hang during module name resolution.
\[CORE] MMMIAASAPNA — No app found when processing new alert. Resolved an error that prevented new alerts from being processed when the associated app could not be found.
\[TASKS] Release task scheduling is ignored after approval task. Fixed an issue where scheduled release tasks were not triggered correctly following an approval step.
\[UX & SUPPORT] Generic error in Task Queue overview. Resolved a generic error that appeared in the Task Queue overview under certain conditions.
\[POLICIES] DOM\_0002 should use Entity ID instead of Domain Model ID. The DOM\_0002 policy check now correctly references Entity ID for accurate domain model analysis.
\[CORE] Use semver check to prevent invalid version numbers sent as fingerprints. Added a semver validation guard to reject malformed version strings before they are processed as fingerprints.
\[CORE] Changed Mendix Project ID causes app list update to fail. Fixed a failure in the app list update when a Mendix Project ID changes but the Mendix App ID remains the same.
\[CORE] Java manifest version length causes model processing to fail. Resolved a parsing error triggered by excessively long version strings in Java manifests.
\[POLICIES] Unable to reset global policy to defaults. Fixed an issue preventing global policy settings from being reset to their default values.
\[CORE] Model processor is not detecting nested widgets correctly. The model processor now correctly identifies widgets nested within other widgets.
\[TASKS] Check policy task uses incorrect revision when using existing package. Fixed a revision mismatch that occurred when a check policy task reused an existing deployment package.
\[UX & SUPPORT] Currently selected user group changes suddenly when cancelling pop-up. Resolved a UI issue where dismissing a pop-up unexpectedly changed the active user group selection.
\[CORE] App does not show up in app list after being added. Fixed a bug where newly added apps failed to appear in the app list without a manual refresh.
\[CORE] Add system script to add missing policy checks. A system script is now available to add policy checks missing from app policies.
\[CORE] Only use active group policy as source when initializing app policy defaults. App policy defaults are now sourced exclusively from active group policies during initialization if a group policy exists and is active. Previously, group policies were used even if they were inactive.
\[TASKS] Models should not be processed for disabled apps. Model processing now skips apps that have been disabled in system configuration.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.bluestorm.io/support/releases/appcontrol-2026/2026.5.0.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.