Release notes - March 2026: Mapping tables finally in Starlify!

Hi there! 

In the beginning of March, we released another update for Starlify, and this was one you have been waiting for!

Mapping tables are finally available, meaning you can now add mapping data between contracts! This is a crucial piece of information that helps humans and AI agents alike understand exactly how data is treated in and between systems. It means we now have a complete picture of integration metadata, from the high level business requirements all the way down to the exact details.

In addition to this, we have also made an an improvement that allows you to cascade delete more entities with less work.

Let’s take a look 👇

🔌 Introducing Mappings!

We are thrilled to introduce Mappings, a brand-new feature that describes how data is transformed from a source contract to a target contract. You can now browse, create, and edit mappings directly from a new left menu item or within your contract details. 

⚙️ How it works:

• Contract-to-Contract: Both the source and target for a mapping must be contracts.
• Row-Level Granularity: You can define row-level mapping definitions, including the operation text that describes the transformation.
• SIR table Integration: Mapping rows document transformation between System Information Requirement (SIR) rows owned by either contracts or references.
• Flows: From a flow's details panel, you will be able to see the mappings used in that flow.
• Import and export: Mappings are fully supported in your import and export jobs.

🧠 Why it matters

Mappings allow you to capture the exact row-level data transformation logic between your integration contracts. Instead of just knowing that two systems communicate, you can now document exactly how the data evolves—for example, mapping a source system order payload to a target system by transforming an "amount" field using an operation like "transform:decimal(2)".

While mapping tables have always been important tools for integration work, bringing them into Starlify allows you to keep more of the important documentation in the same place, and it sets the field for AI-driven insights and AI-powered further work.

🔎 Where to find the mappings

To open the mappings editor, find the mappings symbol on the left menu. If you are working on a laptop screen, you might have to click the triple dot icon at the bottom of the left menu to find it.

Pro tip: Did you know you can rearrange your left menu icons to move your most used menu items to the top? Just click and drag the icon you want to move to your wanted position!

When you have added mappings, you can also find them in the details panel of the contracts and flows they are involved in.

🔎  Cascade deletion of systems with references 

 Did you ever notice that you could not delete a Starlify system that had references to its services or endpoints? This meant you first had to delete all such references one by one before being able to delete the system. Lots of manual work! Well, that time is over now, because we have added cascade deletion of such references when you delete the system! 

⚙️ How it works:

• Cascade Deletes: We now let references cascade delete when deleting systems.
• Clear Warnings: When deleting a system, you will see a warning modal detailing exactly which related entities—such as subsystems, services, endpoints, contracts, and references—will also be deleted. Once you confirm, the deletion will happen.

🧠 Why it matters

This means less clicking in Starlify to achieve your goal, while still getting clear information on affected entities. 

As always, we’d love your feedback

Try it out and let us know what you think 💬