> For the complete documentation index, see [llms.txt](https://docs.roomle.com/rubens/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roomle.com/rubens/whats-new/2026/february-2026.md).

# February 2026

## Configurator/Room designer news

#### HI Article Integration

We have successfully integrated HI articles into the Room Designer product list. By resolving previous technical constraints, users can now access a more comprehensive range of articles directly within their workflow.

#### Multi-Level Catalogue Support (Level 2+)

To align with the latest industry interface standards, we have upgraded our room designer catalogue structure to support 2 or more levels for categories. This allows for a deeper, more organized catalogue hierarchy within the sales configurator, ensuring that even complex product libraries remain easy to navigate.

#### Improved Product Naming Logic

We have refined how product identifiers are displayed to the end-user in the user interface of the Rubens Room Designer. Based on valuable customer feedback regarding interface clarity, we have eliminated the display of technical configuration hashes (saved configuration identifiers) in the product menu after selecting a product. The system now displays the label of the Root Component ID, providing a clean, professional, and human-readable name for every item.

#### Persistent Camera Positioning

We have updated the camera logic so that your position is now persisted when switching between 2D and 3D views. Instead of reverting to a default starting point, the camera stays exactly where you left it, allowing for seamless transitions during the design phase.

#### Streamlined Rotation Controls

The rotation input option has been removed from the side menu of the Rubens Room Designer after a product is selected. Instead users can now simply click the text field within the rotation indicator itself to manually enter or paste precise rotation values.


---

# 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.roomle.com/rubens/whats-new/2026/february-2026.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.
