> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/releases/2023/2023.4.0-february-14-2023.md).

# 2023.4.0 - February 14, 2023

### Nested Configurator API

The get Configurator API has been expanded upon to be more useful when working with Nested Configurators.

Firstly, an API that will only run Catalog Item logic has been added. Allowing for attribute data to be retrieved without the need to load the 3D asset data associated with those attributes.

Secondly, an API to get the nested configurator for a given Attribute has been added. This can be called recursively to dig through multiple layers of nested configurators/attributes.

With these you'll be able to eliminate the need to load asset data when not wanted, which depending on the complexity of your assets could greatly affect performance and stop the configurator from being interacted with until it's finished.

For full details and how to use the new API, visit the [documentation page](https://developer.threekit.com/reference/nested-configurators).

&#x20;

### Bugs/Cases

* DEV-910 Product import jobs with new tags failing
* DEV-751 2D not initializing properly - getting stuck on loading
* DEV-785 Composite API not using stage configuration
* DEV-827 Composite Layer showing empty list in rules


---

# 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://community.threekit.com/releases/2023/2023.4.0-february-14-2023.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.
