beqom v10 HF179 - 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: August 14th, 2024

Fix version: v10 - HF 179.1 - DB 10.0.951

Type	Issue key		Description
	Zendesk	Jira
		BQM-24545	Application Observability: Default Logging Interval Update The interval at which the OpenTelemetry package logs events was updated to an optimized value to guarantee that the logging process does not consume excessive resources.
		BQM-24558	Statement Generation Building Pipeline Token Update The building pipeline for the statement generation feature was upgraded to integrate a new token for the communication with the quality assessment tools used by beqom. This improvement guarantees that the code for the statement generation feature is up to the highest quality standards.
		BQM-24581	Application Quality Gates Failing The TCM application did not pass certain quality gates established to guarantee the quality of the code. Investigation revealed that the issue was related to a mismatch of linking parameter name between the application interface and the quality tool. The issue was corrected by changing the parameter name and making sure they match.
	107792		Advanced Analytics: Duplicate Username Displayed in the User List Following the release of the back-end fix for this issue in Hotfix 177, beqom is now releasing a fix for the front-end of the application regarding this issue. As a reminder, the issue was observed in Advanced Analytics, specifically, the users drop-down list was displaying duplicate names, which made it difficult to distinguish between users with the same name. The problem was addressed in the back-end by adding the email address to the API endpoint response to provide a unique identifier for each user in the drop-down list. This fix provides the front-end part that actually displays the email addresses in the drop-down list.
	109917		Admin Portal: Scheduler Not Processing Requests An issue where the Scheduler got stuck when attempting to establish communication with the database and therefore was not able to process any scheduled jobs. The problem was due to the fact that the Scheduler failed to retry queries, which caused the connection to the database to fail. To correct this problem, the AzureRetryPolicy was implemented on the Scheduler service, for an overall better reliability of the Scheduler.
			BQM24537 Web App: PDF Library Update for Statement Generation The PDF library that is used to generate the statements using the Statement Generation feature was updated for added performance and security.