Synergy CSP 2025 R2 SP16 Release Notes
1. Improvements
In the 186516 – Synergy – eBA integration, only the necessary data is retrieved from the GeteBAWorkFlowItems function, where pending jobs are brought, and unnecessary data is not returned.
186045 – RelatedDocuments object has been given a compression option to reduce the size of the added image files. The "Compression Enabled" option can be used on a category basis in the object.
187131 – The expired link in the interface has been renewed for the installation of the Synergy Capture service, which must be installed on the end user computer in order to add the files scanned in Document Management to the system. Installation can be done via the link on Docs.bimser.
187462 – When a component in the project is deleted (form/flow/datasource) in the developer interface, the cache is refreshed.
186547 – In the event that the same project is open on multiple users or screens, a centralized concurrency and version control model has been developed to prevent errors caused by the parallel operation of critical project processes such as deploy, import, project version, and so on.
In this context, the lock structure has been included in the system for project operations. When it is desired to initiate new conflicting processes while there is an ongoing process on the project or project version, instant and meaningful warning messages are shown to the relevant user in the interface and the transactions are blocked in a controlled manner.
With the new structure:
- Parallel processing on the same project/version is prevented
- Clarified the conflict rules between deploy, import, and project version operations
- Current version verifications have been made mandatory
- Secure lock management is provided for long-term transactions
This has improved consistency, data security, and system stability in project operations.
The behavioral reflection of the development is as follows.
When a deploy process is in progress on the same project, when a deploy is requested from another screen (different user or browser), the second user is informed that there is an ongoing deploy process and the process is not started. In this process, other conflicting operations such as build, import, datasource execute, adding/deleting components are also prevented.
While the import process is in progress in a project, when a new import or deploy process is desired to be started on the same project or version, the user is informed that the relevant process is in progress.
When the same major version of the same project is open on multiple screens:
If the major deploy is in progress, no further deploy operations can be started until it is complete.
After the major deploy is completed, minor broadcasting can be done on the same major version open on the other screen.
While the minor deploy is in progress, a new minor deploy cannot be started on the same major version.
When the minor deploy is completed, the project open on the other screen is put into read-only mode. No action can be taken.
For transactions that are desired to be started while there is an ongoing transaction:
Transaction-specific warning message in operations such as deploy and import
For other overlapping processes, a generalized "transaction in progress" warning is shown.
2. Bug Fixes
184458 – The problem with opening forms in the Firefox browser has been fixed with the upgrade made in the libraries of the relevant object.
187741 – The incorrect match problem in the Fixed Value Check object, where static value control is provided in the Rules Manager, has been fixed.
187054 – Fixed the issue where the loading shown on the screen was not turned off in the scenario where the flow returned to the same user in the flow forms that looked SmartView on mobile in the web interface.
187135 – Fixed an issue where the toaster window shown for flow notifications for user approval did not close when the application was open in SmartView looking forms in the Synergy mobile application.
187950 – Fixed an issue with the appearance of the selection fields in the archive form insertion mode in the IDE interface.
186817 – The problem experienced when starting work for files of the type for which a viewer has not been assigned in Document Management has been fixed.
188011 – The problem of not adding lines to the datagrid with server side code has been fixed.
187963 – When an error is received in an existing component (form, flow, datasource, etc.) in the developer interface at the same time or in consecutive registration operations, the error is displayed in the interface with a toaster message.
187908 – The error received during the creation of the archive form in the developer interface has been fixed.
163987 – Fixed a deadlock error that occurred occasionally in simultaneous or consecutive registration operations in an existing component (form, flow, datasource, etc.) in the developer interface.