Artifact Labels — App-Level Categorization Tags for Microflows, Nanoflows, Pages and Snippets

The Problem

As Mendix projects grow, developers lose visibility into why an artifact exists and how it relates to others — especially across modules.

The two tools we currently rely on both fail at this:

• Naming has a limit on clarity. You cannot encode context, ownership, risk, or cross-module relationships into a name without making it unreadable
• Documentation field is free-text, unstructured, written differently by every developer, and most critically — not filterable
  

There is no structured, searchable way to categorize artifacts across an application today.

!! The Solution — Artifact Labels !!

A controlled tagging system defined at the App Settings level.

• Only admins or lead developers can create and manage labels in App Settings — no developer can invent their own tags, keeping the vocabulary clean and consistent
• Developers can apply existing label or lables to any microflow, nanoflow, page, or snippet
• Labels are visible on the artifact without opening it
• A dedicated Labels Pane — similar to the existing Console, Errors, or Debugger pane — lets developers filter and navigate the entire app by label, including across modules

Why Names and Docs Cannot Do This

Names describe what something does. Documentation describes how. Neither answers:

• Which artifacts belong to the same integration flow across 3 modules?
• Which microflows are owned by Team A vs Team B?
• Which artifacts are sensitive and need extra care before modifying?

Labels answer all of these — instantly, consistently, without opening a single artifact.

Real Scenarios Where This Matters

• Cross-module tracing — A Payment Sync flow spans 3 modules. Label all related artifacts Payment-Sync and filter the entire app in one click. Today there is no clean way to do this.

• Team segmentation — Large teams split into squads. Labels like Team-SAP or Team-Frontend make ownership visible inside Studio Pro without restructuring modules or relying on verbal handoffs.

• Integration risk — Label microflows that call external systems External-API or DB-Sync. Any developer touching them immediately knows these are sensitive — before they open it.

• Cross-team communication — A senior developer needs to signal that an artifact is incomplete or under review. A label does this instantly, without a Confluence page or a Jira comment nobody reads.

!! NOTE: Labels are purely informational. No runtime impact. No enforcement. Just structured visibility at scale.