This topic provides details about the enhancements in Composer 7.5.
- User Auditing
- Trusted Access
- Histogram Updates
- Map: Markers Update
- Count Metrics for Materializations
- Extended Object ID
- Dashboard Reporting Support
Composer now supports robust user auditing for data accessed directly in the Composer Playground UI, via an API, or as embedded objects.
Once enabled and configured, users with appropriate access can see who accessed data, how the data was accessed, and when users accessed it. Events such as opening and viewing a visual, receiving a scheduled dashboard, exporting raw data, creating, or updating visuals or dashboards using data are captured.
For more information about how you can use user auditing, see:
- User Auditing
- Enable and Configure User Auditing
- User Auditing for Multi Tenancy Environments
- Enable User Audit Data for Composer Accounts
- Enable User Audit Data for Multi Tenant Accounts
- Consuming Audit Data
- User Audit Events
Composer now manages trusted user access in a more streamlined fashion, utilizing two new, expanded endpoints.
To reduce the complexity of generating and using trusted access tokens for new and existing users, Logi Composer supports two new endpoints:
/api/trusted-access/push/tokens. Use either endpoint to generate an access token.
If a user belongs to more than one Composer account, specify an account as part of the payload to generate a token for the desired Composer account.
Both the Trusted Access and OAUTH protocol must be enabled before you use either endpoint to generate access tokens.
Use pull to request a user access token for users that already exist in Composer.
The user must already exist, and have an active Composer user account (unless you are using LDAP with automatic provisioning for Composer).
You can't update user context such as user attributes or groups using
Use push to request a user access token for new and existing users by sending their context to Composer. Existing users are updated if their context has changed.
Context must contain
Several reserved keys are restricted from use in Composer as custom user attributes:
The Cumulative Line setting for Histograms is now in the Settings panel.
Several label changes correctly reflect the changes you make to a histogram.
The Labels section now indicates that changes made here affect Y-Axis Labels.
Append Absolute Value is now Absolute Values.
Append Relative Value is now Relative Values.
When you upgrade and migrate your content to this version of Composer, the Map: Markers creation process is simplified by removal of several attributes from the creation flow.
These can be edited in the Settings panel; allowed values are between 1 and 22.
Composer now requires you add a Count mapping when creating a new materialization view.
Select Add Count after specifying an entity.
Specify a Target Column and source field.
Select Apply to apply the mapping to the materialized view definition.
Composer now creates IDs for system objects, up to 36 characters in length, when you create or migrate objects.
These IDs can be a mix of lower case letters, numbers, and dashes. Dashes can't start or end an ID, or be consecutive.
dataviews 3f0191fc-5256-4770-ac06-60b3ca1f8864 4476244f-a3e0-4dcb-8abc-b1c1b164e23b dashboards 0f343e2ca09dc98933e401b7370008f6 1b2ba0dcb3a10df482eb2fe80c218769 tags 01721e6d-92a3-4d1e-8641-9ed973df3f2f 3f041fc-5256-4770-ac09-60b3ca1f8864 visuals vdbfbc9bc-cdx6-4e02-a0d2-fdfa01f4ea1d vdd0d33b0-1r76-4237-9daa-8225f438d45e
Use Trusted Access to authorize connections for Dashboard Reporting. Security Keys have been fully deprecated.
The concurrent session count licensing restrictions apply to the trusted access token created for each recipient of the dashboard report. If the license limit is reached, the report won’t be sent.