beqom v10 HF76 - Release notes

This article lists the new features that have been added to the platform, as well as the bugs that have been corrected in this release.

Deployment date: December 8th, 2021

Fix version: v10 - 58711 - 10.0.650 - 76.1 - 58660

Type	Issue key		Description
	Zendesk	Jira
	30234		Web App: Aggregated Fields Calculation Performance Issues When working in process grids configured with aggregations, performance issues were reported during the calculation of the aggregated fields which impacted the grid loading (sometimes taking up to 60 seconds). The performances when calculating aggregated fields and consequently the total summary row have been significantly improved by optimizing the calculation methods. Impact area: Process > Aggregated calculations and grid loading
	46720		Admin Portal: Conflict During Population Assignment The following issue was reported in the beqom Admin Portal: if users with the correct permissions assigned to their profile attempted to assign to a process a population containing payees already assigned to the current process population, the application returned an error. The issue has been corrected by adding a new parameter to detect already assigned payees and thus preventing any conflicts and errors during population assignments. DB: add parameter PRM_DisableRecreateStepOnPopulationAssignToProcess to the k_parameters table; API: update to RNService Impact area: Design > Population assignment
	50293		Web App: Forms Configuration Improvements As part of the requirements to enable forms in the beqom Mobile App, some improvements have been performed to forms configuration in the beqom . A new editability button has been added to the "Short Text" and "Long Text" form block types in order to enable a read-only mode. In order to be correctly available in the Mobile App, forms assigned to Mobile must always mention one value from a datasource to be used as reference. Catalog DB: add [ds].[bqm_object_datasource_filter] table, add uid_datasouce_attribute column in [obj].[bqm_object_attribute] table; API: new object API FormsService.IsFormReadonly Impact area: Forms > Read-only button for "Short Text" and "Long Text" block types
	51108		Mobile App: Enable New Payee Profile Section in "Home" and "Profile" Components A new possibility to display payees profile information has been implemented in the beqom Mobile Application. When correctly configured in the Web App and in the database, users are now able to open a specific section in personal dashboards and in the and access the configured information. As part of the delivery of this enhancement and in order to optimize the user experience, the "User Settings" component has been renamed to "Profile" and the "Preferences" tab to "Settings". Catalog DB: add [ds].[bqm_object_datasource_filter] table, add uid_datasouce_attribute column in [obj].[bqm_object_attribute] table, remove uid_aggregation_function column from [ds].[bqm_object_datasource_attribute] table and is_aggregated column from [ds].[bqm_object_datasource] table; Tenant DB: insert key to k_parameters with PRM_MobileProfilePayeeForm ; API: modify object service HTTPGET Form/{FormId}/data method to parse custom filters and modify the query filter mechanism to accept the custom parameters once they have been mapped from [ds].[bqm_object_datasource_filter] using their filter_names as an alias Impact area: Home and Profile > New payee profile section configuration and localization
	51633		Web App: Cannot Save Attached Forms with Empty Mandatory Fields The following incorrect behavior was reported in the beqom Web App: when a form was configured with mandatory fields ( Required button toggled) and attached to a process grid, after users accessed the form they were not able to save the modification if mandatory fields were not filled. The issue has been corrected; now users can correctly save a form even if some of the mandatory fields are empty. Impact area: Process > Forms with mandatory fields saving
	51861		Web App: Cannot Apply Filter on Boolean Columns in Process Grids An error was returned by the beqom Web App when users filtered a boolean column in process grids. The issue has been corrected; users can now correctly filter boolean columns in process grids. Impact area: Process > Filter on boolean columns
	52005		Mobile App: Invalid Notifications Content When users of the beqom Mobile Application opened any notifications via the , the text was displayed in invalid format. The issue has been corrected and now the notifications content is correctly displayed. Impact area: Notifications&Documents > Notifications content format
	52262		Admin Portal/Web App: Permission Conflict for Advanced Analytics Widgets Edition in Reports The following issue was reported when working in the beqom and the Admin Portal on Linux: non-admin users needed to have the "Manage" permission for Advanced Analytics Reports as well as any "Edit Reports" permission (granted in the Admin Portal via ADMIN > Functional Admin > Profiles > "Select a profile" > Analysis > Administration ) in order to edit widgets in any Advanced Analytics report in both applications, which was incorrect. The issue has been corrected; now users must only be granted one of the "Edit Reports" permission to edit widgets in Advanced Analytics reports in the beqom Admin Portal and only the "Manage" permission for Advanced Analytics Reports to edit widgets in the Web Application. Analytics API Impact area: Analysis2 (Admin Portal) and Analysis (Web App) > Advanced Analytics widget edition in reports
	52314		Web App: Enable Hotfix Version Verification Before Feature Flag Activation In the previous version of the application, the Hotfix version was not checked before a feature flag was activated which could lead to mismatch in the tenant configuration. From now on, the Hotfix version is always verified in the tenant configuration and the feature flag activation is enabled accordingly. Impact area: Admin > Feature flag activation
	52327		Web App: Incorrect Feature Flag Key Name Causes Application Crash The following problem was reported in the beqom : if a feature flag key name was created without respecting the naming convention (e.g. if the key started with "activation" or "release") in the feature flag management system, the API returned an error and caused the application to crash. The issue has been corrected; now the application will always be operative even if a feature flag key name is incorrect. Impact area: Application use
	52457		Localization Update The rps_localization table has been updated in order to make sure that the beqom application is fully localized. Update to the rps_localization table Impact area: None
	52484		Mobile App: Decimal Precision Inoperative in Percentage KPI Headers The following incorrect behavior was reported in the beqom Mobile App: when a decimal precision was configured for a percentage KPI, the decimal precision was applied to the percentage of the target but not to the KPI percentage value in the header. The issue has been corrected; now the decimal precision is applied, as expected, to the KPI percentage value in the header. Impact area: Home > Decimal precision in percentage KPI headers
			In this Release Note As part of the ongoing deployment of new features within the beqom application, the following ticket has been merged in this hotfix package: #51382.