Logi Composer 6.0 Release Notes
The following enhancements and updates were made to Composer in version 6.0. See the following topics:
- Migration Considerations
- Rebranding Updates
- Derived Field Changes
- User Interface Changes
- What's Fixed?
- What's Deprecated?
Email email@example.com to purchase Composer.
With this release, you can no longer use
<hostname>:8080/zoomdata/api/version. This is no longer supported. Use
<hostname>:8080/composer/api/version instead. While Composer 5.9 supports multiple context paths, this release does not. In addition, the
server.multiple-context-path.secondary properties in the
zoomdata.properties file have been deprecated.
If your installation uses Kerberos, the default behavior for unauthenticated users has also changed. From a browser, unauthenticated users are now redirected to the Composer login page. For API calls, links in the format
<hostname>:8080/zoomdata/api/version now return an unauthorized 401 error. To resolve the error, use
Rebranding the product from Zoomdata to Composer continued in this release in the following specific areas:
- The Service Monitor was rebranded. See Composer v6 Service Monitor Overview.
- Error messages in the UI were rebranded.
- The word "chart" was changed to "visual," where appropriate, in the translation file used for internationalization.
You can now use the
NOW() function in a derived field definition to obtain the current date and time. However,
NOW() functionality is not enabled by default. To enable this functionality, you must set the
calculations.rle.new.function property in the
query-engine.properties file to
true and restart the query engine microservice. See Query Engine Properties and Time Functions.
The following changes were made to the user interface in this release:
The color of the Add Filter button on the Row Security dialog and on the Column Security dialog was adjusted to align with the color of other buttons in the UI (it is now blue) and the button was moved from the left side of the dialogs to the right. See Adding Row Security Definitions and Adding Column Security Definitions.
A row security filter can now be assigned to more than one Composer group. In past releases, it could only be assigned to one group. At least one group must be selected. See Adding Row Security Definitions.
If a user belongs to more than one group, each with separate row security filters for the same data source, an error message now appears when the user tries to view a dashboard using the data source. This occurs because of the row restriction conflicts set by the different groups to which the user belongs. This same error occurs if two separate row security filters are defined for the same group in a data source. (Note that if a single row security filter is defined for two groups and a user belongs to both groups, no error will occur because it is a single row security filter.) See Restricting Access to Data Using Row Security.
You can now use derived fields (row-level expressions) in row security filters. See Adding Row Security Definitions.
Color palette names can now be translated using the translation file. See Translating the Composer Interface.
When a dashboard is embedded in an application, its sidebar now becomes a pop-up dialog (instead of a sidebar) when it is opened. This removes the problem where the sidebar uses the visual space needed by the embedded dashboard.
The maximum length of dashboard and chart descriptions has increased from 255 characters to 750 characters.
The following problems were fixed in this release:
Connectors correctly start now when the
config-server.enabled=trueoption is set in the
edc.propertiesfile in an HA environment.
Improved security in enterprise data connectors.
The following platforms, software and features are no longer supported in this release.
server.multiple-context-path.secondaryproperties in the
zoomdata.propertiesfile have been deprecated. This release does not support multiple context paths.
You can no longer use