> For the complete documentation index, see [llms.txt](https://docs.timvero.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.timvero.com/release-log/release-notes-8.4.md).

# v. 8.4 - Release Notes

v8.4 is about keeping decisions current and launches on schedule: a line-by-line comparison between two versions of external data, scheduled credit product activation, a Save to Profile node that writes several attributes at once, and a configuration transfer with split permissions, file metadata and an operations log.

***

## 🆕 New Features

### 🆕 [Feature Comparison](/release-log/release-notes-8.4/feature-comparison.md) — See what changed since the decision

`NEW`

When a data source is requested again during origination, the Features tab now shows the **previous and the current value side by side**, highlights the rows that changed and puts them first — so an underwriter sees at once whether the client's data moved, and where.

***

## 🔄 Improvements

### 🔄 [Credit Product Scheduled Activation](/release-log/release-notes-8.4/credit-product-scheduled-activation.md) — Set the time, the platform launches it

`IMPROVED`

A Draft credit product can be given an **activation date and time**. At that moment the platform checks readiness and activates the product; if it cannot, the product stays in Draft with a **Product activation error** label and a link to the cause.

***

### 🔄 [Profile Saving in Workflow](/release-log/release-notes-8.4/profile-saving-in-workflow.md) — One node, all the attributes

`IMPROVED`

The **Save to Profile** node now writes **several profile attributes at once**, each with its own expression — no more chains of single-attribute nodes across the decision tree.

***

### 🔄 [Configuration Export/Import](/release-log/release-notes-8.4/configuration-export-import.md) — Verified on test, applied to production

`IMPROVED`

The transfer tool now has **separate Export and Import permissions**, shows the **source environment, author and date** of a file before import, carries the **business day calendar**, and keeps every operation with its result and its file in an **operations log** inside the Admin Panel.

***

### 🔄 UI Enhancements

`IMPROVED`

* **Time in date filters** — list filters by date (Activity Log, Launchpad and other lists) now accept a time of day, so a period can be narrowed to the hour.
* **Scrolling at component level** — vertical scroll moved from the page to the component, removing the layout jump when content expands.
* **Credentials hidden on System Settings** — secrets are no longer displayed on the System Settings page.

***

### 🔄 Workflow Transition to SSE

`IMPROVED`

Workflow communication moved to a unidirectional model: the client opens the connection and the server streams **Server-Sent Events**. A simpler contract, better resilience, and no callbacks to the client. No configuration change is required.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.timvero.com/release-log/release-notes-8.4.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
