|Secured Remote Engine usage||A Remote Engine can now be allocated to a specific workspace with
dedicated workspace permissions, so as to ensure the secured usage of this
engine by a specific group of users.
The new permissions added for this purpose include the individual permission Engines – Use and the workspace permission Use engines.
By combining these permissions, you can easily manage which users can access and use the Remote Engines, including the Remote Engine Gen2, in all types of environments. Both permissions do not consume any seats.
You can assign these new permissions to any role. By default, some roles already have the individual permission Engines - Use. See the list in the below row.
|New permission Engines - Use added to the predefined roles|| With this new permission, the following roles can now view and use
remote engines to run tasks without consuming a seat:
New APIs are introduced to automate the management of the logs of the task runs in Talend Cloud Management Console.
||Gets logs of a given task run.||
These parameters are all optional.
||Generates the full log of a given task run and returns a
download token to this log.
This token is valid for one hour.
||Checks the status of the generated log and returns a download
Put the download token in the body.
For documented use cases of these APIs, see Monitoring task runs
Some fixes are linked to internal issues, therefore not visible for users outside Talend.
|TMC-25012||Advanced parameters were incorrect after promoting the plan.|
|TMC-25038||All tasks did not update after a new artifact version has been published.|
|TMC-25051||Deleting a workspace was not allowed because of common artifacts.|
|TMC-25069||Could not delete artifacts because of workspace permissions.|
|TMC-25076||Tasks scheduled on a daily basis did not run.|
|TMC-25078||Could not connect Talend Studio to Talend Cloud.|