Skip to main content

5.25.0.1

Product Name: Ensemble Version Info: 5.25.0.1

1.Highlights / New Features​

  • 38915 – DR4433- New tags have been developed so that process approvers, approvers' positions and approval dates can be brought to the process card. In order for the relevant data to be used in the process card, the <@ProcessApproverList> tag must be written in the line and the tags <@ProcessApproverName> (approver users), <@ProcessApproverPosition> (positions of approvers), <@ProcessApproveDate>(approval dates) must be added to the bottom lines.

  • 41550 – DR5825- Developed a <@ReferenceProcessesMultiLine> tag to print processes associated with the process on the process card.

  • 38927 – DR4847- Added the parameter "What indicator information should be displayed in the scorecard tooltip?" to the System Definitions-System-System Parameters-Performance Management System screen to display the description and indicator name when hovering over the indicator name in the scorecard details. The corresponding parameter includes the legend description, the indicator name, the selections for both and none. "Indicator name: ..." if the legend name is selected, "Legend description: ..." if the legend description is selected , if both the name and the description are selected, it will be printed by scrolling to the bottom lines, and if none is selected, it will be printed so that no expression is printed. In order for the selections made in the parameter to be reflected in the report card detail, it is necessary to click on the recalculation button on the relevant screen.

  • 34562 – DR2419- The "Require document attachment at data entry" parameter on the System Definitions-System-System Parameters-Performance Management System screen makes it mandatory to add documents to the default series for data entry. In order to manage the obligation to add documents to different series, the "Make it mandatory to add documents" parameter has been added to the series screen of the data on the indicator-measurement location relationship screen. For example, if there is no document obligation for data entry in the target field, if the user wants to require the addition of documents on the basis of the indicator-measurement location, he must select the target on the series screen and activate the parameter "Make it mandatory to add documents".

2.Improvements​

  • 37698 – DR4270- Process Details-Process Steps screen automatically sequences the activities from the visual model. Improvements have been made to easily edit the sort numbers that are corrupted after the process steps added to the visual model or deleted from the model. In the related development, the "Sequence No" column was added to the process steps screen of the process detail, where the sequence numbers in the visual model are automatically printed. After deleting or adding, the relevant sequence number was triggered manually to correct the sort automatically. For example, a visual model of 100 steps has a 45th step. When the step is deleted, it is sufficient to edit the 46th step as 45 by coming to the relevant sequence number and automatically editing the sequence numbers of the other process step. Likewise, when a new process step is added to the visual model of 100 steps after 6.ad, it is sufficient to manually assign a sequence number to the new step that is added so that all other sequence numbers change.

  • 40735 – DR5177- Added "Revision Date" column to bring the revision date of processes to the Reports-Process Reports-Draft Processes Report.

  • 42598 – DR5985- Added "Job Step Description" column to Reports-Process Reports-Process Resource Report. The relevant field brings the explanations entered into the process steps in the visual model.

  • 30235 – DR937- System Definitions-Performance Management-Scorecard can define user-based authorization to the scorecards listed on the screen. The "Add to sub-scorecards" selection was introduced so that the powers added to the report card could be added to the sub-scorecards in the hierarchy without disturbing their authority.

  • 35141 – DR3205- System Definitions-Performance Management-Scorecard screen can establish an indicator scorecard relationship for the relevant scorecard. In order to be able to select all indicators while establishing this relationship, the "New Indicator-Report Card Relationship" button was added to the screen that opened when the "Relate with All Indicators" option was added.

  • 35976 – DR3749- Reports-Performance Reports-Indicator Status Report When exported, the serial values were not numerically visible and therefore could not be calculated on excel. With the development made, it was ensured that the target, actual, and deviation columns were brought as numerical fields.

  • 36465 – DR3806- When entering data, annotations are entered into the relevant periods and explanations can be displayed in the scorecard. In the show calculated by the formula, there was no feature of entering a description. With the development made, it was ensured that the indicators calculated by the formula could be annotated and the relevant explanation was shown in the report card.

  • 38923 – DR4620- Reports-Performance Reports-Indicator Realization Report view has been rearranged with reference to the performance report. A deviation field has been added to indicate the difference between actual and target data. In order to increase the readability of the existing data, it was ensured that the periodic data were displayed by merging the cells.

  • 34799 – Added parameter 152 "Definition to be used in ensemble display actions" to the DR2548- QDMS action module. When the parameter value is empty, the definition field of the action items that are opened is empty. If the parameter contains the tags <PERIOD> <INDICATOR> <DIMENSION>, the <PERIOD> tag prints the period of the corresponding indicator, the <INDICATOR> tag prints the corresponding indicator, and the <SIZE> tag prints the size of the corresponding indicator. Using the relevant tags, the action description field of the actions opened from the Ensemble indicator detail can be edited.

  • 39742 – DR4669- Improved to send e-mails of indicators with data entry date and data entry approval on any day of the month. For the relevant development, the parameters "Which days should be sent for Data Entry Approval Delays?" and "Which days should be sent for Indicators with Expired Data Entry Date?" on the System Definitions-System-System Parameters-Performance Management System screen should be filled in as "dx". For example, if mail is requested on the 26th day of the month, it should be written d26.

  • 42595 – The parameter "What indicator information should be displayed in the scorecard tooltip?" in the System Definitions-System-System Parameters-Indicators area has been moved to the System Definitions-System-System Parameters-Performance Management System screen.

  • 39727 – Users who are not module administrators can edit and delete permission groups from the System Definitions-Users-Permission groups screen. With the improvement made, the edit and delete buttons have been removed.

  • 42591 – Removed the "Indicator Status" column from the Reports-Performance Reports-Indicator Realization Report.

  • 43459 – On the Indicator Measurement Location relationship page, there is a parameter "Make it mandatory to add documents" in the series field of the relevant measurement location. In order to use the corresponding parameter, the "change view settings" parameter had to be activated first. With the improvement, it has been ensured that the "Make it mandatory to attach documents" parameter can be managed without any action in the view settings.

  • 40817 – Security requires users to accurately control their access authorizations and allows users to access only objects that are within their rights. In order to eliminate the vulnerabilities detected in the application, reliable verification and filtering of the data entered by users was ensured.

3.Fixes​

  • 40858 – DR5503- When the documents defined on the QDMS are revised, a revision request is created for the processes to which the relevant document is attached and an e-mail is forwarded. In this e-mail, the information that made the request appeared as the user defined in the system. The error was fixed by bringing "system" to the user field that forwarded the request.

  • 41027 – DR5547- Process requests were not sent to the user groups defined in the "Which user group should the process requests go to" parameter on the System Definitions-System-System Parameters-General screen. The bug has been fixed.

  • 41721 – DR5881 – In cases where the user selected as the process owner does not currently have a counterpart in the QDMS application, it gives the message "Your cancellation request has been successfully sent to the process owner". With the development, the warning message "The process cancellation request could not be sent because the Process Owner and/or the user who created the process is empty" was provided.

  • 41779 – DR5896- The user who sent the process review mails received their information from the "Who should send confirmation mails" parameter. With the improvement made, it was ensured that the sending user information was received from the "Opinion request mails from whom" parameter.

  • 38408 – DR4709- When the "TDA Integration" parameter on the System Definitions-System-System Parameters-General screen was activated, there was a result not found error on the process step. The error was fixed and the TDA data was restored.

  • 41030 – DR5615- The sequence number was displayed in the Process Analysis Report when the "Use alphanumeric sequence number in process step details" parameter was active on the System Definitions-System-System Parameters-General screen. While the error was being fixed, the alphanumeric sequence number was introduced.

  • 41236 – DR5719- The names of user groups added to the process authorization matrix in the process details and to the authorizations of the indicators on the Elements screen were not visible. The bug has been fixed.

  • 40691 – DR5396- Older versions of processes added to the risks defined in the QDMS implementation were also listed. This caused an error in the approval phase of the risk. The improvement ensured that older versions of the process were not listed on risk.

  • 42647 – When only "H" (author) data was entered and saved in the "Who to Go to Review Task" parameter on the System Definitions-System-System Parameters-General screen, the parameter was not saved and the parameter value appeared to be empty when the page was refreshed. The bug has been fixed.

  • 43050 – Reports-Process Reports-Process Analysis Report did not bring data. The bug has been fixed.

  • 31714 – The "View by indicator" screen of the report cards listed in the Report Cards tab sounded incorrect when exported. The bug has been fixed.

  • 36022 – While the "Send data added from the data entry template for approval?" parameter on the System Definitions-System-System Parameters-Performance Management System screen was inactive, the approval flow for the data entered with the template was started. The bug has been fixed.

  • 41590 – When defining the measurement location with a template from the System Descriptions-Performance Management System-Measurement Place screen, the English equivalent of the measurement location name could not be transferred. The bug has been fixed.

  • 41591 – The details of the processes listed in the processes area of the indicator details accessed from the indicators tab would not be opened. The bug has been fixed.

  • 42663 – The Results, Actions, Actions, Processes, Processes tabs of the indicator details accessed from the Indicators tab did not open. The bug has been fixed.

  • 39728 – When any permission group was deleted on the System Definitions-Users-Permission groups screen, the corresponding users still saw menus. The bug has been fixed.

  • 43069 – The details of the report cards listed in the Report Cards tab were not disclosed. Bug fixed

  • 43082 – When the Reports-Performance Reports-Indicator Authorization Report was exported, the data in the KPI column came in as only "no". The bug has been fixed.

  • 43084 – When making new definitions and arrangements on the System Definitions-Performance Management System-Element Type screen, the "Element template counter" could receive a negative value. With the improvement made, when the negative value is given, the warning "Element Template Counter cannot take a negative value, edit it and try again." was provided.

4.Breaking Changes​

  • Ensemble version 5.25.0.1 and QDMS version 5.25.0.1 must be installed.