Skip to main content

Composer 24.1 Release Notes

  • Updated

Composer 24.1 Release Notes

This topic describes feature enhancements, resolved issues, and important information for Composer 24.1.

To purchase this product, contact insightsoftware Sales.

See also Important Notices, Deprecated Features, and Composer Version 24 Summary of Changes.

Composer is offered on a quarterly release schedule, and our version numbering system reflects this. The current major release of Composer is v24.4.

Important: Composer v7, a passive support release, is supported with service packs that address only critical patches and security updates. Composer v7 is in passive support as of September 1, 2023. Security updates are not applicable to third-party dependencies. Changes to existing functionality, bug fixes, and workarounds are described in the Release Notes. Composer v7 is at end of life as of September 1, 2024. See Composer Release Vehicles.

Feature Enhancements

Title Description

24.1.12 Feature Enhancements

None.

24.1.11 Feature Enhancements

None.

24.1.10 Feature Enhancements

None.

24.1.9 Feature Enhancements

None.

24.1.8 Feature Enhancements

None.

24.1.7 Feature Enhancements

None.

24.1.6 Feature Enhancements

None.

24.1.5 Feature Enhancements

None.

24.1.4 Feature Enhancements

None.

24.1.3 Feature Enhancements

None.

24.1.2 Feature Enhancements

SAP S/4HANA Support

Composer now includes an SAP S/4HANA connector. See Manage the SAP S/4HANA Connector.

24.1.1 Feature Enhancements

None.

24.1 Feature Enhancements

Enhanced Filter Security Capabilities

We've expanded the filter capabilities to present data more securely to your users. Filter values can be shown in masked format if you want to filter based on confidential data.

  • To enable, disable Filtering for fields in a data source for one or more data columns on the Fields tab of that data source.

  • Next, set the Value and Display fields in your filter snippets based on your needs.

  • When you view tool tips or hover over fields that have Filtering disabled, you won't see the actual values. Instead, you'll see a generic reference, such as a count of "filter values" or a series of asterisks ******.

Important: Applied filter values that later have Filtering disabled to not automatically mask or hide those fields. You must recreate the filter that uses these values.

You can now set and apply filters to filter snippets. Select a source to apply the filter in the filter snippet.

See Filter Data With Masked Fields.

Lite Dashboard for Self-Service Environments

We've added a simplified lite dashboard to your Composer environment. You can now embed a lite dashboard complete with its own interactivity settings, designed to get your users up and running quickly and easily.

Users can create dashboards with the default visual format as a table visual. Once created, users can:

  • Edit the visual's fields and settings, and optionally change the visual type to an available visual type.

  • Select an available visual type if the data source doesn't support a table visual, then edit the visual as needed.

Available visual types include: Table (default), Bars, Bars:Multiple Metrics, Donut, KPI, Packed Bubbles, Pie. Customize this list further in your embed code as needed to add or remove other visual types.

 

Suppress Time Zone Labels

You can now opt to suppress time zone labels in the Composer user interface.

After upgrading to this version, you can update the Data Details of your time fields in a data source and suppress the labels. Select Not Specified instead of a time zone to hide time zone information in the user interface and when users export data.

Content Migration Flow Improvements and Breaking Changes Management Expansion

  • You can now import and export visuals directly in the Visual Gallery user interface. Import and export one or more visuals in bulk. Import and Export includes any supporting objects the visuals are dependent on, such as data sources and connections.

  • When you import dashboards, visuals, and sources, Content Distributor group members and other users with appropriate privileges can enable Share Default Access With All Users. When enabled, in the UI or as an API option, users in the tenants you selected for import can access to these resources immediately based on default access levels.

  • View improved real-time import validation results, address errors, and suppress warnings for later handling with more options to correct issues in your environment.

  • The import process now considers an origin.id when importing objects: it is stored for every imported object on the target system.

    • When you import using the API, you can select a matching strategy for reusing and updating objects. See API Updates for more information.

  • When you select Ignore Warnings during import, a Tags field is added to the Import work area. Add or create tags to apply to objects that do not import cleanly.

    • If errors occur during import, Composer adds the tags you select to affected objects.

    • Use these tags to find the dashboards, visuals, filter snippets, or sources you need to fix.

  • You can also create or add tags for items that don't import cleanly when you import via API.

For more information, see Import DashboardsImport a Data Discovery Dashboards, Import Visual Gallery Visuals, and Import or Export Sources.

API Updates

API documentation is provided with your Composer installation at this link: https://<composer-URL>/composer/swagger-ui.html.

Endpoint Method Description

24.1.12 API Updates

None.

 

24.1.11 API Updates

None.

 

24.1.10 API Updates

None.

 

24.1.9 API Updates

None.

 

24.1.8 API Updates

None.

 

24.1.7 API Updates

None.

 

24.1.6 API Updates

None.

 

24.1.5 API Updates

None.

 

24.1.4 API Updates

None.

 

24.1.3 API Updates

None.

 

24.1.2 API Updates

None.

 

24.1.1 API Updates

/api/groups

POST, PUT

You can now assign an identifier to your groups using externalId that is unique across tenants. This does not change or replace the accountId assigned by Composer. The externalId is not available in the UI.

24.1 API Updates

/api/sources/export

GET

These attributes are returned for sources in your environment. Include these attributes to work with import matching strategies.

  • connections[].originId - Returns the value of the connection ID from the imported connection.

  • sources[].originId - Returns the value of the source ID from the imported source

/api/sources/import

POST

When you import objects into your environment, you can define a matching strategy that uses multiple approaches to reviewing objects to determine how to handle them in conjunction with your selected insertion strategy.

Matching strategies are processed in order, proceeding to the next and the next if a strategy fails.

If all strategies fail, the object is imported and tagged with your selected tags to help you find affected objects and manage any issues.

These attributes are used to define the matching strategy and warning tags to use for import. Send as an array; each strategy is considered in order.

  • importSettings.objectClassLevel.connections.matchingStrategy[] - Send an array of matching strategies to be considered, in order, for connections. This array can include:

    • BY_ORIGIN_ID

    • BY_ID_AND_TYPE_AND_PARAMS

    • BY_TYPE_AND_PARAMETERS

    • BY_NAME_AND_TYPE

    • BY_TYPE_AND_PARAM_KEYS

    • BY_NAME

      If an order is not specified, the default strategy of BY_ID_AND_TYPE_AND_PARAMS or BY_TYPE_AND_PARAMETERS is used.

  • importSettings.objectClassLevel.sources.matchingStrategy[] - Send an array of matching strategies to be considered, in order, for sources. This array can include:

    • BY_ORIGIN_ID

    • BY_NAME

      If an order is not specified, the default strategy of BY_NAME is used.

  • importSettings.warningTags[] - Send an array of warning tags to apply to objects imported with warnings.

Send enableDefaultRead to enable data read permissions for the sources imported for all users in the tenant.

/api/dashboards/export/

GET

These attributes are returned for dashboards in your environment. Include these attributes for importing.

  • connections[].originId - Returns the value of the associated connection ID.

  • sources[].originId - Returns the value of the associated source ID.

  • visuals[].originId - Returns the value of the associated visual ID.

  • dashboards[].originId - Returns the value of the associated dashboard ID.

/api/dashboards/import/

POST

When you import objects into your environment, you can define a matching strategy that uses multiple approaches to reviewing objects to determine how to handle them in conjunction with your selected insertion strategy.

Matching strategies are processed in order, proceeding to the next and the next if a strategy fails.

If all strategies fail, the object is imported and tagged with your selected tags to help you find affected objects and manage any issues.

These attributes are used to define the matching strategy and warning tags to use for import. Send as an array; each strategy is considered in order.

  • importSettings.objectClassLevel.connections.matchingStrategy[] - Send an array of matching strategies to be considered, in order, for connections. This array can include:

    • BY_ORIGIN_ID

    • BY_ID_AND_TYPE_AND_PARAMS

    • BY_TYPE_AND_PARAMETERS

    • BY_NAME_AND_TYPE

    • BY_TYPE_AND_PARAM_KEYS

    • BY_NAME

      If an order is not specified, the default strategy of BY_ID_AND_TYPE_AND_PARAMS or BY_TYPE_AND_PARAMETERS is used.

  • importSettings.objectClassLevel.visuals.matchingStrategy[] - Send an array of matching strategies to be considered, in order, for visuals. This array can include:

    • BY_ORIGIN_ID

    • BY_NAME

      If an order is not specified, the default strategy of BY_NAME is used.

  • importSettings.objectClassLevel.sources.matchingStrategy[] - Send an array of matching strategies to be considered, in order, for sources. This array can include:

    • BY_ORIGIN_ID

    • BY_NAME

      If an order is not specified, the default strategy of BY_NAME is used.

  • importSettings.objectClassLevel.dashboards.matchingStrategy[] - Send an array of matching strategies to be considered, in order, for dashboards. This array can include:

    • BY_ORIGIN_ID

    • BY_NAME

      If an order is not specified, the default strategy of BY_NAME is used.

  • importSettings.warningTags[] - Send an array of warning tags to apply to objects imported with warnings.

Send enableDefaultRead to enable data read permissions for the sources imported for all users in the tenant.

/api/visuals/export/

GET

These attributes are returned for visuals in your environment. Include these attributes for importing.

  • connections[].originId - Returns the value of the associated connection ID.

  • sources[].originId - Returns the value of the associated source ID.

  • visuals[].originId - Returns the value of the associated visual ID.

/api/visuals/import/

POST

When you import objects into your environment, you can define a matching strategy that uses multiple approaches to reviewing objects to determine how to handle them in conjunction with your selected insertion strategy.

Matching strategies are processed in order, proceeding to the next and the next if a strategy fails.

If all strategies fail, the object is imported and tagged with your selected tags to help you find affected objects and manage any issues.

These attributes are used to define the matching strategy and warning tags to use for import. Send as an array; each strategy is considered in order.

  • importSettings.objectClassLevel.connections.matchingStrategy[] - Send an array of matching strategies to be considered, in order, for connections. This array can include:

    • BY_ORIGIN_ID

    • BY_ID_AND_TYPE_AND_PARAMS

    • BY_TYPE_AND_PARAMETERS

    • BY_NAME_AND_TYPE

    • BY_TYPE_AND_PARAM_KEYS

    • BY_NAME

      If an order is not specified, the default strategy of BY_ID_AND_TYPE_AND_PARAMS or BY_TYPE_AND_PARAMETERS is used.

  • importSettings.objectClassLevel.visuals.matchingStrategy[] - Send an array of matching strategies to be considered, in order, for visuals. This array can include:

    • BY_ORIGIN_ID

    • BY_NAME

      If an order is not specified, the default strategy of BY_NAME is used.

  • importSettings.objectClassLevel.sources.matchingStrategy[] - Send an array of matching strategies to be considered, in order, for sources. This array can include:

    • BY_ORIGIN_ID

    • BY_NAME

      If an order is not specified, the default strategy of BY_NAME is used.

  • importSettings.warningTags[] - Send an array of warning tags to apply to objects imported with warnings.

Send enableDefaultRead to enable data read permissions for the sources imported for all users in the tenant.

/api/accounts/name/{name}

GET

This takes the {name} of the tenant account as a path parameter and returns tenant account details. Works similarly to /api/accounts/{id}/.

Resolved Issues

Title Description

24.1.12 Resolved Issues

Converting Custom SQL to Stored Procedure

When you convert custom SQL statements in a data to a stored procedure for visuals that also rely on custom metrics, Composer appropriately updates the underlying connector capabilities to support AGGREGATION, FILTERING, JOINING, PAGING_AND_SORTING, and PROJECTION.

First and Last Weeks of the Year

Data used in environments that use Australian time zones now appropriately reflect the correct weeks as the last and first weeks of the year.

Bar Charts

Changing the time zone on a user’s device no longer affects the appearance and behavior of date values used in some bar chart granularities.

24.1.11 Resolved Issues

Time Ranges

Corrected an issue that caused the time bars to display and render an incorrect start year for bar charts that used year ranges and granularity set to week.
Time Bar

Corrected an issue in the time bar that used and displayed UTC time in place of the configured time zone.

24.1.10 Resolved Issues

Embedded Dashboards

Corrected an issue that prevented selected dashboards from displaying properly in embedded environments.

24.1.9 Resolved Issues

None.

 

24.1.8 Resolved Issues

Line Trend: Attributes Visual Update

When you create a line trend visual that includes the option to include blank data, data with no value is displayed along with data that includes values.

24.1.7 Resolved Issues

Content Security

Added the value http.response.header.content-security-policy to zoomdata.properties. Use to add appropriate content security values to support your implementation. See zoomdata.properties Properties.

24.1.6 Resolved Issues

Derived Fields

Corrected an issue that prevented attributes from being converted from text to time (creating a derived field) within a fused data source.

24.1.5 Resolved Issues

Scheduled Reports

Corrected an issue that prevented simultaneous scheduled report generation in a multi-tenant environment.

24.1.4 Resolved Issues

None.

24.1.3 Resolved Issues

SAML SSO Integration

Corrected an issue that prevented use of Okta IdP to authenticate through SAML SSO.

Null Values

Resolved an issue with sources containing null values that prevented use in visuals and dashboards.

World Maps Filtering

You can now apply filters to the World Maps visual using the context menu.

24.1.2 Resolved Issues

List Filter Selections

When you select multiple values in a list filter, Composer includes a scrollbar to allow you to scroll among your selections as needed.

24.1.1 Resolved Issues

Ruler Log Scale Function

Corrected an issue that returned incorrect results from the log scale function if negative values or zero values were included.

Exporting Raw Data

Corrected an issue that prevented the export of visual data in visuals where the option Show Distinct Rows is used.

24.1 Resolved Issues

None.

Deprecated Features

Title Description

24.1.12 Deprecated Features

None.

24.1.11 Deprecated Features

None.

24.1.10 Deprecated Features

None.

24.1.9 Deprecated Features

None.

24.1.8 Deprecated Features

None.

24.1.7 Deprecated Features

None.

24.1.6 Deprecated Features

None.

24.1.5 Deprecated Features

None.

24.1.4 Deprecated Features

None.

24.1.3 Deprecated Features

None.

24.1.2 Deprecated Features

None.

24.1.1 Deprecated Features

None.

24.1 Deprecated Features

None.

 

Removed Features

Title Description

24.1.12 Removed Features

None.

24.1.11 Removed Features

None.

24.1.10 Removed Features

None.

24.1.9 Removed Features

None.

24.1.8 Removed Features

None.

24.1.7 Removed Features

None.

24.1.6 Removed Features

None.

24.1.5 Removed Features

None.

24.1.4 Removed Features

None.

24.1.3 Removed Features

None.

24.1.2 Removed Features

None.

24.1.1 Removed Features

None.

24.1 Removed Features

None.

 

Known Issues

Affected Releases Description

Composer 24.1 and later

None.

Related articles

Comments

0 comments

Please sign in to leave a comment.