Synergy CSP 2025 R2 SP21 Release Notes

1. Improvements

189412 – Use Thousand Separator option has been added for labels with numeric values to chart objects. When the Label property in the Chart properties is selected as visible: true, the Use Thousand Separator option can be used according to the visible label type information (decimal, fixed point).

172576 – User, Position, Department, Title, User Group, Admin Key, Company, and Company ServiceAPI and RestAPI required for creating/editing administrator records functions were created.

187681 – FormatDateTimeOffset variable has been added in order to convert the date fields used in the e-mail contents to the desired format. Depending on this variable, date values can be generated according to different formats.

Description	Usage	Example
Datetime format	'{{ ProcessStartDate | FormatDateTimeOffset }}'	2026-03-22 14:30:00 +
Only date	'{{ ProcessStartDate | FormatDateTimeOffset: "date" }}'	2026-03-22
Only time	'{{ ProcessStartDate | FormatDateTimeOffset: "time" }}'	14:30:00
DatetimeOffset	'{{ ProcessStartDate | FormatDateTimeOffset: "datetimeoffset" }}'	2026-03-22T14:30:00+03:00
Custom format (e.g. dd.MM.yyyy)	'{{ ProcessStartDate | FormatDateTimeOffset: "dd.MM.yyyy" }}'	22.03.2026
Use with UTC offset	'{{ ProcessStartDate | FormatDateTimeOffset: "datetime", "+3" }}' - '{{ ProcessStartDate | FormatDateTimeOffset: "datetime", "-5" }}'	2026/03/22 17:30:00 - 2026/03/22 09:30:00
Timezone support	'{{ ProcessStartDate | FormatDateTimeOffset: "datetime", "Europe/Istanbul" }}'	2026/03/22 09:51:32
Custom format + offset combined	'{{ ProcessStartDate | FormatDateTimeOffset: "dd/MM/yyyy HH:mm", "+03:00" }}'	22/03/2026 17:30
Use of offset only without specifying the format	'{{ ProcessStartDate | FormatDateTimeOffset: "", "+03:00" }}'	03/22/2026 11:07:29 +03:00

2. Bug Fixes

187136 – The problem that the advanced authorizations given through the upper breakdown in the power of attorney and access keys created in the old versions were not reflected in the lower breakdowns with the transition to the new version has been fixed.

187889 – On the Task Management screen, only user-to-user or position-to-position assignment is provided. In addition, when the task transfer is performed, the workflow data in the flow is updated and the flow is reduced to the right user.

190609 – On the IDE side, the performance problem that caused the OpenProject request to take a long time was examined and it was determined that there was a problem caused by parameter sniffing in the query. For this reason, OPTION (RECOMPILE) has been added to the relevant query and an execution plan suitable for the parameter has been created in each run.

190833 – It has been ensured that the RelatedDocuments object in the form supports files with heic and heif extensions.

To upload files in this format, the category-based content compression feature must be enabled in the RD object.

When the feature is active:

• The file is automatically converted to jpeg
• Becomes viewable on DM
• OCR is done on the converted jpeg file
• Added a short loading indicator to manage delays due to file size

190685 – The problem of deleting the company relations of the user whose data is no longer coming from the relevant data source during the HR transfer phase but is defined in the system has been fixed.

190923 – The problem of not deleting the relevant flow form when the flow document deletion object is passed has been fixed.

In the examination, it was seen that the DELETEDBY and DELETEDAT fields were filled.

In case of making a transaction through a proxy, the problem has been fixed by seeing that the information of the user who performs the transaction by proxy is not written in the DELETEDELEGATEDBY column.

190886 – The problem experienced during approval in the approval steps with the timeout lever in the flow has been fixed.

>NOTE: The project with the error must be republished.'

190963 – The issue of the selected row not being selected in the datagrid where the selection settings feature is activated as single has been fixed.

191055 – Save mode: The value of the column set to auto increment in the static datagrid with Row Change is assigned correctly regardless of the number of records listed on the datagrid page.

191231 – When the ProductionModeExceptions: true configuration, which allows hiding the details of the error on the request, is active, it is displayed with a user-friendly general error message in the interface.

191281 – In the Schedule trigger properties in the IDE, placeholder is displayed for informational purposes in the cron expression field. A warning is displayed at the build time for the incorrectly defined cron expression.

191966 – The problem of not being able to close the open panel in the interface when the request waiting for a response from eBA drops to the timeout on the eBA screens opened in Synergy has been fixed.

191733 – Fixed an error in the GetConfiguration ServiceAPI function that is available depending on the IS_GETCONFIG_ENDPOINT_ENABLED environment variable.

191942 – The problem of taking the title of the flow variables created from the objects in the form in the process lists in Dashboard and Workflow Management from the object in the form instead of the title information in the flow variable has been fixed.

>NOTE: The project with the error must be republished.'

192103 – In the use of forms in the flow and variables fed from form objects, authorization control has been applied only to the relevant forms.

192408 – The problem that caused the schedule to stop in schedule tasks with the flow start action type has been fixed.

191653, 191151 – In case the artificial intelligence configuration is incorrect or incomplete, the error message shown on the artificial intelligence assistant panel has been provided with guiding content at the point of configuration.

190460 – Fixed an issue where changing the user's e-mail address in the Human Resources module deletes the user's last password change date.

In addition, the problem that if the password change date information is cleared from the database, the user is directed to change the password at the login stage has been fixed.

188105 – Value can be assigned to ongoing flow variables in flow continuation functions (SaveAndContinue, ContinueWorkflow, ContinueWorkflowWithDocument, etc.) in ServiceAPI and RestAPI.

191784 – Save mode: GetAutoIncrementValue function has been prepared for the correct assignment of the value of the column set as auto increment in the static datagrid with Row Change.

For columns with active auto increment feature, the correct id value is created by sending a request to this endpoint.

189845 – The Precision Enabled feature has been added to the label options to determine how the decimal values in the numerical data in the chart objects will be displayed on the data label.

• When Precision is active, the following fields are visible

• Precision

  • Rounding Mode

• The data label is shown on the chart according to the number of decimal digits entered in the Precision field.

• Precision: When 0, the decimal place is not shown.

When Enable Precision is passive, the numeric data is displayed as it is without any rounding.

191649 – The error of primary key column-induced flow not progressing in flow forms containing dynamic datagrids has been fixed.

190844 – The error that occurred after the draft form secret key value was created incorrectly in flow forms with the feature of saving as draft turned on and prevented the flow from being progressed has been fixed.

190704 – When the Save button is clicked in Application Explorer, the use of the add, close and save buttons on the screen is prevented until the saving process is completed.

190283 – Search feature in the authorization hierarchy on the power of attorney and access keys detail screens, It ensured that the data that met the criteria was only highlighted in the hiyearşi. Search with the development made feature only returns results that meet the criteria.

The selection behavior appropriate to the search results is determined when an authorization is selected from the top breakdown, It works as follows in order to prevent the election of powers that are not shown:

• If the result that meets the search criteria is included in both the top breakdown and the bottom breakdown, both the top breakdown and selection can be made from appropriate sub-breakdowns. When the selection made from the top breakdown is made Authorizations that are not shown in search results are also selected.
• When the result that matches the search criteria is only in the lower breakdown, the parent breakdown is only The hierarchy cannot be selected from the parent breakdown, as it will be listed to show it correctly. The checkbox in the top breakdown is hidden in this case.

186232 – Fixed a form lifecycle management issue that caused static datagrid data used in Save On: Row Change mode to appear blank on the first boot when the flow was started.

191014 – Fixed an issue in the rules manager where the StartsWith, EndsWith, and NotContains operators produce incorrect results in null or null scenarios.

190561 – Functional errors in the Schedule object during the recurring appointment creation and appointment deletion phase have been fixed.

190564 – In the Scheduler object in the form:

• With the all-day feature, it is possible to create an appointment covering the whole day
• Fixed an issue where description data was not saved
• Fixed the multiplexing problem in the calendar after appointment update
• Static columns required for dynamic data source use have been created
• Modal display in accordance with the interface language has been provided in serial editing and deletion operations

190605 – Fixed the issue where the new version message displayed when the project is republished when the scheduler appointment mode is open is behind the modal.

A description field has been added to the appointment detail.

191161 – The artificial intelligence service has been enabled to be active by default for new installations and transitions from the 2024 R1 version.

191156 – The name of Bimser artificial intelligence service has been updated to Bimser AION. The AI usage consent text, which the user must approve when using the artificial intelligence assistant for the first time, has been updated to include the new name of the service.