---
uid: whats-new.2026.03
---
# What's new in Intent Architect (March 2026)

Welcome to the March edition of What’s New in Intent Architect.

- Highlights
  - **[Integrated diff tool in the Software Factory](#integrated-diff-tool-in-the-software-factory)** - The Software Factory dialogue now has an integrated diff tool (no more needing to launch an external diff tool) as well as other layout improvements.
  - **[Mapperly support for DTO mappings](#mapperly-support-for-dto-mappings)** - Type-safe, compile-time DTO mapping with zero reflection overhead.
  - **[Automatic route parameter filtering in API documentation](#automatic-route-parameter-filtering-in-api-documentation)** – Eliminates duplicate parameter documentation in API specs when properties are already defined as route parameters.
  - **[Convert many-to-many associations to intermediate entities](#convert-many-to-many-associations-to-intermediate-entities)** - Transform implicit join tables into explicitly modeled entities for advanced customization.
  - **[Improved Code Management Documentation](#improved-code-management-documentation)** – Practical real-world examples and guidance on choosing code management techniques.

## Update details

### Integrated diff tool in the Software Factory

The Software Factory Dialogue **Changes** view has undergone extensive updates:

![Software Factory dialogue improvements](images/updated-software-factory-dialogue.png)

The most noticeable change is the integrated diff view, simply selecting a file in the left pane will show the diff inside the Software Factory dialogue. Typical diff viewing options as well as the ability to save changes are available above the right side of the diff:

![Software Factory diff tool toolbar](images/software-factory-diff-tool-toolbar.png)

As part of the above changes, the list of files has been changed to be a tree view so as to require less screen real estate as well as making it more clear where files are being output to.

The toolbar buttons above the file list can be used to choose filtering options or toggle between "flat" and "tree" views of the change list:

![Change list buttons](images/sf-changes-view-buttons.png)

Available from:

- Intent Architect 4.6.0

### Mapperly support for DTO mappings

![Mapperly example](images/mapperly-example.png)

The new `Intent.Application.Dtos.Mapperly` module generates type-safe mapper classes and extension methods using [Mapperly](https://mapperly.riok.app), providing compile-time code generation instead of reflection-based mapping. Mappers automatically handle entity-to-DTO conversions with null-safety and nested DTO references, while remaining fully extensible via partial classes for custom mapping logic.

Available from:

- Intent.Application.Dtos.Mapperly 1.0.3

### Automatic route parameter filtering in API documentation

![Swagger Example](images/swagger-route-param-filter-example.png)
![Scalar Example](images/scalar-route-param-filter-example.png)

When documenting REST endpoints, you often reference the same parameter as both a route parameter (`/api/users/{id}`) and in the request body schema, causing confusing duplication. Both `Intent.AspNetCore.Swashbuckle` and `Intent.AspNetCore.Scalar` now automatically remove properties from request body schemas when they match route parameter names, ensuring clean API documentation.

The implementation handles inline and referenced schemas, matches names case-insensitively, and removes properties from the `required` list automatically.

Available from:

- Intent.AspNetCore.Swashbuckle 5.2.3
- Intent.AspNetCore.Scalar 1.0.7

### Convert many-to-many associations to intermediate entities

![Before Convert to Intermediate Entity](images/pre-convert-intermediate-entity.png)

![Suggestion to Convert to Intermediate Entity](images/suggestion-convert-intermediate-entity.png)

![Converted](images/converted-intermediate-entity.png)

When modeling many-to-many relationships, a new `Convert to Intermediate Entity` suggestion (available in the Domain Designer) allows you to convert implicit join tables into explicitly modeled entities. Hover over any many-to-many association and select the suggestion to create an intermediate entity with two many-to-one associations, giving you full control over the join table structure for adding properties, indexes, or constraints.

Available from:

- Intent.Metadata.RDBMS 3.7.12

### Improved Code Management Documentation

In our ongoing effort to improve our documentation, a new article has been added with **practical real-world** examples of code management, including guidance on when and how to use each technique.

![Code Management Documentation](images/code-management-docs.png)
*Updated Code Management documentation*

See the full article: [Practical Code Management Examples](https://docs.intentarchitect.com/docs-md/application-development/code-management/practical-code-management-examples/practical-code-management-examples.md)