> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/release-notes/archive/2024/2024-06-07-ce-mixin-schemas.md).

# 2024-06-07: CE - Mixin Schemas

### Overview

Mixins are a fantastic extension concept that allows you to design your platform flexibly, extend it quickly and respond to the individual business requirements of your customers. This contributes to more efficiency, competitiveness and customer satisfaction.

For more details, check out the What’s New table.

### New features

| Feature                                                                      | Benefits                                                                                                                                                                                                                                                                                       |
| ---------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Management Dashboard support for objects, arrays and nullable attributes** | Empower your team with intuitive handling of complex arrays and objects. This provides your employees with a Management Dashboard wizard to distribute and organize development processes more efficiently, enabling your company to respond very fast to customer requests and market trends. |
| **Displaying arrays and objects on entity level within the**                 | <p>The out-of-the-box arrays and objects are displayed automatically in a well-structured format, eliminating the need for further implementation, which speeds up project implementation.<br><br>Objects, arrays, and decimals are available for all supported entities.</p>                  |

### Fixes and improvements

Supporting now array, object, decimal attributes within the Management Dashboard. Also, it's possible to define the schema to accept `null` values.

### Known problems

None.

### Documentation and links

* Management Dashboard User Guide - [Mixin Schemas](/user-guides/management-dashboard/settings/mixin-schemas.md)
* Core Commerce Guide - [Mixin Schemas](/user-guides/core-commerce/mixin-schemas.md)
* Developer Guide - [Schema Service Tutorial](/api-documentation/api-guides/utilities/schema/schema.md)
* API Reference - [Schema Service](/api-documentation/api-guides/utilities/schema.md)


---

# 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://developer.emporix.io/release-notes/archive/2024/2024-06-07-ce-mixin-schemas.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.