beqom v10 HF33 - 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: January 20th, 2021
Fix version: 10 - 42267 - 10.0.345 - BeqomApp.Gateway_10_42610 - BeqomApp.WebApp_10_42596
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| 34411 | Web Application: Cannot Delete all Rows in Data Grids The following issue was reported when working with data grids in the beqom Web Application: when users selected all the rows in a data grid, after they clicked Delete , only the rows displayed on the application screen were deleted and not the rows of the entire grid as expected. The issue has been corrected; now when all the rows of a data grid are selected and after clicking Delete , the selected rows are correctly delete> Row deletion | ||
| 37195 | Advanced Analytics: ElastiCube Dashboards with Filters Import Issue If users exported an Advanced Analytics dashboard with ElastiCube-type datasource to which filters were applied, when the dashboard was imported to another tenant, the API method used for the import was not correctly updating the filters datasources. The issue has been corrected; now the filters datasources are updated via the target tenant definition when importing the dashboard. Impact area: beqom Advanced Analytics > Dashboard with filters import | ||
| 37196 | Advanced Analytics: Live Dashboards Import Issue When users exported and imported an Advanced Analytics dashboard with Live-type datasource from a tenant to another, the dashboard was not displayed in the target tenant and the application returned an error message. The issue occurred because several key values from the data model were not updated for Live-type datasource dashboard during the import process. The issue has been corrected; now Advanced Analytics dashboards with Live-type datasource are correctly imported from a tenant to another. Impact area: beqom Advanced Analytics > Dashboard with Live-type datasource import | ||
| 37458 | Abnormal CPU Consumption by Object Service It was reported that no matter the number of instances, the object service was constantly consuming around 60% of the CPU. The issue has been corrected; now the object service is using an proportionate percentage of the CPU according to the number of instances in traffic. Impact area: None | ||
| 37472 | Mobile App: Users Cannot Access the Application The following issue was reported: certain users could not access the mobile app. Investigation of the problem revealed an issue related to user profiles, specifically when users switched profiles in the application. In this case, the application did not receive the information that the user had switched profiles and continued to behave as with the original profile. Another issue was discovered related to the switch session profile logic. Both issues have been corrected; access to the application is now possible as expected. Impact area: Mobile App > Application access | ||
| 37502 | Admin Portal: Cache Refresh Issue when Modifying Process Grid Column Name When users with admin rights modified the name of a process grid column via the in the beqom Admin Portal, the new column name was not updated in the grid setup preview neither in the related process grid. After investigations, it was discovered that the issue happened because of a cache refresh problem. The issue has been correctly; now the cache is properly refreshed when modifying process grids column properties. Impact area: Process and Design > Process grid column name update | ||
| 37507 | : Cannot Use Filter Search Bar When users attempted to use the filter search bar, the application returned the following error: "An error occurred. Please contact the administrator.". The issue has been corrected; now the filter search bar is working as expected. Impact area: Organization > Filter search bar | ||
| 37772 | Mobile App: KPI Details View Implementation As of this Hotfix package, a new view has been added to the Mobile App configuration in order to display the KPI details in personal dashboards. Impact area: Home component > KPI details view | ||
| 37775 | Mobile App: KPI Modifiers Implementation A new functionality has been implemented in the beqom Mobile Application: users are now able to use modifiers in order to simulate payout. The modifiers enable to have a more precise handling on KPI in personal dashboards. Impact area: Home component > Personal dashboards KPI | ||
| 37777 | Mobile App: KPI Kickers Implementation Following the implementation the new KPI details view on the Mobile App, the possibility to switch between different payout curves has been enabled by using kickers. Impact area: Home component > Personal dashboards KPI | ||
| 37782 | Mobile App: Enable KPI Details Display Following the implementation of the new KPI view, the possibility to display KPI details has been introduced. The KPI details are disabled by default. Impact area: Home component > KPI details display | ||
| 37783 | Mobile App: Enable KPI Types Display on Details Graph As of this Hotfix package, the display of all the KPI types supported in the beqom Mobile App is now available in the KPI details graph. The graph is adjusted according to the type of KPI to display (boolean type, currency type, numeric type, etc.) Impact area: Home component > KPI types display in details graph | ||
| 37888 | Admin Portal: Auto Generated Documents Edition Issue The following issue was reported in the beqom Admin Portal: when auto generated documents were created from reports, the padlock icons (located on the document icon in the "Communication Workbench" menu and in the document details) indicating that the documents could not be edited was not displayed. The documents were editable which was not correct because auto generated documents should always be in read-only mode. The issue has been corrected; now the padlock icons are correctly displayed for auto generated documents created from reports and their edition is always disabled. Impact area: InfoHub > Auto generated documents | ||
| 37996 | Admin Portal/ : Excel Import Issue with Process with Null Values When a process grid with a workflow and containing empty drop-down list fields was exported to Excel, first if values were added and immediately removed in two different lists the Excel file, and then in a second time random values were added again and saved, when the Excel file was imported back into the applications a message indicated that some rows of the grid were updated but the values were not displayed in the grid as expected. Investigation of the issue revealed that drop-down list fields containing "null" values were inserted twice in the k_m_values table and caused unique key violation error. The issue has been corrected; now when adding values to empty drop-down lists in Excel, the grid is correctly updated when importing the file back into the applications. Impact area: Process and Process > Excel import | ||
| 38215 | /Admin Portal: Conditional Formula Syntax Issue with Single Apostrophe The following incorrect behavior was reported in the beqom Admin Portal and in the : when users created a condition using a business object value containing a single apostrophe, the application returned an error. Investigations revealed that using a single apostrophe in the formula was causing an SQL syntax error. The issue has been corrected by always replacing the single apostrophe by a double apostrophe in the formula. Impact area: Rules and Populations in the beqom ProductVariant and Rules and Organization in the beqom Admin Portal > Formula syntax | ||
| 38217 | : Hierarchy Security Exceptions Issue The following issue was reported in the beqom : when a hierarchy security was created for a given user, if this secured hierarchy was applied to a process with permission exceptions configured for that user via > Administration > Process Security > Exceptions in the beqom Admin Portal, it happened that the permission exceptions were not applied in the beqom and no error messages was displayed. The issue has been corrected; now hierarchy security permission exceptions are correctly applied in the beqom . Impact area: Process > Hierarchy security exceptions | ||