User activity tracking and page-performance optimizations added for Applied Policies pages

Note:This feature is available with Automation.

The Applied Policies pages now leverage a new API to support user activity tracking for policy changes as well as faster page loading and overall performance. User activity on these pages, such as deleting a policy, editing a policy, or applying a policy are now logged. These activities will be trackable via the API Event endpoint in the Identity and Access Management API. Example API GET:

https://api.flexera.com/iam/v1/orgs/{orgId}/api-events?filter=(timestamp ge ‘2024-03-11 T14:00:00Z' and timestamp le '2024-03-01T16:00:00Z') 

Note:For more information about the API Event endpoint, see the API documentation on developer.flexera.com: Identity and Access Management API: API Event.

Performance optimizations allow the Applied Policies pages in the Flexera One UI to render more efficiently at scale. Users will also notice some user experience changes for the Applied Policies page as a result of the performance optimizations:

Pagination—Policy lists are paginated with 50 policies per page. This change makes Applied Policies pages load more efficiently. It also changes the output of exports from these pages.
Export—Previously, exports from the Applied Policies page would export all policies that matched the current filter settings. Now, exports from Applied Policies only export the policies shown on the current page.
Filters—Small changes to the operation of filters on the Applied Policies page: Filters are not applied until you click Apply. Contains operator is case sensitive. Equals operator must be an exact match.

Exceptions: The Applied Policies page changes for this release have not been implemented for the Organization Summary view of Applied Policies nor for the Policy Templates and Policy Catalog pages. When applying policies from the catalog, user activity will not be logged.

Note:The legacy API for Applied Policies remains active.