Skip to main content

Synergy CSP 2025 R2 SP26 Release Notes

> Release Date: 01.06.2026

1. Improvements​

161991 - Completed the enhancement of the Process Recovery Tool enhancement that detects data-driven discrepancies in newly started flows or during the validation phase of ongoing flows.

The developed tool works independently of the project in the background and performs scanning operations in all ongoing flows. For newly started or ongoing flows, the rollback and restart mechanism works as follows:

  • For newly launched flows;

    • The existing flow request is deleted, and a new flow request is created with the same flow form and data. An information e-mail is sent to the approver/approver group "An inconsistency has been detected in the flow previously submitted for your approval, so it will be submitted for your approval again".

  • In ongoing streams;

    • The flow is reverted from the current approver/approver group to the previous approver/approver group. An information e-mail is sent to the approver(s) who are withdrawn from their approval, "An inconsistency was detected in the flow previously submitted for your approval, it was returned to the previous approver".
    • An information e-mail is sent to the approval/approver group to which the flow is returned, "An error was detected in the process you previously approved, so it has been submitted for your approval again".

In case of an error during the rollback/restart process, there is a retry mechanism so that the flow enters an infinite loop and is not processed repeatedly. If the flow submitted for approval again after rollback is progressing incorrectly, an incorrect transaction log is created for that flow. If an error is received in the same operation up to the retry count specified in the configuration, the relevant flow is prevented from rollback/restart again and the relevant flow is blocked so that it is not triggered.

The following parameters have been added to the system for the Recovery Tool:

  • Workflow.RecoverySettings.ExecutionInterval: Determines the working period of the Job on an hourly basis. It is not triggered automatically when a value of 0 is assigned. Requests can be manually sent to the relevant endpoint.
  • Workflow.RecoverySettings.RetryCountOnFailure: Specifies the number of retries for flows that received errors during restart/rollback when the job runs. It can take a value between 0 and 10.

194915 – Since the existing license valid for the use of electronic signatures and mobile signatures expired on June 1 and the use of free licenses by KamuSM was terminated, improvements have been made in accordance with the new license structure.

Customers who want to continue using electronic signatures and mobile signatures must purchase the relevant signature license through their sales managers. Once the license purchase process is complete, customers must transition to the 2025 R2 SP25 package. With this package, necessary verification configurations will be made for the secure and authorized use of the signature license. In addition, end users are required to install the current DSClient installation package suitable for their operating system.

The current DSClient package, prepared in accordance with the new license structure, includes only the functions required for signing operations. Thanks to the verification structure to be put into effect with the SP25 transition, electronic signature and mobile signature transactions will be carried out only through licensed and authorized customer environments.

In this context, transactions using electronic signatures or mobile signatures, such as login, signing through Document Management, and process approval, are secured by license and verification controls.

Electronic signature and mobile signature will not be used in environments where licenses are not purchased or necessary verification configurations are not completed.

197276 – The timeout behavior on GPTProvider has been improved in order to manage timeout scenarios that occur during intensive use in OCR operations performed through the artificial intelligence service in a more controlled manner.

The timeout period, which is defined on the GPT data source but does not have any validity, has been made valid after the edit. If the Timeout value is not defined, 90 seconds is applied by default.

With this improvement, it has been ensured that long-lasting requests are terminated more predictably in OCR operations performed through the artificial intelligence service and that resources are prevented from being unanswered for an unnecessary period of time.

197348 – Changing the user's default language has been prevented by ensuring that the interface language change in the account logged in by proxy is only valid for the active session in the browser.

197453 – In environments where Synergy - eBA integration is active, eBA screens can be opened by using the general search function in the web interface.

197464 – Added Disable Auto Open Flow History to flow features in IDE. When the feature is activated, after the flow approval process is performed, the screen where the flow is opened (dashboard/workflow management list) opens instead of the flow history. The default value of the property is set to false so as not to affect current usage.

197495 – When the form/document panel opened via the Redirect link is closed, the dashboard screen is opened.

196279 - Support for culture / default language has been added to the HR Transfer user transfer process.

When the CULTURE column is sent in the source data, this value is sent to the user's OSUSERS. DEFAULTCULTURE. Thus, the default language of newly created or updated users can be set via the HR transfer.

When the CULTURE column is not sent in the source data, the default language of the current user is retained and the transfer process continues without errors.

2. Fixes​

196245 – The cache problem that caused the authorization changes made in the security module to be reflected late in the user menus has been fixed.

When authorization changes are saved, the user menu cache is cleared along with the authorization cache. Thus, menu authorizations given or removed from the security screen are reflected correctly when the user refreshes the page, without the need for manual cache cleaning.

In addition, the cache cleaning process, which was missing in the new authorization group creation scenario, was added, ensuring that security changes are applied consistently throughout the system.

196978 – When the Position Group object is used in parallel flows, the root request cannot be closed even though the group approvals are completed, resulting in the flow not being completed.

With the arrangement made, the data of parallel flow requests is evaluated through the correct flow arm and the approval date information of the root request is updated correctly when the relevant Position Group step is completed. Thus, the situation that causes users to give consent again and again in the same step is prevented.

197324 – An index key has been added in the PROJECTFORMOBJECTS table to eliminate the timeout error that occurs during the form saving phase due to the IX_PROJECTFORMOBJECTS_ProjectId_FormId_PackageVersion_MinorVersion data density in the forms whose data is indexed.

189741 - In static datagrid, it has been enabled to add lines with client side code in Save on: Row Change mode.

194449 - Null items from the datasource are prevented from appearing in the list when Run At Server is active in ComboBox's dynamic datasource.

194479 - In the rule triggered by the server side event in the Rules Manager, the error that occurred in running the conditions added over the NAME value of the datagrid columns was fixed and the defined rule was run smoothly.

195790 – Added the Refresh button to reload the data source in Combobox, Tagbox, Treeselect objects in SmartView looking forms in Synergy mobile app and mobile browser.

196039 – IDE -> When the statistics of a flow are requested to be displayed in the Flow Manager, the value overflow error that occurs in the function where the time in the start-end date range of the flow is calculated in milliseconds has been fixed.

196051 – Fixed an issue that caused row selection to be reflected incorrectly in the interface in single selection mode in datagrids with the SelectionSettings feature enabled.

With the arrangement made, the selections made through the checkbox are updated correctly, and when a different line is selected, the previous line is deselected and the new selection is reflected correctly in the interface.

196460 – Although there is a valid value in the PanelSize parameter newly added to the CreateLink method in ServiceAPI and RestAPI, the problem of the panel size being opened statically when the created link is opened has been fixed.

193273 - SetUser, SetDepartment, SetGroup, SetPosition and SetProfession endpoints in RestAPI/ServiceAPI will return an error if there is a mandatory property for the relevant HR entity type and it is not included in the request body (or if properties are sent as empty blocks).

Property validation in the relevant endpoints works as follows:

  • null + insert → Validation works, the value of the mandatory properties must be entered.

  • null + update → Validation is not run for the updated record.

  • [] + required property var → Validation works, the value of the required properties needs to be entered.

  • [] + no required property → Property values are considered to be deleted, the property values present in the record are deleted.

  • Required validation is applied → a full list.