Release Notes
CrossModel Professional v1.27.15
Upgraded 1 November 2026, 22:00 CET.
The hosted environment moves from v1.19.4 to v1.27.15. Your workspaces, models and Git history open as before. One thing looks different the first time you save an older model file, and it is explained below: the file is written with two spaces per level.
Watch it first
What is new in 1.27 shows Model Changes, the toolbar, the form outline, clearing a field and identifiers that survive a rename, in two and a half minutes.
See your changes as model changes
Source Control opens with a new section, Model Changes, that lists what you changed the way you modeled it rather than file by file: each changed entity, relationship or diagram under its data model and folder, as in the Model Explorer, and inside it the attributes you changed. So Customer, Email tells you at a glance what a commit will hold, where a list of files would only say Customer.entity.cm.
From there you can compare an object with the last commit (Open Changes), throw a change away (Discard Changes, on an object or a whole folder, after a confirmation) and Commit with a message, in one place, or commit and push in one click with Commit & Push. A commit from Model Changes takes all your model changes at once, with no staging. Model Changes lists model files only; if other files have changed as well, CrossModel asks whether to include them.
Below it, File Changes lists every changed file, templates and other non-model files included, with Git's full set of steps: staging files one by one, committing and pushing separately, stash, branches and merging.
A toolbar for the everyday actions
A toolbar now runs under the menu bar: Save, Save All, Undo and Redo on the left; the CrossModel Assistant, Properties and Toggle Name/Id Display in the middle; Close All Tabs in Main Area, Split Editor Right and Reset Workbench Layout on the right. Undo works on a form as well as on a diagram or the code, and Split Editor Right opens a second copy of any CrossModel editor beside the first, so an entity's form and its code, or two corners of one diagram, can be open at once.
See The toolbar.
An outline for every form
The Outline view now works on the Form Editor tab too: one entry per section, the fields in it, and every row of a grid, so an entity's outline lists its attributes and identifiers by name. Click a section and the form scrolls to it. The Outline is docked in the right bar from the start, next to Properties, so it no longer has to be opened from the View menu each session.
See Outline in the form editor.
Fields you can clear, and that keep what you type
Dropdown fields, a Type, a Realizes, a cardinality, behave the same way in a form and in a grid cell. Text you type is kept while you look for a match; Enter or Tab takes the option that matches it, Escape throws the typing away. A field that may be empty has a clear (×) button beside it, so removing a value is one click rather than selecting the text and deleting it.
Identifiers that survive a rename
A data model can give every object a UUID, a permanent identifier that stays the same when the object's name or id changes, so a catalogue, a lineage tool or a deployment script can follow an object across a rename. Tick Assign unique identifiers in the data model's new Settings section and save: CrossModel offers to give the objects that already exist a UUID in one go, and every object created afterwards gets one when it is first saved. The UUID shows read-only under the ID. Set on a data model definition, the setting applies to every data model of that type.
See Giving every object an identifier that survives a rename.
Styles are grouped in a style block
The colour and border fields of an entity, a relationship, a definition or a diagram node are
written together under style: in the model file. Files that still have them one by one load as
before, with a warning on each such line that offers a quick fix, and are rewritten in the new
form the next time you save them. The example workspaces on the welcome page have been converted,
so a fresh clone opens without warnings.
See Giving a type its own look.
What looks different
Model files are written with two spaces per level. Files saved by earlier versions used four. An older file keeps its layout until a save changes it; that save writes the whole file in the new layout, once. CrossModel's own comparison ignores the indentation, but the commit and a comparison on GitHub or Azure DevOps show every line of the file.
Other fixes in this release
- Identifier attributes inherited through
inheritsorextendsare kept. An identifier that used an inherited attribute could lose it when the workspace loaded, and the file was rewritten without it. That no longer happens, and the Attributes picker in the Identifiers grid offers the entity's attributes again. - Diagrams keep their lines after a quiet spell. A diagram reopened after its model had been idle could lose relationship lines, Show Relationship could add a second node for an entity that was already there, and a paste in the code editor could repeat itself. All three are fixed.
- A referenced attribute is labelled by its entity,
Customer.Id, orExample CRM.Customer.Idacross data models, where it used to show only the data model. - Dropdown and date panels stay with their field when the form scrolls, and close when you switch tabs.
- Generate and Generate All report a template that cannot be found as an error rather than skipping it, and Handlebars templates can read values an object inherits, as Nunjucks templates already could.
- The AI assistant writes data models for the current CrossModel version, so they are no longer flagged as needing migration.
- An attribute without a datatype is drawn without a trailing colon on a diagram, so a conceptual attribute reads Customer Name rather than Customer Name :. The same goes for the diagrams in generated documentation.
CrossModel Professional v1.19.4
Upgraded 18 October 2026, 22:00 CET.
The hosted environment moved from v1.16.1 to v1.19.4. Your workspaces, models and Git history open as before. Two things behave differently, and both are explained below: dependencies between data models reach one step, and an older diagram is rewritten with current keywords the first time you save it.
Watch it first
What is new in 1.19.4 shows conceptual diagrams, notes, colour by type and copy and paste in a little over two minutes. Conceptual models shows conceptual modeling on its own, in ninety seconds.
Conceptual modeling is released
This is the release that makes conceptual modeling an official part of CrossModel. Earlier releases carried parts of it as a preview; v1.19.4 delivers the whole tier, and it is the first release in which we recommend using it for real work.
A conceptual model records what the business means - the things it cares about and how they relate - before anyone decides how they are stored. Everything that takes:
- Conceptual data models. An ordinary data model whose Type is
Conceptual. It offers what you need to describe the business: entities, relationships and diagrams. - Concepts in business terms. A concept carries a name, a description and the attributes the business uses to talk about it. Storage details follow on the logical entity that realizes it.
- Relationships between concepts, with their cardinalities, as on the logical tier.
- Conceptual diagrams. Right-click the model and choose New Element → Diagram.... Drag concepts in from the Model Explorer, and the relationships between concepts you drop together come with them; or create a concept or a relationship straight on the canvas, which is often where the conversation with the business starts. The toolbox is made for concepts: show, create and relate them, and add notes. Styling works as on a logical diagram.
- Realizes, the link to the logical tier. A logical entity, and each of its attributes, records which concept it implements. The link lives on the logical side, so one concept can be realised by many systems, and you can ask which.
See Conceptual Modeling, which builds a conceptual model, links a warehouse to it and draws it, and A conceptual model linked to a logical one.
Notes on a diagram
Create Note puts a free-text note on a logical or conceptual diagram, for the decision, the open question or the warning that the next reader needs. Double-click to edit, ++shift+enter++ for a new line. Notes keep the size you give them and can be coloured like any node.
See Notes on a diagram.
Colour a type once, see it everywhere
Entities, relationships and their type definitions have a Style section: background, border and font colour, border weight and style. Put a colour on a definition and every object typed by it is drawn in that colour on every diagram, including entities created later. A node on one diagram can still override it, and the most specific value wins.
See Giving a type its own look.
Type definitions for mappings
Four new definition kinds: Mapping, Source, Target and Attribute Mapping Definition, and a Type field on each of those parts of a mapping. They carry what the other definitions carry - custom properties with defaults, code generation templates, property templates - so a kind of load can be described once and applied to every mapping of that kind.
See Typing mappings.
Copy and paste rows between forms
Right-click a row in any grid - attributes, custom properties, identifiers, dependencies - and copy it, then paste it above or below a row in another object's grid. Where a pasted attribute clashes with an existing one, you choose per row whether to create a new one, replace the old one or leave it out.
See Copying attributes between entities.
A second copy of an entity is now a choice
Dropping an entity onto a diagram it is already on asks first: The entity "Customer" is already shown on this diagram. Add it again anyway? When you do, each occurrence carries a number, ¹ and ², so two boxes for one entity cannot be mistaken for two entities.
See Dropping an entity that is already there.
Diagrams in generated output
Every diagram has an _svg property in CrossGenerate templates: the diagram drawn as an SVG
image, as the editor shows it. A documentation template can now put the picture of a model next
to its description, and a diagram can be exported to an .svg file of its own.
See Putting a diagram into the output.
An Outline for the code editor
The Outline view (++ctrl+shift+i++) now follows the Code Editor tab as well as the diagram: it lists the structure of the file, and clicking an entry jumps to it.
See Outline in the code editor.
Two changes in behaviour
Dependencies reach one step. A data model now sees its own contents and those of the models its dependency list names, and no further. Before, it could also see what those models depended on. If a reference field that used to offer an object now comes up empty, add that object's data model to the dependency list of the model you are editing. In return, editing a dependency list no longer stalls a large workspace: a save that took more than ten seconds on a customer's workspace now returns at once, with a progress message while the rest catches up. A dependency declared on a DataModel Definition now also counts for every data model typed by it.
See the dependency note in Conceptual Modeling.
Older diagram files are rewritten on first save. Diagrams now come in one kind per tier, and
a logical diagram file says logicalDiagram: and logicalEntityNodes: where it used to say
diagram: and entityNodes:. Old files open unchanged. The first time you save one, the
keywords are updated, so that diagram's next commit shows those lines changed. New diagram files
are named .diagram.lcm (logical) and .diagram.ccm (conceptual); existing .diagram.cm files
keep their names.
Other fixes in this release
| Fix | What you would have seen |
|---|---|
| Diagrams | Right-clicking empty canvas offers the same tools as the toolbox, plus Auto Layout |
| Diagrams | The line that follows the pointer while you draw a relationship is back |
| Diagrams | Two open diagrams no longer interfere, which made some node borders draw twice as thick |
| Code editor | The outline keeps up with edits and keeps its place when you return to the tab |
| Forms | An autocomplete list opened right after clicking elsewhere no longer closes at once |
CrossModel Professional v1.16.1
Upgraded 24 September 2026, 22:00 CET.
The hosted environment moved from v1.12.4 to v1.16.1. Nothing you have modelled changes: existing workspaces, models and Git history open exactly as before.
Find anything on a diagram
Two ways to get around a diagram too big to scan.
Press ++ctrl+f++, or use the magnifier in the diagram toolbox, and a box opens over the canvas listing every node and edge. Type part of a name, pick an entry, and CrossModel selects that element and centres the canvas on it.
The Outline view (++ctrl+shift+i++) lists the whole diagram as a tree, grouped the way the model is: Entity Nodes, Relationship Edges and Inheritance Edges for a system diagram, and Sources, Target and Attribute Mappings for a mapping. Clicking an entry selects it on the canvas.
See Finding your way around a large diagram.
Drop several entities and keep their relationships
Select entities in the Model Explorer, drag them onto a diagram together, and the relationships between them are drawn for you, inheritance links included. On a diagram that was empty, the new nodes are laid out so they do not overlap.
A relationship is added only when both of its ends are part of the same drop, so a drop never quietly adds lines to boxes you placed earlier. An entity whose data model is not a dependency of the diagram's model is not added, and a warning names it.
See Datamodeling Fundamentals.
See which mappings fill an entity
An entity form now has an Incoming Mappings section listing every mapping whose target is that entity, with an action to open each one. Previously the only way to find out what filled an entity was to open each mapping and read its target.
See Mapping Fundamentals.
Filter a mapping with an expression
A mapping can now carry an expression that decides which rows it produces, not only what each
attribute contains. There are two: one on the mapping, evaluated against the source objects,
and one on the target, against the target entity's own attributes. Both use the familiar
{{Source.Attribute}} syntax with the same {{ suggestion list, and both are checked against
the attributes that actually exist.
Clicking empty canvas on a mapping diagram now shows the mapping's own form in the Properties panel, which is where that filter lives, and the panel header names whatever you selected instead of always naming the mapping.
See Add expressions to a mapping.
Custom properties in more places
Custom properties can now be attached to a system diagram, to an entity node or an edge on one, and to a conceptual entity attribute, alongside the objects that already supported them.
See Where custom properties can be attached.
Dates in your own format
Date, Time and DateTime custom property values are shown and picked in your workstation's
own convention: field order, separators and the 12- or 24-hour clock. What is stored in the file
stays canonical ISO, so a date means the same instant for every colleague, whichever format each
of them sees.
Other fixes in this release
| Fix | What you would have seen |
|---|---|
| Mapping diagrams | Right-clicking an attribute row now offers Show Properties; the menu used to come up empty |
| Entity forms | Incoming mappings keep a stable order instead of moving between opens |
| References | A reference could briefly fail to resolve while its document was being rebuilt |
| Model Explorer | A stored tree state could be written in a form that wiped the layout on the next open |
CrossModel Professional v1.12.4
Upgraded 17 September 2026, 22:00 CET.
A fix release, from v1.12.0 to v1.12.4. No new features, and nothing to do.
| Fix | What you would have seen |
|---|---|
| Forms | A reference field no longer wipes its value when you click away from it. This is the one you are most likely to have noticed |
| Scope | Data models that could not be resolved no longer leak into every other model's scope |
| AI chat | A trailing assistant message is dropped before the model is asked again, which is what made some runs stop with a gateway error |
| Mappings | Attributes inherited from a type definition resolve on a cold build |
| Sessions | Memory defaults tuned, and the workbench survives a websocket reconnect without losing or reordering your changes |
CrossModel Professional v1.12.0
Upgraded 7 September 2026, 22:00 CET.
The hosted environment moved from v1.5.3 to v1.12.0. That covers seven releases, so this page collects everything you are likely to notice. Nothing you have modelled changes: existing workspaces, models and Git history open exactly as before.
Build target attributes by dragging
Mapping diagrams gained a Create Attribute tool. Drag one or more source attributes onto the target entity and CrossModel creates the matching target attributes and their mappings in a single gesture, instead of you creating each attribute by hand and then wiring it.
Where a name already exists on the target, an Attribute Name Conflict dialog lists every clash and lets you resolve them one at a time or in bulk: map to the existing attribute, create a new one, or skip it.
See Mapping Fundamentals.
Tidier diagrams
Two changes, one you ask for and one you simply get.
Routing points let you override an automatic route. Select a relationship line, drag the handle that appears at its midpoint, and the bend becomes a fixed point the line must pass through. Routing points are part of the model rather than a per-session view setting, so they are saved into the diagram file and your colleagues see the layout you arranged. Remove them with ++delete++, or with Remove All Routing Points from the line's context menu.
Edge routing has been rewritten. Lines are now straight wherever a straight line is possible, take fewer corners when they cannot be, and where several lines run together they are separated rather than drawn on top of each other. This is most obvious on mapping canvases with many attribute lines, which are considerably easier to read. Your existing routing points are honoured exactly as before.
See Datamodeling Fundamentals.
Large mappings open quickly
Opening a large mapping used to take tens of seconds and could stall while the diagram settled. A mapping with a thousand target attributes now opens in a few seconds, and its Form Editor tab appears immediately rather than after a pause. Diagram routing that previously took seconds on a busy canvas is now effectively instant.
AI assistant budget
The AI chat toolbar now shows what you have spent against your budget, turns red once you pass a threshold, and can notify you when you cross it. The budget is yours: each user's environment is provisioned with its own key rather than sharing one. The chat also reports how much of the context window a conversation is using.
Three settings control the indicator, under Settings:
| Setting | Default |
|---|---|
ai-features.chat.budgetUsageIndicator.enabled |
true |
ai-features.chat.budgetUsageWarning.enabled |
true |
ai-features.chat.budgetUsageWarning.defaultThresholdPercentage |
80 |
Property templates
A type definition can now derive a value rather than only supply a fixed one. Give a
definition a property template such as {{entity.name}} Key for name, and every instance that
adopts the definition and does not set its own name gets one worked out from its context.
Templates are available for name and description, and they travel down the extends chain,
so a child definition can override a parent's.
See Extending the Metamodel with Type Definitions.
Custom property data types
Custom properties gained a Unit field for Duration values, offering milliseconds through
years, so a retention period of 7 can say that it means years. The field is only enabled for
Duration.
Values are also checked against the data type they claim to be, and that checking now covers
UUID and Duration alongside the types already validated. A malformed UUID or a fractional
duration is reported in the Problems panel rather than being accepted silently. Note that a
value is re-checked against whichever type the field currently holds, so changing a property's
data type can surface an error about a value you entered earlier.
See Extending the Metamodel with Type Definitions.
Conceptual data models
You can now model at the conceptual tier: the things the business cares about and how they relate, before anyone decides how they are stored.
A conceptual model is an ordinary data model whose Type is Conceptual. Its entities carry a
name, a description and attributes, and deliberately no datatypes and no lengths, because a
datatype is a decision for the logical tier. Each logical entity can then record which concept it
implements through a Realizes field, so one agreed definition can be realised by many systems
and you can ask which.
Conceptual models are authored through the Model Explorer and the form editor. As of v1.12.0 there is no conceptual diagram; that is planned for a future release.
A preview, released officially in v1.19.4
This first version of the conceptual tier was a preview. Conceptual modeling was released officially in v1.19.4, with conceptual diagrams.
See Conceptual Modeling and A conceptual model linked to a logical one.
Changes to your session
These come from the hosting platform rather than the application, and all three are things you would have felt.
Sessions are no longer stopped while you are working
A running session could previously be stopped after four hours even if you were in the middle of using it, because activity was not being tracked. Activity is now tracked properly:
- A session you are actively using is never stopped, however long you work.
- An idle session warns you after 55 minutes and stops after 60. Both were shorter before, so a long meeting or lunch no longer costs you your session.
A stopped session is not lost work: your files live in the workspace, and starting it again brings them back. Note that a workspace you stop and start opens on the welcome page, whereas simply reloading a running session restores the editors you had open.
Commits carry your identity
Commits made from inside the workspace now use your name and email automatically. You no longer have to configure a Git identity by hand before your first commit.
See Git Provider Authentication.
More reliable sign-in
Signing in with a social account, such as Microsoft, could fail while username and password sign-in kept working. The cause has been fixed, and sign-in is now pinned to a single server for the whole exchange so a momentary hiccup cannot interrupt it.
Smaller fixes
| Fix | What you would have seen |
|---|---|
| Id uniqueness | A document could report that its own id was not unique |
| System diagrams | Nodes and edges could be given colliding ids |
| AI chat | Safer handling of the context and change-set views around unstaged changes |