beqom v10 HF34 - 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 27th, 2021
Fix version: 10 - 42320 - 10.0.373 - BeqomApp.Gateway_10_42825 - BeqomApp.WebApp_10_42917
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| 34613 | Back-End: Kernel Stored Procedure Synchronization Issue The following issue was reported on the database side of the application: a missing delete operation was causing the Kernel_SP_Admin_Synchronize stored procedure used to synchronize views to fail. The issue has been corrected by adding to the stored procedure the missing statement which is linked to the k_user_grid_field_view table. Impact area: Application back-end | ||
| 35743 | : Rules Component Search Bar Incorrect Behavior The following incorrect behavior was reported in the : when users entered a value in the search bar, if they closed and opened the component side panel, sometimes the result of the search was not displayed. The issue has been corrected; now the search bar is working as expected and the searched items are correctly displayed. Impact area: Rules > Search bar item display | ||
| 36184 | Advanced Analytics: Report Data Source Display and Name Modification Issues The following issues were reported in the beqom Admin Portal: when opening the properties of an Advanced Analytics report, the name of its datasource was not displayed in the "Data Source" field as expected. Furthermore, when the name of the report was modified, an error message was returned by the application when attempting to access the report. The issues have been corrected; now Advanced Analytics report datasources are displayed as expected in the report properties and users no longer experience an error message after opening a report which name was previously modified. Impact area: Analysis > Advanced Analytics report | ||
| 36295 | : Cannot Access User Component if Home Page is Disabled The following issue was reported in the beqom Web Application: when the access to the was disabled for a given profile, it occurred that when the user attempted to open the , he was redirected to the predefined default page instead. Investigations revealed that the Home and User components shared the same component rights which was causing the issue. The issue has been corrected; now the can be correctly accessed if the Home page is disabled. Impact area: UserSettings > Component access | ||
| 37850 | Admin Portal: Cannot Use Multiple Application Tabs The following incorrect behavior was reported in the beqom Admin Portal: when users were working in the application, if they attempted to open the application in another tab in their Web browser, they were not able to use the first tab because an error was encountered by the application. After investigation, it was revealed the issue occurred because of an incorrect behavior of the csrfttoken when a new tab of the application was opened. The issue has been corrected; now users are able to use multiple application tabs in their Web browser at the same time. Impact area: Application usability | ||
| 37953 | beqom Cookie Policy Display Issue on Internet Explorer When logging in the beqom application for the first time using with the Internet Explorer Web browser, the cookie policy acknowledgment page was not displayed as expected. Instead, a blank page with the Reject and Accept buttons was displayed. The issue has been corrected; now the cookie policy acknowledgment page is properly displayed when connecting to the application for the first time. Impact area: beqom cookie policy page display | ||
| 38010 | Cannot Reject the beqom Cookie Policy Users logging in the application for the first were not able to reject the beqom cookie policy because the Reject button located at the bottom of the acknowledgment page was not working. The issue has been corrected; the Reject button located at the bottom of the cookie policy acknowledgment page is now working as expected. Impact area: beqom cookie policy | ||
| 38271 | Admin Portal: Missing Localization in Data Grid Source Export Message When users with the correct permissions granted to their profile attempted to export a data grid source via DATA > Administration > Grid Export , it was noticed that in the title of the information window, the localization key was displayed instead of the correct label. The issue occurred because the localization method was not applied to this specific field. The issue has been corrected; now the correct label is displayed in the data grid source export information message. Impact area: Data > Data grid source export message | ||
| 38481 | Back-End: Maximum Simultaneous Request Threads Increase for all Services In order to avoid Redis server timeouts, the initial maximum of simultaneous request threads handled by all the services in beqom has been increased. Impact area: Application back-end | ||
| 38543 | Admin Portal: Cannot Switch Profile in Data Grid Object Security Configuration When admin users attempted to apply an object security assignment to data grids via DATA > Administration > Grid Editor > Security , when selecting "Object Security" in the view type field and clicking the Add button, the application returned an error when a new profile was selected in the "Profile" drop-down list and the users related to this profile were not displayed as expected. The issue has been corrected; now users can properly switch between profile when adding an object security view to a data grid. Impact area: Data > Object security configuration | ||
| 38552 | : Cannot Upload a Profile Picture When users attempted to upload a profile picture for the first time in the beqom , after they selected a picture with the correct format, the picture was not uploaded as expected. The issue has been corrected and now users can properly upload a profile picture for the first time in the beqom . Impact area: UserSettings > Profile picture upload | ||
| 38562 | Back-End: SQL Injection Mechanism Error It was reported that the mechanism protecting against SQL injection was throwing an internal server error when only one keyword ("SELECT", "ALTER", "CREATE", "DELETE", etc.) was used as a request parameter. The issue was corrected by fixing a bug in the code and now the error is no longer encountered. Impact area: Application back-end | ||