...
- The session handling is optimized. Current sessions can be monitored on the REST-WS status page. To avoid DOS attacks, the maximum number of sessions for one user can be configured in yuuvis® RAD management-studio.
You can monitor the technical update tasks on the REST-WS status page.
New Features in yuuvis® RAD designer
...
- With version 6.0 we announced to deprecate the ETL functionality with version 7.0. It is still available for the SAP integration, but the XML - file extraction functionality has and script execution functionalities have been removed. You have to migrate your import process to a Talent Talend import process.
Notice: If you try to import with your old process, you will see an error stating the "Driver can not be loaded" in the ETL log.
With version 8.0, the complete entire ETL functionality will be removed because the SAP integration will not rely on ETL anymore. - Binary fields have been deprecated, since it is better to keep binary content as document payload (its content is searchable, can be rendered) of an object, so its use in projects was extremely rare. Projects that use this type will receive a deprecation warning. The field type will be removed with the next major version of yuuvis® RAD.
- The deprecated functional rights "Assign global roles" and "Edit roles related to global domain" have been removed. These rights will be automatically removed from the server during an update to version 7.0. and they will no longer be included in system snapshots created from an updated server. However, they may still exist in older projects located on local filesystems. In case that they are still present and an administrator attempts to activate such schemas, the schema and role set validation will show an error – they must be removed from the rights system prior to activating the schema and role set in a yuuvis® RAD 7.0 system or later (or a snapshot of an already updated system should be taken in order to create a project without these rights).
- BPM Script: the deprecated script property
process.responsible
has been removed. It had been deprecated with the introduction ofprocess.owners
which can also be changed (unlikeprocess.responsible
which was read-only). - BPM-Service
- The deprecated optional parameter "maindoc" has been removed in the following endpoints of the bpm-service:
GET api/bpm/process/{processId}/file - get process file
POST /process/{processId}/file/{elementId} - create process file
PUT
/process/{processId}/file/{elementId} - update element of process file
get list of process instances that include documents (parameter of call) in their filesPOST api/bpm/process"-
The following deprecated methods have been removed:
GET /api/bpm/process
- The method GET /api/bpm/processes should be used instead
GET /api/bpm/process/user
- core-service method BpmProcessService.getProcesses should be used instead
- The deprecated optional parameter "maindoc" has been removed in the following endpoints of the bpm-service:
- Core-Service
The
locationinfo
parameter forDmsService.getItem
has been removed. Use thecontextinfo
parameter instead.The
renditionType
parameter forMediaManagementService.assignBinding
has been removed. This parameter is no longer necessary and has not been handled in previous versions.The
csmeta
parameter forResultService.getEsqlResult
has been removed. Use thedatameta
parameter instead.The internal endpoint
InterProcessResourceService.getRendition
has been removed.
...