Let us know your feedback!

Tell us how we can make App Catalog better.

Extended App Update Log Retention in Customer Portal

As a Security Engineer or Compliance Officer I want the App Catalog Customer Portal to retain and display app update logs for a longer duration than the current 90-day limit so that our organization remains compliant with strict regulatory frameworks (such as SOC 2, ISO 27001, HIPAA, or GDPR) that mandate long-term audit trail preservation, preventing compliance failures and historical tracking gaps during security reviews. Currently, the App Catalog Customer Portal enforces a 90-day retention limit on app update logs. While a 3-month window is sufficient for everyday operational troubleshooting, it creates a critical compliance gap for enterprise customers.

null null 14 days ago

πŸ’‘

Feature Request

Initiate app updates instead of opening Catalog App from Notification Center

As an End User I want the "Update Now" button on an update notification to immediately initiate the app update(s) in the background rather than opening the Catalog App interface so that I can update my applications with a single click, eliminating unnecessary navigation steps, reducing workflow friction, and saving time. Currently, when a user receives a Notification Center alert regarding an available app update, clicking the "Update Now" button acts as a shortcut link. It launches the Catalog App and opens on the "Updates" tab. This behavior introduces unexpected friction: The user expects the update to start when they click "Update Now." Instead, they are forced to wait for a desktop GUI to launch. They must then visually locate the update again and click a second confirmation button inside the app. This multi-step process disrupts the user's focus and actively discourages prompt app patching.

null null 14 days ago

πŸ’‘

Feature Request

Configurable graceful app termination

As an IT Administrator, I want the ability to configure whether an app update (when user interaction is required) enforces an immediate close or attempts a native, graceful termination request so that I can protect end-users from losing unsaved work in apps that lack macOS Auto Save support, while still retaining the ability to force immediate closures for critical security patches. Currently, the Catalog Agent terminates running apps ungracefully when the enforcement deadline is reached. If an app does not natively support macOS Auto Save architectures, users may lose unsaved data. This may result in data loss, user frustration, and increased helpdesk tickets.

null null 14 days ago

πŸ’‘

Feature Request