beqom v10 HF112 - 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: September 7th, 2022
Fix version: v10 - 93045 - 10.0.759 - 112.4 - 92187
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| 64929 | Admin Portal: Cannot Select Recipient Population for Email Notification The following problem was reported in the of the beqom Admin Portal interface: when creating an email notification, it was sometimes impossible to select a population in the To field of the notification form and the application would crash. The problem was related to the number of populations available in the system. If the number was too high, the field could not handle the long list. To correct the issue, the To field has been modified in order to include pagination and search. Impact area: InfoHub > Communication Workbench > Notification > To field | ||
| 65385 | Web App: Report Path not Retained in the Side Menu after Collapsing it In the Web App interface of the beqom application, after opening a report in the , if the user collapsed the side menu to have more space on screen to view the report, and then expanded the side menu again, the path to the report (i.e. folder, and opened report) was not retained; all folders in the side menu were collapsed. The problem has been correct and the context is now retained when the side menu of the is collapsed. Impact area: Analysis > Side menu | ||
| 65694 | admin Portal: Unexpected Behavior when Reordering Indicator fields When attempting to reorder indicator fields for a process grid in the of the Admin Portal interface, the change in order was not applied as expected: the changes were applied to a different indicator. Investigation of the problem revealed that the issue occurred when several indicators were defined for a single grid. To correct the problem, the way the information is transmitted to the application back-end has been changed: now only field IDs are used for querying. Impact area: Design > Setup > Columns | ||
| 66021 | Web App: Incorrect Behavior of the UI when Adding Business Objects to Population Criteria When creating or editing a population in the of the Web App interface, placing the cursor in the criteria syntax and then adding a new business object to the query did not have the expected effect: the new business object was added to the end of the query instead of in the location of the cursor. The issue has been corrected; new business objects are not added in the location of the cursor. Impact area: Criteria definition in the Populations of Web App | ||
| 67223 | Application Back-End: RabbitMQ Event Handling The unitOfWork object is not initialized in the database in order to automatically handle RabbitMQ events. Impact area: Event handlers, such as team deletion, team update, etc. | ||
| 67283 | Application Back-End: Change in Migration Script for Population Sharing In order to make sure that permissions are properly handled when using the new Team Sharing Feature Flag, the migration script associated with the flag has been changed. Specifically, the check associated with the Copy permission has been removed from the script. RNService modification | ||
| 67489 | Advanced Analytics: Issue when Importing a Report into an Environment When migrating Advanced Analytics resources from one environment to another, the report UID was not retained from the source environment. This meant that a new dashboard was created every time an import was executed. In order to correct the issue, the system now checks at the time of import whether a dashboard with the same UID exists in the target environment. If there is no corresponding UID, a new dashboard is created; if the UID already exists, the existing dashboard is overwritten. Impact area: Migration of Advanced Analytics resources between environments | ||
| 68005 | Web App: Conditional Formatting not Applied when a Condition is Defined on Workflow Step When using the new conditional formatting feature, if a user attempted to defined a conditional formatting condition on the workflow step, the condition could be properly defined, but it was not applied to the grid. To correct the problem, additional checks were added for the "Workflow Step" column of process grid. Impact area: Conditional formatting in process grids | ||
| 68133 | Admin Portal: Process Grids not Visible for Certain Users The following issue was observed in the Admin Portal interface of the beqom application: when navigating to a process grid, certain users noticed that the grid was not visible whereas it should have been based on their permissions and hierarchy security. Investigation revealed that the issue occurred when the datetime format parameter was null in the user settings (in this case, start date and end date could not be defined). As a solution, the datetime format setting is set to "d/m/Y" by default if it is not configured for a specific user. Impact area: Date format in user settings | ||
| 68276 | Localization Update In order to make sure that the beqom application is properly localized in all supported languages, the rps_localization table has been updated with all latest translations. rps_localization | ||
| #68153/68534 Web App: Cannot Import Modified Excel Files When a user with the correct rights exported a process grid to Excel, modified some data (in this case in rows located after the first 25 rows) and attempted to import the file back into the application, the following error message was returned: "Insufficient permissions. Please contact your administrator". Investigations revealed that the problem occurred because of an issue in the Kernel_SP_Hierarchy_GetTreeContent_FlatListForOrganization stored procedure. The mentioned stored procedure has been corrected; now users can correctly import Excel files with modified data in rows located after the first 25 rows. DB: Updated Kernel_SP_Hierarchy_GetTreeContent_FlatListForOrganization stored procedure Impact area: Process > Excel import | |||
| In this Release Note | |||