# v4.16

## Release highlights <a href="#v4.16-releasehighlights" id="v4.16-releasehighlights"></a>

### 1. Profiling on demand <a href="#v4.16-1.profilingondemand" id="v4.16-1.profilingondemand"></a>

The way for a user to request profiling has been improved by allowing this request on demand using user interface.  As of now this is only available at a field level but will be enabled at table level in following releases. The option will only be displayed to users with permission to run profiling and in structures that are being populated by a data source with profiling enabled.

Please be advised that in order to have the profiling working some changes need to be done in the connector in order to support this new functionality.

![](/files/-MaJIV5gvT9zROynQSt5)

## Features and fixes delivered with this release <a href="#v4.16-featuresandfixesdeliveredwiththisrelease" id="v4.16-featuresandfixesdeliveredwiththisrelease"></a>

### Features <a href="#v4.16-features" id="v4.16-features"></a>

* TD-2951 - As a user with permissions to run profiling I want to run the profiling of one field from the front-end
* TD-3326 - As an admin/integrator I want to setup the session timeout
* TD-3327 - As a I user I want to click on the title of a result search (global search) to navigate to the asset

### Fixes <a href="#v4.16-fixes" id="v4.16-fixes"></a>

* TD-3185 - Implementation key is not updated when an implementation is modified
* TD-3387 - It is not possible to modify extra information in data structures without refreshing the screen
* TD-3444 - Metrics connector error on run.sh


---

# 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.truedat.io/v8.4/release-notes/v4/v4.16.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.