Skip to main content

5.25.0.6

Product Name: Ensemble Version Info: 5.25.0.6

1. Highlights / New Features

  • No New Features

2. Improvements

  • No Improvements

3.Fixes

  • 51358 – DR8396- While searching during the selection of the Organization Unit throughout the application, there was case sensitivity in the Turkish character. The problem has been fixed.

  • 51570 – DR8458- In System Definitions->Process Management->Controls screen, the control could be disabled in cases where the control also had a sub-control. With the development made, it was ensured that a control with a sub-control could not be disabled.

  • 52408 – DR8687- System Definitions->Process Management-> Process Step Types screen, the parameter "Cannot be associated with processes" has been hidden when BPMN type object selection is made.

  • 55081 – DR9071- While the process was in the approval flow, when the approver was changed, the approver did not change in the Reports->Process Reports->Processes Pending Approval report. The error has been fixed.

  • 54174 – DR8964- In the document module in the SubQDMS application, when the process was added to the document, a relationship such as default QDMS document was established. The error has been fixed.

  • 50346 – DR8192- System Definitions->Performance Management->Elements->Series screen in the indicator-measurement location relationship, a formula can be determined to receive data from different indicator data in data entry. The code of the indicators in this formula could be changed and passive. With the development made, these situations were prevented and a warning message was given that it was used in the formula.

  • 52483 – DR8698- System Definitions->Performance Management->Elements->The start date of the measurement location relationship in the indicator-measurement location relationship is after the start date of the related period case, the data entered was not on the screen of the approver. The error has been fixed.

  • 56184 – DR9198- System Definitions->System-System-System Parameters->Process Management screen, revision requests were going to the process owner when the revising user was selected in the "To Whom Revision Requests Go" parameter and the related process did not have a revising user. With the development made, it was ensured that when the selection specified in the parameter is empty in the process, a warning is given that it is empty and revision requests are not forwarded. In cases where there is more than one selection in the parameter, it has been ensured that revision requests are sent only to users who have a corresponding user in the process.

  • 51335 – DR8286- The problem of showing the risks added to the process step in the process detail and visual model only once in the process detail has been fixed.

  • 50834 – On the screens of the Process Management module where the listing is made, right-click on the column Options-Refresh feature from the menu was not working. The error has been fixed.

  • 51048 – When the "Use version management in processes" parameter on the System Definitions->System- >System Parameters->Process management screen was inactive, the approval, control, opinion, information matrices in the process details continued to appear. Related fields were removed with the development made.

  • 51059 – While the "Use cancellation request in processes" parameter on the System Definitions- >System->System Parameters->Process management screen was inactive, cancellation requests could be used in processes. The error has been fixed.

  • 51272 – When the cancellation request created by the processes was approved, the process owner was written in the warning message, even though it went to the users in the control and approval matrix for approval. The error has been fixed.

  • 51368 – Process visual models can be transferred from visio with the import button and related visio objects can be matched with Ensemble objects. After the transfer, the background colors of the process step objects did not change from the Process Management->Process Step Types screen. With the development made, the option "Use the background colors of the steps in the file" can be checked during the transfer. The problem was solved by transferring it.

  • 51488 – While the process is inactive, a selection can be made from the cancellation requests created. However, after the process was inactive, the information of the request was not included in the Passive Information->Passive Requests field in the process detail. The error has been fixed.

  • 51496 – When the process steps on the Process Management->Processes screen were edited, the mandatory field could be saved by leaving the process name blank. The error has been fixed.

  • 51863 – When the Revision Requests on the System Definitions->Tools->Personnel Task Transfer- >Process Management screen were activated, the requests listed included requests for the old version of the process and cancellation requests. The error has been fixed.

  • 51906 – When the value of a waste used in process steps was changed on the System Definitions- >Process Management->Wastes screen, the updated value appeared in the process step detail of the process, but the old value appeared on the waste icon. The error has been fixed.

  • 53836 – When the process owner was selected as the department, revision requests could not be completed on the application screen and the process appeared to be in progress. The error has been fixed.

  • 52416 – Reports->Process Reports->Process CAPA report included deleted, inactive and old version processes. The error has been fixed.

  • 52621 – While importing process step details with template from System Definitions->Tools->Process Step Detail Import screen, competencies could not be transferred. The error has been fixed.

  • 52635 – System Definitions->Tools->Process Step Detail The problem of transferring inputs as output and outputs as input type when transferring with template on Import screen has been fixed. Two separate sheets were created for input and output transfer in the template.

  • 52700 – The type changes made on the System Definitions->Process Management->Input Output screen were not reflected in the detail of the process and the process steps in the visual model of the process.

  • 52704 – When the unit of measurement of a resource used in processes was updated on the System Definitions->Process Management->Resources screen, it was not reflected in the process details. The error has been fixed.

  • 53836 – Implementation of revision requests for processes when the process owner is selected as the department screen, it appeared as incomplete and the process was in progress. The error has been fixed.

  • 55534 – While the "Use cancellation request in processes" parameter on the System Definitions->System- >System Parameters->Process management screen was inactive, the cancellation request button continued to appear in the processes. The error has been fixed.

  • 55542 – Operation could not be performed on the System Definitions->Process Management->Controls screen. The error has been fixed.

  • 60076 – System Definitions->System->System Parameters screen was not opening. The error has been fixed.

  • 60553 – System Definitions->Process Management->When searching on the Process Step Types screen, the problem of incorrect search in the letters i,İ,ı,I has been fixed.

  • 60576 – When an input-output type data was added to the process steps in the visual model of the processes, the data was displayed as output in the icon. With the development made, it was displayed as "input output".

  • 51480 - While creating a process from System Definitions->Process Management->Processes screen, the process was active when the "Status" parameter was passive. With the development made, when the status parameter is disabled, the relevant process is included in the list of inactive processes.

  • 37420 – Decimal entered with comma in series from System Definitions->Performance Management- >Data Entry screen data tooltipe was showing a dot. The error has been fixed.

  • 49718 – In System Definitions->Performance Management->Elements screen, data entry responsible can be selected from the indicator-measurement location screen of the related element. The related responsible person can be selected from active user, position and user groups. However, the change operations made with the "Change Data Entry Responsible" button were from the active user, position and department lists. With the development made, user group was brought instead of department.

  • 51078 – When we changed the parameter from the limit & range screen on the System Definitions- >Performance Management->Evaluation Methods->Series screen, this change was not reflected on the editing screen of the method. The error has been fixed.

  • 51136 – When transferring report card with template from System Definitions->Performance Management->Score Card screen, the message "template loaded successfully" was given when the report card symbol was not entered. With the development made, the error message was provided. The "Display Order" entered in the template was not reflected in the uploaded report card and appeared as 0. The error has been fixed.

  • 51144 – When defining a measurement location with a template on the System Definitions-Performance Management-Measurement Location screen, when the "Measurement location symbol" and "Measurement location name" are left blank in the template and uploaded It was giving the message "template loaded successfully". With the development made, a warning was provided for the fields left blank.

  • 51531 – On the indicator-based data entry screen, filtering could not be done according to the indicator measurement location owner and data entry responsible. The error has been fixed.

  • 55572 – On the screens of the Performance Management module, the Options-Refresh feature was not working from the menu that opens when right-clicking on the column. The error has been fixed.

  • 56042 – In System Definitions->Performance Management->Evaluation Methods, in the parameters on the "Periodic Limit & Intervals" and "Cumulative Limit & Intervals" screens in the series of the related method changes were not being saved. The error has been fixed.

  • 60330 – In the indicator based data entry screen, if the start date of the measurement location relationship is after the start date of the related period, the data is not visible. New data entry could not be done. The error has been fixed.

  • 52592 – The authorization control of the indicators added to the visual model of the processes is based on the authorizations of the indicator measurement location. not according to the indicator authorizations. The error has been fixed.

4. Breaking Changes

  • Ensemble version 5.25.0.6 and QDMS version 5.25.0.6 must be installed.
PDF Download