5.27.2.4

*Product Name: QDMS Version Information: 5.27.2.4*

1. Improvements

Document Management Module

187546-DR20528 - When the ‘lblREV_TALEPLERI’ label in the language settings is marked as mandatory, selecting a request becomes mandatory during the revision stage. A warning message appears if no selection is made.
192973-DR21300 - The ‘307-General webAPI address’ parameter has been added to BSID to enable the use of the Webdav feature without a mobile app (The webAPI address required for Webdav and the online editor is retrieved from the value of this parameter). The value of parameter 307 is derived from parameter 107, thereby ensuring the Webdav feature operates correctly. The Webdav feature functions even if parameter 107 is left blank. However, if parameter 307 is left blank, the Webdav feature does not function.
193744 - When the ‘423-Should the cover page be printed in an uncontrolled print job?’ parameter is set to ‘Yes’ and a page range is used in both controlled and uncontrolled copies, the cover file is prevented from being downloaded. However, if the user does not enter a page range, it continues to function as before.

Risk Management Module

191577-DR21173 - Performance optimisation work was carried out on the form-based report.
193807-DR21387 - Performance optimisation work was carried out on the general risk list page.

Field Inspection Management Module

194488-DR21465 - Option-based scoring and support for Option4/Option5 have been added to the field inspection question transfer template (if lblOption4/lblOption5 are defined in the language settings). During template download, the SCORE column was removed and the POSITIVE_ANSWER_SCORE, NEGATIVE_ANSWER_SCORE, and NEUTRAL_ANSWER_SCORE columns were added. If Option4/Option5 is used, the dynamic addition of the OPTION4_ANSWER, OPTION4_ANSWER_SCORE, OPTION5_ANSWER, and OPTION5_ANSWER_SCORE columns has been enabled.

Document Management Module

192080-DR21195 - The issue where an email was sent twice if the user who initiated the document cancellation process was also listed in the distribution matrix has been resolved.
191323-DR21001 - When the ‘124-Should the approval matrix proceed on a role-based basis?’ parameter is actively used, and the position listed in the document’s approval matrix is vacated due to the incumbent leaving the organisation, the warning ‘The approval matrix contains inactive staff’ is displayed.
192079-DR21220 - The issue where the "GetDocumentsByFolderAndSubFolders" method would fail when used on a folder without subfolders has been resolved.
192081-DR21196 - For documents originating from a folder, the review period information now appears in the ‘Document Summary List’ and ‘Review List’ as specified in the folder settings.

Corrective and Preventive Actions Module

192402-DR21254 - When the parameter ‘Should the section manager responsible for the non-conformity be the Team Leader?’ is set to ‘Yes’, the Team Leader is now assigned when a section is selected via the mobile app.
193987-DR21417 - The issue where the language-specific version of the transaction source data was not displayed when using a custom email in the defect opening email and the relevant tag was used to retrieve the transaction source information has been resolved, ensuring it is now printed in English.

Audit Activities Module

192752-DR21283 - When attempting to update the options for a question used in an active audit, the warning message “The options for this question are currently in use in active audits. Please use the ‘Revise’ function” is now displayed. When the question is revised, the previous version is displayed in open audits, and the audit can be closed without an error.
192079-DR21316 - When the Audit Findings Report is exported to Excel, the issue where tag information was not replaced in records without an open CAPA in the first data row has been resolved. Consequently, for findings records without an open CAPA, the CAPA columns now appear blank, whilst for findings records with an open CAPA, the CAPA data is displayed as hyperlinks.

Customer Complaints Module

193181-DR21319 - The functionality of the DEGERLENDIRME_TARIH tag, used for the assessment date in individual reports within customer complaints, has been restored.
193353-DR21216 - In the Customer Complaints Module, when the ‘Action’ and ‘Root Cause’ parameters are set to ‘No’, the ‘Open Action’ and ‘Progress’ buttons are no longer displayed during the record closure process.

Equipment Management Module

192083-DR21183 - A validation check has been implemented for the new record and update functions regarding the parametric fields added via the language settings for use on the ‘Device Identification’ page.

Survey Management Module

192968-DR21291 - On the external participant selection and external participant definition pages, filtering has been enabled based on the parametric fields added via the language settings.

IT Asset Risk Assessment Module

193591-DR21351 - When the ‘Risk Source’ field defined in the asset definition within the Risk module is modified via a revision, this change is now displayed on the revision change page opened via the ‘Revision Change’ button.

FMEA Module

194136-DR21432 - In the English version, the language equivalents of action titles now appear in the action creation pop-up during the optimisation step. Following the publication of the FMEA, the dates of action items are now displayed correctly, ensuring that the action progresses as planned.

Supplier Evaluation Module

192403-DR21248 - In the Supplier Evaluation module, when multiple question lists are added via survey templates and different weights are assigned to these lists, the survey score generated when the survey is published and completed by the user is now calculated based on the weight values specified in the survey templates.

194494 - An XSS vulnerability in the “Code=” field on the Device Management System > Transaction Execution > Device Information page has been resolved.
194495 - The issue with the warning message displayed on the user login screen and in sections representing the user object, which was showing the same warning message regardless of whether an account existed or not, has been resolved.