beqom v10 HF122 - 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: November 30th, 2022
Fix version: v10 - 106769 - 10.0.784 - 122.6 - 104753
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| 49326 | Back-End: Update NextSession Cookie In order to prevent any errors when more than four application stacks are opened in the same Web browser, the application now generates a separated NextSession cookie per application stack and removes the cookie which has the least expiration time remaining before creating a new one. This fix will also prevent huge number of next session cookies. Impact area: Application back-end | ||
| 67039 | JWT Token Security Certain API methods returned the JWT token of the logged in user. In order to improve the security of the application, risky methods were removed from the application back-end. API: removed endpoints /api/SSO/Token , /api/SSO/GetUserSessions , /api/SSO/GetLastUserSession and /api/SSO/GetUserInfo from the Next service, and removed GetUserInfoAsync and GetUserSessionsAsync from RN Service Impact area: All application services | ||
| 67679 | Strengthen Pseudorandom Number Generator In order to improve the overall security of the beqom application, the source of entropy used to generate application secrets has been changed. Impact area: RN Service | ||
| 68243 | Admin Portal: Bulk Apply Feature Inoperative in Data Grids with Multiple Values Column When working in a data grid containing at least two pages and with a multiple selection column, if users applied a filter on one of the grid column, and then used the bulk feature to apply the same value to all the grid columns, the values of the multiple values column were not applied to all rows as expected. The issue has been corrected and now the bulk apply feature is correctly working for multiple values column in filtered data grids. Impact area: Data > Bulk feature on multiple values columns | ||
| 69723 | Admin Portal: Bulk Apply Issue The following issue was report in the Admin Portal interface of the beqom application: when using the bulk apply feature on a grid containing several pages, the bulk apply was not applied to all pages in the grid. Investigation revealed that the issue occurred when a filter was applied on drop-down list columns, due to an SQL query issue. The problem has been corrected and the bulk apply is now properly applied. Impact area: Data > Bulk apply | ||
| 70052 | Migrate Environment Manager Service to ".Net Core 6" Framework As part of the general update of the beqom application regarding containerization and for security purposes, the Environment Manager service has been migrated to the ".Net Core 6" framework. Impact area: Environment Manager service | ||
| 70053 | Migrate Gateway Service to ".Net Core 6" Framework As part of the general update of the beqom application regarding containerization and for security purposes, the Gateway service has been migrated to the ".Net Core 6" framework. Impact area: None | ||
| 70267 | Web App/Admin Portal: Cannot Use " \ " in Population Condition When attempting to create a population with a condition containing the " \ ", both the Web Application and the Admin Portal interface would display an error and the population was not properly created, even though the application marked the condition as valid. The presence of the " \ "character was causing a javascript error, that has been corrected by replacing the character. Impact area: Populations > Population creation | ||
| 71296 | Migrate Authorization Service to ".Net Core 6" Framework As part of the general update of the beqom application regarding containerization and for security purposes, the Authorization service has been migrated to the ".Net Core 6" framework. Impact area: None | ||
| 71311 | Migrate Hub Service to ".Net Core 6" Framework As part of the general update of the beqom application regarding containerization and for security purposes, the Hub service has been migrated to the ".Net Core 6" framework. Impact area: None | ||
| 71312 | Migrate Object Service to ".Net Core 6" Framework As part of the general update of the beqom application regarding containerization and for security purposes, the Object service has been migrated to the ".Net Core 6" framework. Impact area: None | ||
| 71314 | Migrate Data Service to ".Net Core 6" Framework As part of the general update of the beqom application regarding containerization and for security purposes, the Data service has been migrated to the ".Net Core 6" framework. Impact area: None | ||
| 71315 | Migrate File Service to ".Net Core 6" Framework As part of the general update of the beqom application regarding containerization and for security purposes, the File service has been migrated to the ".Net Core 6" framework. Impact area: None | ||
| 71318 | Update React-Redux Library to Latest Version As of this hotfix package, the React-Redux JavaScript library which is used for building the user interface in the application has been updated to the latest version. Impact area: None | ||
| 71375 | Web App: Update "Mobile" Sub-Menu Label in "Admin" Component In the previous version of the beqom Web App, the sub-menu to access the Mobile Application settings management page from the was labeled Mobile which was confusing. In order to make it more clear for admin users, the label of that section has been updated to Configuration . DB: update to rps_localization table Impact area: Admin > Mobile sub-menu label modification | ||
| 71379 | Migrate Analytics Service to ".Net Core 6" Framework As part of the general update of the beqom application regarding containerization and for security purposes, the Analytics service has been migrated to the ".Net Core 6" framework. Impact area: None | ||
| 71381 | Web App: Advanced Analytics Data Model Creation and Migration Issue The following issue was reported in the beqom Web App: if a beqom tenant was configured with a connection string without a protocol in the server name in PMC, the creation and migration of Advanced Analytics was impacted. The issue has been corrected and now Advanced Analytics data models can be correctly created and migrated even if the protocol is not specified in the server name in PMC. Impact area: Admin > Advanced Analytics data model | ||
| 71599 | Web App: Incorrect Attached Documents Opened in Data Grids When a quick filter was applied to a data grid and the user opened an attached document, the opened document was not the correct attachment for the row. The problem was related to a refresh issue after application of the grid. Impact area: Data > Attached objects | ||
| 71615 | Back-End: Object Access Deletion API Method Inoperative The API method DELETE/api/objects/access/{id} returned an error and the access to the object was not revoked as expected. The issue has been corrected and the API now behaves as expected. Impact area: Object service | ||
| 71996 | Back-End: Session Timeout Not Working An issue occurred where the user session timeout defined in the of the Web Application interface was not properly applied when the application was actually used. The issue occurred when a large number of instances were active and sticky session was not used, any method call was causing the application to refresh the last activity date and thus never applying the session timeout. The issue has been corrected; the application now controls whether the user lands to a different instance and whether a last activity time exists. If there is a value, the application does not change it upon instance change. Impact area: User session timeout, login and profile switching | ||
| 72022 | Back-End: Improve Server Error Messages for SSRS Report Previously, when errors occurred when opening and viewing SSRS reports, the server would return very technical information that were hard for end-users to understand. This behavior has been improved and clear, user-friendly messages are now displayed when an error is encountered with SSRS reports. Impact area: Display of SSRS reports in the Home , the Process and the Analysis | ||
| 72239 | Formatting Issue When Using Custom Translation in Forms The following problem was reported in the of the Web Application: when building a form and inserting translation keys into the title of a form block using the " # " character, the text inserted using this method was displayed in a different color when viewing the form in preview or in the . The problem has been corrected by adjusting the CSS parameters related to text inserted using " # ". Impact area: Forms > Display of translations in forms | ||
| 72657 | Back-End: Adjustment to DB Structure In order to prevent duplicates to be created when performing changes into the database, the Catalog DB scripts have been removed from the tenant DB. API: RN Service > DB project Impact area: Application back-end | ||
| 72845 | Mobile App: Enable Components Display Management In order to improve the customization of the beqom Mobile App, the possibility to hide certain components of the application is now fully available. This is an attention message. This ticket is the second part of a two parts deployment phase. The first part has been deployed with ticket #69355 in the hotfix package 10 HF116 . Impact area: Application configuration | ||
| 72846 | Mobile App: Multiple Periods KPI Sorting Improvement As of this hotfix package, the following improvement has been introduced for multiple periods KPI in the Mobile App: when a parent KPI is configured with multiple child periods, the periods are now correctly sorted based on the configured period or sub period length and start date (week days, months, etc.). Impact area: Home > Multiple periods KPI | ||
| 73061 | Web App: Cannot Access Process Grids The following issue was reported in the beqom Web App: when users attempted to access the , the application unexpectedly returned the error "An error occurred when displayed the page. Please contact the administrator.". Investigation of the issue revealed that the previous upgrade of the Analytics service to the .Net Core 6 framework was responsible of the problem. The issue has been solved and now users can correctly access the as expected. Impact area: Access to Process | ||
| 73084 | Web App: SSRS Reports not Displayed The following issue was reported in the beqom application: when attempting to view an SSRS report from the or the , the report failed to load and the application displayed a blank page. The issue was corrected and SSRS reports can now be viewed normally. Impact area: SSRS report viewing in Web App | ||
| 73251 | Web App: Missing Localization for "Conditional Formatting in Data Grids" Feature Flag Localization was missing for the "Conditional Formatting in Data Grids" Feature Flag name and description and thus the application was displaying technical keys instead of the expected text. The issue has been corrected; the technical keys are no longer visible and the correct labels are displayed for the mentioned Feature Flag. DB: update to rps_localization table Impact area: Admin > Feature Flags page | ||
| #68376/#69238 Web App: Cannot Access Standard Reports Without Default Profile Assignment The following incorrect behavior was reported in the beqom Web App: if a user was not configured with a default profile, if he attempted to access any standard report from the , the page of the report was blank. The issue has been corrected and now users without a default profile assignment can normally access standard reports in the Web App. Impact area: Analysis > Access to standard reports | |||
| In this Release Note | |||