# What's New

## These are the highlights of our Helmut release 4.7.0:

#### New features

* Added "PATCH" method to HTTP node.
* Improved the timeout settings and status verification of the Diva nodes.
* Added a boolean field "Vidispine Wildcard" in VidiCore Get Item ID By Relative File Path Action V3.&#x20;
* Added an optional string field "Storage ID" in VidiCore Get Item ID By Relative File Path Action V3.&#x20;

#### Improvements

* Added a new reduced HelmutIO project file for more efficient rendering in After Effects exports.
* Updated EFS nodes to work seamlessly with the Editshare Multisite Service.
* Reduced the size of metadata objects in job, project, and asset objects.
* Updated the Premiere Path Settings Action node description  to align with the terminology used in the latest Premiere versions
* Optimized MongoDB's CPU utilization.
* Implemented "Skip metadata sync" & "Skip markers sync" switches in Cosmo Change Asset Action, Cosmo Add Proxy To Project Action, and Cosmo Change Project Asset Action to enhance synchronization performance.
* Introduced an option to bypass SSL checks for HTTP Action.
* Enhanced the FX frontend to pre-resolve the helmut templates path in preferences.

For more detailed information check our [Changelog](/helmut4-releases/v4.7.0/release-notes/changelog.md)\
\
Please feel free to contact our Helmut Support Team in case of any questions! [Support](/helmut4-releases/v4.7.0/support/requesting-support.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.helmut.de/helmut4-releases/v4.7.0/release-notes/whats-new.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
