Skip to main content

5.24.2.5

Product Name: Ensemble Version Info: 5.24.2.5

1.Highlights / New Features​

  • No New Features

2.Improvements​

  • 36469 – DR3981- System Definitions-Performance Management-Element screen, when the element is copied, the privileges of the corresponding element are brought to the copied element.

  • 36466 – DR3799 - The information contained in the report card details opened from the report card tab did not show the accumulation method of the element. With the development made, it was ensured that the "Accumulation Method" column could be added with the "Column Selector" button on the "Display by Indicator" and "Classic View" screens.

  • 37162 – DR4035- Added "Data Entry Officers" and "Indicator Holders" columns to the "Indicators to Generate Action" and "Indicators to Generate DOF" tasks on the Pending Jobs screen.

  • 37161 – DR4150- Authorization control was provided in indicators added to process details and process steps. If the user concerned does not have authorization on the display, he is prevented from accessing the detail and the lighting that determines the indicator status is not visible.

  • 36261 – Version update for the gojs tool used by the Ensemble application for process drawing and modeling. In the current version gojs v2.2. 21 is used.

3.Fixes​

  • 37419 – DR4297- QDMS document can be added to process step objects used when creating a visual model of processes. The version number did not change in the processes added after the revision of the QDMS document. Related issue fixed. In the added processes, the current version number comes after the revision.

  • 36902 – DR4145- System Definitions-Process Management-Processes screen hierarchical and list view processes listed in the list view had case sensitivity. For example, when the process name "SYSTEM" was searched as "SYSTEM", the relevant process could not be found. The bug has been fixed.

  • 37064 – DR4176- There was case sensitivity when searching the process steps tab on the process details screen. For example, when the name of the process step that was "yearly" was searched as "YEARLY", the relevant process step could not be found. When searching the Job By column, the error message "Cannot read properties of null (reading me)" was received. Related bugs fixed.

  • 36406 – DR3960- The <@ProcessResponsiblesTable> tag attached to the process detail and the duties of these responsibles was working incorrectly. The relevant tag was canceled and new tags were developed for the intended use. In order to bring the names of the process responsibles (process team) attached to the process detail to the process card, the tags <@ProcessResponsibleResponsibleTable> (responsible person names), <@ProcessResponsibleAccountableTable>(accountable person names), <@ProcessResponsibleControllerTable>(controlling person names), <@ProcessResponsibleInformatedTable>(names of people to be informed) should be used. For the display of the activated features of the relevant responsible persons as yes / no The tags <@ProcessResponsibleResponsible>(responsible?), <@ProcessResponsibleAccountable>(accountable?), <@ProcessResponsibleController>(controlling?), <@ProcessResponsibleInformated>(will information be provided?) should be used. For example, the user of Bimser Solution had an accountable status of Active. If the process card is only required to write Bimser Solution, the <@ProcessResponsibleAccountableTable> tag, if the accountable status is desired to be shown as yes because it is active, the <@ProcessResponsibleController> tag should be used.

  • 36497 – DR3992- When creating a process visual model, the lane and the organizational unit of this lane can be selected. The selection mark of the selected organizational unit before development could not be removed. The bug has been fixed.

  • 36252 – DR3885- Risks defined on QDMS can be added to processes. Even if the user was authorized in the risks listed, not all of the QDMS defined risks came. The bug has been fixed.

  • 37840 – When adding risks defined in QDMS to processes, all risks were displayed in the hierarchical view, but risks were not included in the list view. The bug has been fixed.

  • 36112 – The system did not return an error message when the user who was not a module administrator entered more than one data with an expired data date on the new data entry screen when the parameter "H" was "H" on the System Definitions-System-System Parameters-Performance Management System screen. With the improvement made, it was ensured that the error message was displayed on the screen.

  • 37445 – When the "Show report card comments" parameter on the System Definitions-System-System Parameters-Performance Management System screen is active, comments can be added to the report cards opened from the report cards tab. On the commenting screen, there are description, comment and file fields. The wording of the comment from these fields did not appear in practice. The bug has been fixed with the improvement made.

  • 37439 – On the Reports-Performance Reports-Report Card Based Performance Report screen, there was a "Download General Information" button in the reporting area. Since there was no general sheet in the relevant report, excel was giving an error when opening. With the improvement made, the button has been removed.

  • 37888 – Processes have undergone an aspose license update for a license error when retrieving the process card.

  • 37444 – When creating a measurement location with a template on the System Definitions-Performance Management-Measurement Location screen, the template could not be loaded without filling in the owner field. The relevant field is not mandatory in practice. For this reason, the obligation to fill in the owner field when defining with the template has been removed.

4.Breaking Changes​

  • Ensemble version 5.24.2.5 and QDMS version 5.24.2.5 should be installed.