(v24) Symphony 24.1 Release Notes

Symphony 24.1 Release Notes

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

• Beta Features in this Release

• Feature Enhancements

• API Updates

• Resolved Issues

• Deprecated Features

• Removed Features

• Changes in this Version

• Known Issues

Beta Features in This Release

This release of Symphony may contain some features and enhancements in a beta test state so you can try them out in a non-production environment. Assess how they work in your environment, or provide feedback to insightsoftware as part of a formal beta testing process.

Important: Do not use beta features in a production environment or on mission-critical systems.

Name	Beta Version	Description	Final Release Version
Logi AI	24.1	Logi Symphony introduces Logi AI, a comprehensive AI and Natural Language Generation (NLG) module designed to transform the way you analyze your data. Logi AI is a flexible AI platform that enables you to build and embed your own AI-powered chatbots directly into dashboards and visualizations in partnership with Flowise. Embedded chatbots help you elevate the user experience, making complex data analytics intuitive and effective for informed data-driven decisions. Adjust chatflows based on your use cases, domain policies, and security policies to ensure actionable insights are easily accessible and perfectly aligned with your strategic goals. Backup your chatflows manually. Four starter templates are available from insightsoftware in the Flowise market place. For more information, see Logi AI and Logi AI Solutions. Important: This feature is considered to be released in beta for your testing purposes. Workflows and features may change before a production-ready version is released.	N/A
Managed Dashboard Data Connections	23.4.1	You can now create data sources in Visual Data Discovery data cubes or data connectors. Establish a connection to an available project in Visual Data Discovery then use to create a data source. After you've created the source, use it to create a visual in the Visual Gallery or in a dashboard. See Add Data Discovery Data Store Connections and Define a Visual Data Discovery Source. Important: This feature is considered to be released in beta for your testing purposes. Workflows and features may change before a production-ready version is released.	N/A

Feature Enhancements

Title	Description
Logi Symphony Software As A Service	Logi Symphony is now available as a fully-hosted Software as a Service (SaaS) solution. This managed implementation allows you and your users to leverage the extensive capabilities of Symphony without the back-end upkeep of managing security, upgrades, and features. Designed to scale for your needs and provide a seamless onboarding experience, use Symphony directly, or as embedded components in your own environment. Contact your sales team to get started! For more information, see Logi Symphony - Software as a Service (SaaS) and Logi Symphony SaaS Solutions.
Logi Symphony For Visual Data Discovery	You can now deploy and use only the Visual Data Discovery module in Symphony. Use the capabilities of this module as an entire deployment, installed directly or hosted as an SaaS with insightsoftware. Users can use Symphony directly, access their data in an embedded environment, and belong to one or more tenants as needed. See Install Symphony - Kubernetes.
Groups Management	Groups management is now a streamlined experience in Symphony. Create groups in the Symphony interface, and make privilege changes to groups in each module as needed. You can also add users to multiple groups at user creation time. When you create, edit, and update groups, the changes are shared across all of your licensed modules in your environment, and within applicable tenants. System Administrators can manage all groups and users in groups. View all groups across all tenants by selecting Groups from the main menu: searchable tags for each group tell you which tenant is associated with each group. Tenant Admins can manage users and groups associated with the tenants they administer. View all groups in a tenant by selecting Groups from the main menu while you're working in that tenant. Switch between tenants as needed to view that tenant's groups. If you're a member of multiple tenant groups that use Visual Data Discovery, you can switch between tenants to see a list of the groups for each tenant. For more information, see Symphony User Groups and Create And Edit Symphony Groups.
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.
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, Symphony 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 Dashboards, Import Visual Gallery Visuals, and Import or Export Sources.
Lite Dashboard for Self-Service Environments	We've added a simplified lite dashboard to your Symphony environment for Data Discovery content. 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 SymphonyData Discovery 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.
Self Service Reporting Improvements	Report editing features in the Managed Reports module are now controlled by a set of Application Privileges. Enable or disable (allow or deny) as needed for users and groups to give you the flexibility to offer your users a simplified report editing experience. The new application privileges are: Report Advanced Dockable Windows, Report Advanced Toolbar Options, Report Data Visualizations, and Report Styles & Themes.
Multi-Tenancy Improvements	We've expanded and improved multi-tenancy in Symphony to make it easier to manage tenants, add users to multiple tenants, work with tenant and user content, and for users to navigate between tenants if they belong to multiple tenants. Add new users to multiple tenants at account creation time. Easily edit users, changing their tenant status, admin or system admin status, member of the Global User group, or content distributor. Users can switch easily between tenants from the main menu, and verify what tenant they are working in. The tenant a user is working in is always at the top of their tenant list and indicated with a check mark. The minimum length for a tenant name has been removed. Symphony only verifies that the tenant name is not empty. System admins are listed with an Admin tag in the Name column on the main Users landing page. Only Global Users can be system admins, and show a Global User tag in the Tenants column. Sources created in the Visual data discovery module are visible only in a tenant where it is created, and optionally to other tenants as assigned. For more information, see Multi-Tenancy in Symphony and Add New Users .
Embed Data Discovery Components in Managed DashboardsEmbed Data Discovery Components in Managed Dashboards	Present a comprehensive view of the information in your environment in one place, utilizing the full capabilities of Symphony. You can now include any data discovery object in your managed dashboards to bring all of your data into Symphony. Add existing dashboards or visuals as components to a managed dashboard, and edit the properties as you would for any component: adjust the main properties, the look, and the layout. You can additionally add a component by selecting the (new) option instead of existing content. This lets users to work with available data to create a visual or dashboard in a managed dashboard and see data in a different context. Select different interactivity settings for dashboard components as needed.
Data Cube Discovery Enhancements	When you create or edit a data cube using a manual select transform, you can now set a temporary limit for discovering data as you build and test. This temporary limit allows you to build and test your data cube, and still run it against the full data set when complete.

API Updates

API documentation is provided with your Symphony installation at this link: <symphony-URL>/discovery/swagger-ui.html.

Visual Data Discovery Module

Endpoint	Method	Description
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}/.

Managed Dashboards and Managed Reports Modules

Endpoint	Method	Description
None.

Resolved Issues

Symphony

Title	Description
None.

Visual Data Discovery Module

Title	Description
None.

Managed Dashboards and Managed Reports Modules

Description

Clicking or right-clicking a Data Cube transform and choosing Refresh will now update the element names based on the source data cube.

Fixed an issue that could prevent a job failure email from being sent and log an invalid session exception when configured to send it to the application maintainer.

Fixed an issue where setting the isDownloadLink URI parameter to false in a REST request to /Export/Result/ was no longer responded to with the correct headers to open the file directly in the browser.

Fixed an issue preventing some date/time token values from working as expected in a filter transform when using greater/less than operators, allowing you to choose whether to apply the upper or lower boundary value of the calculated token.

Fixed an issue that could cause grand total text to be missing the color assigned based on state conditions when exported to Excel.

Addressed custom total text not being applied to the grand total column when exporting to Excel.

Prevented unnecessary changes made automatically to table visualizations starting in version 23.4 when displaying indented row headers with totals disabled for hierarchies not being visualized, and addressed related issues such as no change when choosing indented row headers when using certain hierarchy totals settings.

Fixed an issue that caused formulas to stop calculating subsequent rows after the formula script encounters an error.

Fixed an error preventing a metric set file from being opened if its saved visualization included a template cell ID.

Fixed an issue that could prevent single sign-on using federated authentication from working when embedded in an iFrame on a page with a different origin/domain.

Fixed an issue that could prevent view parameters from remaining connected to a slicer comparison measure when adding new slicer hierarchies.

Fixed an issue that could cause numeric columns from Google BigQuery to be discovered as the incorrect type.

Specifying IsGlobal/isGlobal as true is no longer required when creating an account through the API on instances without multi-tenancy or without any tenants.

Deprecated Features

Symphony

Title	Description
None.

Visual Data Discovery Module

Title	Description
None.

Managed Dashboards and Managed Reports Modules

Title	Description
None.

Removed Features

Symphony

Title	Description
None.

Visual Data Discovery Module

Title	Description	Alternative
None.

Managed Dashboards and Managed Reports Modules

Title	Description	Alternative
None.

Changes in this Version

Managed Dashboards and Reports

Description

24.1 Changes in this Version

To update the default visualization saved in the underlying metric set based on the current visualization in a dashboard or other view, first click Visualization in the Data Analysis Panel and then click Update Metric Set.

When deploying on Kubernetes, the default value for dundas.bi.website.service.sessionAffinity has been changed from ClientIP to None if not set in your own YAML values.

The Unknown Member Caption for a hierarchy in the Data Analysis Panel can now easily be customized to be blank/empty.

When you need to re-upload a file when creating or editing a data connector, you no longer need to first save or close and re-open it.

The Microsoft SQL Server data provider uses improved functions for the datetime2 data type and for time dimensions and date trimming if available in newer SQL Server/Azure SQL versions.

When exporting to a DBIE file in Administration, a search box has been added for more easily locating and selecting project files.

When scheduling a notification for a report, you can now export to the Image and PowerPoint formats.

The Check Warnings button when editing a ragged hierarchy now checks for an invalid level depth value.

When upgrading an instance running on Kubernetes with an evaluation license, the license is now updated automatically to be valid for the new version.

Users belonging to multiple tenants can see the currently selected tenant and switch between them more easily using the Profile menu.

UI improvements have been made for exporting a DBIE file to better support accounts belonging to multiple tenants.

When importing a DBIE file containing accounts that also belong to a tenant not included and not already present, references to that tenant are now removed automatically rather than requiring a health check to be run afterward.

A new built-in Global Users group includes all accounts set as global rather than belonging to specific tenants on multi-tenant instances.

The styling of the Properties window has been updated to better differentiate between headings and navigable list items on a wider variety of displays.

Assign optional colors to your data cube transforms to help categorize and identify them.

The included version of jQuery has been updated to 3.7.1.

New report application privileges have been added that can be denied to certain users or groups to provide them with a simplified report design experience when not all functionality is required: Report Advanced Dockable Windows, Report Advanced Toolbar, Report Data Visualizations, and Report Styles and Themes.

Administrators can now set tenant-specific custom attribute values on accounts that belong to multiple tenants.

The search box in the Views, Data, and Business pages accessed from the main menu now provides results from all subfolders in the current project for the selected file type. Hover over a result's name to see its full location in a tooltip.

Expand All content in Logi Symphony to quickly return to previous files you had open including dashboards, reports, metric sets, data cubes, and more.

The message shown on Views, Data and Business pages when the selected folder on the left is empty has been improved.

The description and validation for the Gateway Hub URL configuration setting have been improved.

Tenant administrators can now manage custom attribute values for an account for the current tenant if the account also belongs to another tenant.

Manual Select transforms have a new option Element Discovery Execution Behavior to more quickly discover the elements returned by more complicated queries or larger results.

Log entries for containers running separate Python, export, and/or other microservices now contain the date in their timestamps.

Known Issues

Affected Releases	Description
Symphony 24.1 and later	None.