Skip to main content

Synergy CSP 2025 R2 SP22 Release Notes

1. Improvements​

193215 – After the user logs in to the Synergy mobile application, the processes performed in the background are divided into steps during the readiness of the webview running in the background. The stages consisting of 8 steps are as follows.

  • Reading login parameters: 1
  • Checking user session: 2
  • Launching the app: 3
  • Loading Webview components: 4
  • Reading deployagent information: 5
  • Deployagent-based projects are being taken: 6
  • Deployagents ready: 7
  • App ready to use: 8

193975 – In the language model selection area in the Synergy artificial intelligence chat panel, the first model in the LLM active in the Bimser AION service is selected by default.

2. Bug Fixes​

192085 – The UI error that occurs when the GPT Prompt step is requested to be displayed in the object tab of a flow in the Flow Manager in the IDE has been fixed and the step details can be viewed.

189560 – Fixed an issue where previously started processes for flows deleted from the project could not be listed and escalated in Workflow Management and Dashboard. With the arrangement made, tasks can be accessed even if the flow has been removed from the project.

In addition, errors caused by some flow variables not being reflected in the data source of the process while creating the process list have been eliminated, and consistency has been ensured in archive and process listing scenarios.

>'NOTE: Changes must be published in major order for stream deletions to work properly. In broadcasts made with the minor version, the processes of the deleted streams will not be accessible.'

190280 – In the document sharing function in the Document Management module, the date clearing feature in the relevant field has been disabled as the expiration date selection is mandatory.

190705 – The problem of the preview panel used for the images in the document viewer object in the form not being at the front of the screen has been fixed.

192342 – In forms with the Check-in/Check-out feature activated, when a form open in one user is opened by another user in the mobile application, the message that the form is open for another user is displayed on the screen. Since the form cannot be operated while the form is open for another user, action and flow buttons are not shown on the screen.

188516 – The problem of corruption of the form version information in the requests sent consecutively during the form create phase has been fixed.

With the arrangement made, version inconsistency was prevented by applying the lock mechanism for the relevant document in sequential flow initiation requests and it was ensured that the necessary data was loaded without errors during the creation process of the form.

189281 – Fixed an issue where previously started processes for flows deleted from the project could not be listed and advanced in Workflow Management and Dashboard. With the arrangement made, tasks can be accessed even if the flow has been removed from the project.

In addition, errors caused by some flow variables not being reflected in the data source of the process while creating the process list have been eliminated, and consistency has been ensured in archive and process listing scenarios.

>'NOTE: Changes must be published in major order for stream deletions to work properly. In broadcasts made with the minor version, the processes of the deleted streams will not be accessible.'

190440 – The issue of appointments in the calendar overflowing to other cells when changing the size of the form panels containing calendar objects has been fixed, and the appointment is marked correctly in the cells of the relevant time period in the calendar.

190756 – Errors that caused the same unique id values to repeat in cases where the same form is closed and reopened from the menu after starting the flow, or when the flow is triggered again with the same form data without closing the form, have been fixed.

Within the scope of the improvements made:

  • A situation where action buttons were reactivated during flow initiation, causing requests to be sent again, was prevented.
  • The cache problem that caused the previous form data to be included in the form when a closed form is reopened through the recently used or menu has been fixed.

191185 – The bug that caused the action buttons to be reactivated and more than one process to be started if the same form was reopened after the flow form was advanced has been fixed.

With the regulation made, the situation that causes the relevant buttons to remain active during the flow initiation process and as a result, a request to start the flow again is prevented and the triggering of actions that are not suitable for the current state of the form is prevented.

191734 – In environments with active Synergy - eBA integration, after the approval of the eBA flow opened within Synergy, the number of pending jobs on the Workflow Management -> Approvals screens on the dashboard was updated instantly.

192112 – The problem that the results of the search operation made in the lookup object and containing Turkish characters in the expression were not correctly reflected in the dropdown list opened on the object has been fixed.

192591 – Error Information column has been added to the notification e-mail sent to the users specified in the system for errors in the HR Transfer process in order to make the errors more understandable. The column contains the record data for which the error was received and the stage at which the error occurred, and the error message is included in the Error Message** column.

In the example below; For a new user to be added to the system, a department code that is not in the system is included in the data source. In the Error Information column, the registration number/name/at which stage the error was received is included, and in the Error Message column, the information about why the error occurred (the department could not be found in the system) is included.

  • Error Information

  • Step: User-Insert. Type: User. Process: Insert. Identifier: 11113. Display: John Doe. Summary: 'John Doe'.

  • Error Message

  • GetDepartmentId method department value not found(DepartmentCode=G4444)

192517 – When the flows cannot be listed due to an error that occurs during the listing of the flows waiting for approval, the exception message that occurs is returned as a response.

When an error occurs as a result of the request, a general message is returned in the interface as "An error occurred while receiving process data", while the message that caused the error is shown in the response of the relevant request.

192589 – Fixed an issue where the value of custom controllers created by the developer in the IDE was incorrectly null when called via REST datasource. With the arrangement made, it was ensured that the string and other types of values returned by the methods in the controller were correctly retrieved by the REST datasource.

192590 – After object name changes in form rules, the error that caused the rule structure to be corrupted and not to be saved has been fixed.

With the amendment, the replace operation, which caused the ID values of the conditions and actions in the rule to be updated incorrectly, was removed. Thus, when the object name is changed, the rule structure is preserved intact and can be saved without any problems.

In addition, necessary data corrections have been applied for incorrect rule definitions in previous versions.

>NOTE: If the specified error occurs in the 2024 R1 versions, it is necessary to switch to the 2025 R2 version.'

192627 – In the HR transfer process, the HumanResources.Transfer.UseTransaction parameter has been added in order to continue the transfer process by skipping the incorrect data in the data source or to protect the data integrity, and the transfer behavior has been revised as follows.

  • UseTransaction = true (default): The transfer process will not be initiated if there are incorrect/inconsistent records in the data source. All errors are collected by validating before the process and sent to the relevant users by e-mail. In cases where there are no incorrect records, the transfer process is carried out.

  • UseTransaction = false: Incorrect records in the data source are detected and sent to the relevant users by e-mail. The transfer process is carried out for error-free records.

192626 – In the HR Transfer process, unnecessary error logs in the transfer process have been prevented in case of data coming from the data source while the import status of the properties of user, department, position, title and user group assets is inactive.

192988 – Fixed the issue where the change made was not saved when using the Bring to front, Send to back, Show grid lines, Hide gridlines, Disable snapping, Snap to grid functions on the flow design screen in the IDE.

192987 – The problem experienced during the saving phase of the form has been fixed due to the fact that the controlType value of the form was not included in the archive form created in the IDE.

192986 – The issue of newly added items belonging to the selected project not being displayed in the selection field in the form/flow list on the menu addition screen has been fixed.

With the arrangement made, when the refresh button on the screen is clicked, the form and flow list is reloaded with up-to-date data and newly added items can be listed without the need to close and open the application explorer.

192982 – In the row editing process in the static datagrid, if the first column in the datagrid is PK, it is ensured that the focus is made on the first column that is editable from the next columns.

192980 – In the datagrid whose data is filled through the selection form, if a column marked as mandatory is passed as empty, a mandatory warning is displayed during the form saving/flow advancement phase.

193739 – In the datagrid whose data is added via the selection form, the relevant record is prevented from being transferred to the datagrid if there is no data in the relevant datasource for the columns marked as mandatory on the selection form. The error message contains information about which mandatory column does not have a value in the selections made.

For example; When you want to add a datagrid of a record with an empty EMAIL column in the user list in the selection list, an error message will be shown: Since the EMAIL column is empty, 1 row will not be transferred.

>INFORMATION: For columns that do not have data in the selection list but whose data will be assigned on the datagrid, the column should not be marked as mandatory in the selection list, it should be marked as mandatory directly on the datagrid column. In this case, a record can be added from the selection list, but a warning message will be shown when the form is requested to be saved.

193314 – The following fixes have been made for incompatibilities between the project files and the database records of the project during the project publishing phase in the IDE and for the problems that occur in accessing the project's files:

  • In case of an error during the project publishing process, version inconsistencies that may occur between Document Management (DM) and the database have been prevented. System integrity was preserved by automatically rolling back version folders created in incorrect publishing attempts.

  • In document management, the pagination problem that could cause missing or duplicate folders in scenarios with a high number of items (200+) has been fixed.

  • Environment variables have been improved for the port access (SocketException: Permission denied) error experienced by the DeployAgent while starting the application, providing a more stable startup process.

193316 – In the GPT datasource of the Info Extractor/Custom Prompt type in the IDE, it has been enabled to rename the fields created in the Return Fields field.

193366 – The problem that caused the flow to not be advanced when the flows started from old versions in the system and did not contain web notification data were tried to be advanced has been fixed.

193713 – The problem that caused the same panel to be opened more than once by clicking the toolbar buttons added to Datagrid and allowing the panel to be opened repeatedly has been fixed.

193716 – The problem of assigning data to form fields depending on the selection made from the lookup object has been fixed.

With the regulation, the data structure processed in Lookup selections has been made to include all the data of the selection. Thus, when the selection is made by modal or different methods, data assignment to the relevant fields takes place without any problems.

193782 – The problem that the line coloring process made with the code in the datagrid object in the form is not reflected in the interface has been fixed.

193889 – In the HR Transfer process, the error of duplicate records for company relations of the existing records in the system depending on the parameter values of HumanResources.Transfer.TransferCompanies and HumanResources.Transfer.MultiCompany has been fixed.

194276 – In the HR Transfer process, it was ensured that a company that comes from the data source and does not exist in the system is created correctly in the system with the company definition information.

194461 – Fixed a bug that caused the action buttons to be reactivated and more than one process to be started if the same form was reopened after the flow form was advanced.

With the regulation made, the situation that causes the relevant buttons to remain active during the flow initiation process and as a result, a request to start the flow again is prevented and the triggering of actions that are not suitable for the current state of the form is prevented.

193582 – In HR Transfer, if the properties of user, department, position, title and user group assets are not included in the data source even though the import status is active, the deletion of the existing data and the passive change of the import status value are prevented in order to prevent data loss.

187281 – In scenarios where the FlowGptPrompt object is used in the Decider type in the flow, the cast/convert error that occurs when converting the value returned from GPT to the GptDeciderResponse type when the subbreakdown of JSON is selected via SelectedPath has been fixed.

192377 – The issue of resetting the display expression and value expression values of the lookup object in the IDE has been fixed even though the datasource mode is closed without any changes after opening it.

192284 – Fixed an issue where the form could not be displayed in form preview mode in the IDE.

190525 – The bug in using raw body in Rest type queries in the IDE has been fixed.

193578 – In projects containing treelists in the IDE, the error that occurred in the artificial intelligence assistant due to the inability to transmit the data of the treelist object to the artificial intelligence service correctly has been fixed.

189924 – When the datasource type of the context menu in the form changes, the problem caused by the data of the old datasource type remaining in the form has been solved by clearing the data of the context menu.

189908 – Document comparison feature is disabled for files displayed in forms opened in SmartView view via the Synergy mobile app and mobile browser. Document comparison is not suitable for the screen structure of mobile devices.

193896 – The problem of rendering columns in static datagrid has been fixed.

191555 – The value cannot be null error that occurred in project build and deploy operations has been fixed.

191937 – The error experienced during the electronic signature signing process on the Linux system has been fixed.