Breaking Changes

You will find all breaking changes for the major and minor releases below.

Implementation of a License Control, starting with version 10.0:
- Differentiation between named and concurrent user
- Differentiation between PRODUCTION, TEST, and PROVISION (trial) system with the control of an expiration date
- Later and step by step: Control of functions like Import/Export (ETL), Signing, OCR, ...

In yuuvis® RAD version 8 LTS, the BPM-Scripting API call "$.history.createEntry" was deprecated by a new method "$.history.addEntry".
The deprecated method is removed with version 10.0.
The script engine is running in strict mode, so some of the errors that were previously present in scripts (and were ignored by the engine) are now visible.
- If a read-only property of an object belonging to the workflow scripting API is changed, an exception will be thrown. In previous versions, it would appear as if they could obtain a new value, but when saving the state of properties, they would not be saved.
  - This change in particular affects manipulation of performers in scripts, where old examples were using read-only fields in an improper manner.
  - We have introduced a new approach to obtain the correct OrgObject (with method getObjectById() ), details can be found in How to Update/Upgrade 10.x.
- Use of undeclared variables results in an error. This is a frequent issue in Javascript that does not run in strict mode and is typically caused by a typo (either a name of a previously declared variable is mistyped, or var declaration is forgotten). The issue is corrected by using the correct name, or by properly declaring the variable.

Custom clients must be upgraded to Angular 17 because the client has been updated to this framework version. See this documentation for building a custom client as well: https://yuuvisdevelop.atlassian.net/wiki/spaces/onpremise/pages/319620113
The Task list widget has been refactored and face-lifted. The old version saved the list data in the local browser storage, so the data was not available on other workstations.
The new widget saves the data centrally. However, the old data will get lost.

In a client form-script, it is possible to check with row.persisted whether a row existed or not when the onchanged event was fired. But row.persisted gave the wrong false or true value for the current situation. Now this is corrected so you need to change your script and negate your logic.

Deprecated Features

You will find all deprecated features for the major and minor releases below.

Qlik, the new owner of Talend Open Studio has discontinued it from January 31st, 2024.
For this reason, we are forced to deprecate the Talend connectors for yuuvis® RAD but we will continue to offer support in form of bug fixes in yuuvis® RAD version 10.0.
In BPM-Scripting API, the class "Variable" has been deprecated and we recommend using the new class "Datafield" instead. It is similar to the deprecated class "Variables" but offers a simpler and more consistent API when working with complex data types (for instance, lists of lists). Details and examples can be found in BPM-Scripting API documentation in core-service. It is allowed to use "Datafield" and "Variable" classes in different scripts of the same workflow model, but not to mix them in the same script. This also means that if the model's global script was adjusted to use the class "DataField" instead of "Variable", it must be ensured that other scripts calling affected global script methods are adjusted, too. And vice-versa, if global script uses the class "Variable", then its client should also use the class "Variable".