> For the complete documentation index, see [llms.txt](https://docs.volven.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.volven.io/changelog/v0.48.0.md).

# v0.48.0

19th January 2024

## What's new

* Add custom title component to trading view module
* Add support for all conversion and transfers
* Add Live indicator to Orders Chart
* Add scaling orders vertically to fit the visible area in the orders chart in strategy detials
* Add `total_time` and `allowed_size` to strategy properties debug list
* \[Strategy details] Unable to select very small orders in Orders Chart
* Username and Password input fields accept newline and tab characters
* \[Create strategy] DMM, TMM should not differentiate between buy/sell colors
* \[Create strategy] Binding loop when selecting ALO
* \[Strategies] Can’t access more parameters due to scrolling
* \[Strategies] Scroll bar covers fields in strategy details
* Icon for Volven Terminal has some background leftover


---

# 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 dynamically by asking a question.

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

```
GET https://docs.volven.io/changelog/v0.48.0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
