New features
| Feature | Description |
|---|---|
| Audit logs | New event types have been added to the audit logs. This update covers event types varying from access management to project or environment management. Since this release, audit logs have started to record basic yet limited number of activities in more Talend applications, such as login in Talend Studio or configuration changes in Talend Cloud Data Preparation or Talend Cloud Data Stewardship. |
| Debugging Job runs | As an improvement to the debug feature introduced in the previous release, now you can debug Job tasks in any status except Running. |
| Restrictions on Cloud Engine for Design run profiles | From this release on, it is not possible to create
Standard, Big Data, or
Advanced type run profiles for Cloud Engines for
Design. This engine can only be used with Databricks
type profiles, or without a profile (default settings). However, all run profile types can still be created and used with Remote Engine Gen2. |
Bug fixes
These fixes are linked to internal issues, therefore not visible for users outside Talend.
| Issue | Description |
|---|---|
| TMC-23688 | HTML injection vulnerability in log entries. |
| TMC-23117 | Talend Studio log4j logs are not consistent with Talend Management Consolelogs after adding log4j2 custom code. |
| TMC-22987 | Tasks scheduled on Remote Engine cluster are executed and fail on Cloud Engine. |
| TMC-22813 | A particular Job task constantly fails when executed in Talend Management Console but successful when run from Talend Studio on a Remote Engine. |
| TMC-22183 | A triggered task starts two executions of a single Job against the same Remote Engine, which appears as multiple tasks in the Operations page, even though the task history shows no duplicate runs. |
Get started with Talend Management Console on Talend Management Console User Guide.