beqom v10 HF35 -FEATURE PACK - 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: February 10th, 2021
Fix version: 10 - 42415 - 10.0.392 - BeqomApp.Gateway_10_43647 - BeqomApp.WebApp_10_43655
| Type | Issue key | Description | |
|---|---|---|---|
| Zendesk | Jira | ||
| 33115 | : Syntax Issue in Single-Answer Form Block The following incorrect behavior was reported in the beqom : when users created a single-answer block in a form, if they added an option to this block containing the ":" character in the edit section, it happened that label was not correct in preview mode and also when opening the form as an attached document. The issue has been corrected by always replacing the ":" character with the character ">" and now the labels are correctly displayed. Impact area: Forms > Single-answer form block | ||
| 37065 | : Incorrect Document Date When users created a document in the beqom Admin Portal to which the scheduled date was set on a past date and was added to the document queue, a discrepancy was noticed in the beqom . Indeed the application displayed the start date instead of the creation date of the document. The issue has been corrected; documents are now displayed with the correct date in the beqom . Impact area: Notifications component > Document date display | ||
| 38207 | : "Show" and "Export" buttons in Standard Reports Display Improvement In order to offer a better user experience when working with standard reports in the in the beqom , the Show button and the Export button (when configured) are now located closer to the first row of the filter panel. Impact area: Analysis > Show and Export buttons in standard reports display | ||
| 38483 | Advanced Analytics: API Security and Code Quality Improvements Major enhancements have been performed in order to improve the code quality and security when using Advanced Analytics APIs in the beqom applications. Impact area: Advanced Analytics APIs | ||
| 38634 | : Individual Planner Improvements As of this Hotfix package, the beqom application has been updated with several major improvements related to the and the : Admin users can now, from the , create comp rounds, comp trees and comp elements, manage individual rights to comp elements using profile-specific permissions, and fine-tune comp element eligibility. These improvements enable beqom administrators to manage individual planner availability and edition rights with a very fine granularity.; The overall functionality of the has been reworked. Most notably, it is no longer possible to create comp packages from the , since all the round configuration and management operations are now performed in the .; Numerous new features have been added to the , including, but not limited to: effective date for comp elements, comparison with previous comp rounds, comp round anchoring, redirection from the individual planner to the original process, etc. This is an note/information message. The full function of the and of the individual planner will be documented in the beqom Online Help, along with a number of FAQ documents detailing the method to enable the in the beqom application and to ensure synchronization of the data between the process and the . This is an note/information message. The individual planner is disabled by default. For more information, please contact beqom. Impact area: CompPlan > Comp round creation and configuration, Organization and Process > Individual com planner | ||
| 38689 | Admin Portal: Cannot Select Indicator Field Source When admin users attempted to create or edit a process indicator field via the process field editor in the , they were not able to select a source for this field because the drop-down list was empty. Moreover, an SQL error was reported on the back-end side of the application when using the source drop-down. After investigation, it was revealed that the issue was caused by the addition of a filter for the source drop-down performed during the previous SQL injection fix. The issue has been corrected; now admin users can properly select an indicator field source in the process field editor. Impact area: Design > Indicator field source display | ||
| 38704 | Mobile Application: Image Fetch Mechanism Security Improvement In order to improve the security of the beqom Mobile Application and following the new method to fetch images in beqom, the user and payee images displayed in the Mobile App are now fetched by providing images URLs in an API call. Impact area: Application security | ||
| 38823 | : Cannot Modify Form Block Title The following issue was noticed in the beqom when using the Google Chrome Web browser: users were not able to modify the title of blocks in forms because the "Title" field appeared as read-only and not as editable as expected. It was revealed that the issue was linked to the update of the last version of Google Chrome. The issue has been corrected; now users can modify the title of form blocks as expected when using the last version of Google Chrome. Impact area: Forms > Block title modification | ||
| 38900 | Mobile Application: Performance Issue when Fetching Personal Dashboards Data The following issue was reported when working with the beqom Mobile Application: when users accessed their personal dashboards, it took an unexpected amount of time to display the related data (between 30 and 40 seconds). The issue occurred when the data were fetched from data grids where security hierarchy was applied. Investigations revealed that the NHibernate queries used to fetch the data were causing the issue. The issue has been corrected by replacing the NHibernate queries by SQL queries which significantly reduced the data loading time. Impact area: Home component > Personal dashboard data loading | ||
| #38979/#39100 : Cannot Open PDF with Acrobat Reader The following issue was reported in the beqom : when a document to which a PDF was attached (with a size up to 256KB) was created in the beqom Admin Portal, if users downloaded the document from the and attempted to open the PDF with Acrobat Reader, an error informing that the file was corrupted was displayed. It was revealed that the issue happened because the size of the PDF was unexpectedly increased in the beqom . The issue has been corrected; now downloaded PDF with a size up to 256KB from the can be properly opened with Acrobat Reader. Impact area: Notifications > Open downloaded PDF with Acrobat Reader | |||