Skip to main content

Synergy CSP 2025 R2 SP23 Release Notes

1. Improvements​

192211 – With the development made in the artificial intelligence service, it has been ensured that the documents brought to the artificial intelligence service through a project can be stored on a customer/environment basis.

In parallel with the development, necessary arrangements were made in the Synergy environment in order to analyze the documents brought to the artificial intelligence service by the artificial intelligence service and to create responses suitable for the document content.

As part of the development, the "Search Document Pool" option was added to the artificial intelligence assistant panel. When the option is active, the documents created for the customer/environment are analyzed while creating a response to the prompt entered.

To avoid confusion, the definition of the "Search in Documentation" option has also been changed to "Search in Synergy Guide".

> NOTE: The new feature works in harmony with the current "Search the Web" and "Search Synergy Manual" options. The options can be used simultaneously or independently of each other. According to the selection made, the analysis source is dynamically pulled.

194674 – The features defined in the Human Resources module can be associated with more than one entity (user, position, department, user group, title) independently of each other and their obligations can be managed separately.

195199 – In the integration of Synergy - eBA (6.4), it has been enabled that the user who logs in to Synergy with a power of attorney can also list and approve the pending jobs in eBA.

In order to be used, the useDelegationMode: true parameter must be added to the Web.eBAIntegration.Config parameter used for eBA integration in Synergy.

For example;

{
  "enabled": true,
  "configs": [
    {
      "name": "eBA 6.4",
      "version": "6.4",
      "url": "```<```eba-url```>```https://",
      "userName": "admin",
      "password": "```<```password```>```",
      "useDelegationMode": true
    }
  ]
}

> NOTE: This feature is only available for eBA 6.4 version, the feature is not supported in eBA 6.7.

195115 – When a form is open in the Synergy mobile application, the necessary event is added to open the previous screen when the navigation button back on the phone is clicked, and the relevant form is closed when the button is clicked.

194431 – Added Resolve Label Overlapping to PieChart and other Chart objects, which determines how data labels behave in the event of conflicts.

When the Label feature is active, this setting becomes visible and appropriate options are offered according to the chart type.

For PieChart: hide, none (default), shift
For other chart types: hide, none (default), stack

With this development, tag conflicts are managed in a more controlled and readable manner in data-intensive graphics.

194409 – The default log level in Logger and Instance system parameters has been enabled to work as information.

193648 – A rule with a broken condition/action relationship in the Rules Manager in the form is automatically corrected when the project is republished.

194341 – In endpoints such as SetUser, SetPosition, etc., which are added to the RestAPI and ServiceAPI layers, when the value is not assigned to the ImportStatus field or is left null, the value is assigned as 0 in the background.

194529 – Errors returned from HR endpoints in RestAPI and ServiceAPI are returned as meaningful error messages in response.

194300 – In the SetUser function in RestAPI/ServiceAPI, if the user password information is not sent or is left blank, it is assigned with a value of 0 in the background.

2. Bug Fixes​

195927 – The problem that caused the value of the Company property definition in the Human Resources module to be transferred as the company name instead of the company code during the HR transfer process has been fixed. The problem was caused by a fix made to SP22.

195764 – Save Mode: The problem in creating rows with code in the datagrid with Row Change has been fixed. As a result of development, the relevant request is triggered at the right time and the row is successfully created in the datagrid.

195483 – Precision value in Datagrid and NumberBox objects can be set as max 6.

195484 – Fixed an issue that caused group and position records to be incorrectly deactivated in some scenarios in the HR transfer process.

With the arrangements made:

MultiplePositionsEnable: false scenario; In cases where position columns are missing or incorrect in the HROrganization data source, all positions are prevented from being passive.

Group records that are not in the Temp data source are prevented from being automatically deactivated and their current status is preserved.

Improved the update scenario that caused group records to be incorrectly deactivated again during company transfer in the TransferCompanies: true scenario.

With this enhancement, it was ensured that the records in the specified scenarios during the HR transfer were updated correctly.

195062 – In case the Run request triggered by server side functions on the form receives an error, it is prevented from automatically re-running within the scope of the retry mechanism.

With this regulation, duplicate transactions and form records that may occur as a result of re-triggering Run requests that take a long time or receive errors are prevented.

194277 – After publishing a major version in the IDE, the problem of corrupting the content of the files in the assets directory in the project has been fixed.

194278 – Fixed a bug that prevented the interface from responding when the AI assistant panel was opened while a flow in the project was open in the IDE.

194279 – When a flow waiting for approval is advanced, the following error messages are displayed in accordance with the interface language when the relevant approver position/user is not active in the system.

  • John Doe is inactive
  • Software Specialist position is inactive

193317 – Flexibility has been provided for validation, which causes data not to be assigned to DataGrid columns using parameterized datasources in form saving operations via ServiceAPI and WorkflowAPI on the code side of the project.

In this context, the ignoreGridValidations parameter has been added to the form save methods.

By default, false is valid and the current validation behavior is preserved. When used as true, it allows data assignment by skipping validation in columns with parameterized datasources.

186439 – ServiceAPI and RestAPI functions required for creating/editing User, Position, Department, Title, User Group, Admin Key, Company and Company Admin records have been created.

194724 – In the Document Management module, the Expiry Date, Limit and Permission options in the document sharing function can be used independently of the file access type (Everyone with the Link, People in the Company, People with Current Access, Selected People).

Thus, document sharing criteria have been made determinable regardless of the type of sharing.

194726 – When a view is assigned to the Print button on the form, it is prevented from switching to the relevant view in the background during the form printing process. As a result of the development, the selected view is used in the printing process, but the relevant view is not opened in the interface.

194089 – In forms containing a schedule object, the content major error that occurs during the form saving phase depending on the size of the appointments defined in the relevant object has been fixed. With the regulation, not all appointments in the object are loaded at once, only the appointments belonging to the displayed date range are loaded.

194807 – Visual incompatibilities in the warning message displayed in case of interruption of the real-time connection service that provides inter-service communication in Synergy (stopping the environment, disconnecting the internet connection, etc.) have been fixed.

194182 – In cases where password renewing/setting is required after login (password expire or force change password), the incorrect redirection problem that occurs when the user's password reset screen is exited with the browser's back button has been fixed.

194421 – After the flow in a project is deleted and the relevant project is published as major, the error that occurred when transferring the ongoing approvals from the previous version to a different user/position from the Task Manager screen has been fixed, allowing the ongoing flow to be transferred smoothly.

194350 – The problem of the flow and standard forms opened by searching from the global search screen not being reflected in the Recents list has been fixed. In addition, the Superset and external link type menus opened from the search screen are also reflected in the Recents list.

194650 – Workflow Management -> The error "An error occurred while retrieving process data" that occurred as a result of filtering in the Request Date column in the Pending Jobs list has been fixed.

193894 – The features defined in the Human Resources module can be associated with more than one entity (user, position, department, user group, title) independently of each other. Fixed an issue where the feature was duplicated on the list screens when the feature was associated with more than one entity.

191666 – The features defined in the Human Resources module can be associated with more than one entity (user, position, department, user group, title) independently of each other.

190855 – The error that prevented the project from being opened has been fixed when opening encrypted projects in the IDE by entering a password.

194656 – The error that occurred during the restoration of a deleted project in the Project Manager in the IDE has been fixed and the project can be restored.

195936 – The skip validations option in the IDE is actively prevented from receiving errors due to datasources that are not executed in the relevant project during the project deployment phase.

194273 – The error that occurred during the login of the user created in the system with the SetUser function in RestAPI/ServiceAPI has been fixed.

194274 – In the SetUser endpoint in RestAPI/ServiceAPI, if the user's default culture information is sent blank, the current defined value is deleted.

194275 – The problem of not being able to set the user's Date of Birth, Start Date and Termination Date values with the SetUser function in RestAPI/ServiceAPI has been fixed.

193897 – In single process endpoints (SetUser, SetPosition, etc.) created in RestAPI/ServiceAPI, it has been ensured that properties that are mandatory but have a default value can be assigned with the default value if the value assignment is not made in the function.

193893 – In endpoints such as SetUser, SetPosition, etc. in RestAPI/ServiceAPI, it is prevented to assign the property value that is not included in the relevant entity in the request body.

194303 – When GPT Query defined in a project is run in the IDE, the problem of the GUID value of the relevant field returning as a result in the defined return field fields has been fixed.

190465 – In the Synergy mobile application, the problem that the value in the NumberBox field does not appear in the object if the header of the column is long in the modal opened during the add/edit phase in the datagrids in SmartView-looking forms has been fixed by fixing the width allocated to the header field. Long headings are scrolled to the bottom line and shown at the same width.