The properties panel is the right-side pane of the MC Modeler editor. Select any BPMN element on the canvas and the panel immediately populates with that element’s editable attributes. Every change you make is applied to the canvas in real time — there is no save button in the panel itself; the diagram auto-saves in the background.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Aston2710/mc-modeler/llms.txt
Use this file to discover all available pages before exploring further.
Opening and Closing the Panel
Open by selecting an element
Click any element on the canvas. The properties panel opens automatically and shows that element’s attributes.
Toggle with the collapse button
Click the ▷ button on the panel’s left edge to collapse it, freeing up canvas space. Click ◁ to re-expand it. The toggle state is reflected in
UIState.propertiesPanelOpen.Panel Header
When an element is selected, the panel header shows:| Area | Content |
|---|---|
| Type icon | Colored square icon matching the BPMN element category (blue for tasks, green/red for events, yellow for gateways) |
| Type label | Uppercase label of the exact element type, e.g., USER TASK, EXCLUSIVE GATEWAY |
| Name | The element’s current name in bold — click to edit inline |
| ID | The auto-generated immutable ID in monospaced font, e.g., Task_3f2a1b |
Common Properties (All Elements)
Every BPMN element exposes these three properties regardless of type:ID
Read-only. Auto-generated on element creation in the format
{Type}_{shortUUID}. Used internally to link flows, boundary events, and cross-references. Never editable by the user.Name
Editable text field. Displayed as the element’s label on the canvas. Optional on all elements except pools (where it is strongly recommended). Changes appear on the canvas character by character as you type.
Documentation
Editable long-text area. Free-form notes or descriptions attached to the element. Stored as
bpmn:documentation in the exported XML, so the content is preserved when opening the file in Bizagi or Camunda.- General — ID, Name, and element-specific fields (see below).
- Documentation — The full-width
documentationtext area.
Element-Specific Properties
Tasks
When a task is selected, the General tab shows a Task type dropdown that lets you morph the element into any task sub-type without deleting and recreating it:| Task type | BPMN type | Icon marker |
|---|---|---|
| Generic task | bpmn:Task | (none) |
| User task | bpmn:UserTask | 👤 person silhouette |
| Service task | bpmn:ServiceTask | ⚙ gear |
| Script task | bpmn:ScriptTask | ≡ script lines |
| Send task | bpmn:SendTask | ✉ filled envelope |
| Receive task | bpmn:ReceiveTask | ✉ empty envelope |
| Business rule task | bpmn:BusinessRuleTask | 🏛 table grid |
Changing the task type in the properties panel is equivalent to using the morph option in the context pad. Both update the
bpmnType stored in the XML immediately.Events
For start, intermediate, and end events, the panel exposes an Event definition type selector that attaches or changes thebpmn:EventDefinition child element:
- Start events
- Intermediate events
- End events
| Event definition | Description |
|---|---|
| None | Plain start — no trigger |
| Timer | bpmn:TimerEventDefinition — time-based trigger |
| Message | bpmn:MessageEventDefinition — receives a message |
| Signal | bpmn:SignalEventDefinition — receives a broadcast signal |
| Conditional | bpmn:ConditionalEventDefinition — condition becomes true |
Gateways
For gateways the panel shows a read-only Gateway type indicator confirming the current type (Exclusive XOR, Parallel AND, Inclusive OR, Event-based, Complex). To change the gateway type, use the Change type option in the context pad — this prevents accidental type swaps, since the routing semantics differ significantly between gateway types.Pools and Lanes
| Property | Behavior |
|---|---|
| Name | The pool or lane label displayed in the header strip. Edited inline. Required for pools that represent named participants. |
| Documentation | Free-form notes. |
Sub-processes
Collapsed / Expanded toggle
Switch between the collapsed view (small task with + icon) and the expanded inline view. When expanding, the sub-process grows to its expanded default size (90 × 60 px base, then resizable).
Linked sub-diagram
A sub-process can optionally link to a separate diagram stored in the project. This lets you navigate into the detail diagram from the parent canvas. The link stores the
parentDiagramId and subProcessElementId reference in the Diagram metadata.Image Badge Feature
Any flow element (task, event, gateway, etc.) can have one or more library images attached to it as a visual badge. The badge is rendered directly on the element in the canvas byImageBadgeModule.
Open the image picker
Select an element on the canvas. In the context pad, click the image-link icon (or use the Link image button in the properties panel). This opens the Image Picker modal.
Choose an image from the library
Browse or search your image library. Select the desired image. The link is stored in the element’s
flujo:linkedImages extension attribute in the BPMN XML — image bytes are never embedded directly in the element.Badge appears on canvas
The selected image appears as a small badge overlay on the element. Multiple images can be linked to the same element.
Images are stored by reference (
storage://diagram-images/... in cloud mode, local://<id> in local mode). The BPMN XML file stores only the image ID, keeping the diagram file lightweight. When exporting to .bpmn or .bpm, the inlineImages utility resolves references to base64 data URLs so the exported file is self-contained.Real-Time Synchronization
Every field change in the properties panel is applied instantly:Ctrl+S.