MDL syntax to disable/enable individual activities in microflows and nanoflows

[acarum]

Studio Pro allows marking any activity as disabled (right-click → Disable) — the activity remains in the flow but is skipped at runtime. There is currently no MDL equivalent for this flag.

Use case: when an activity cannot be correctly configured via mxcli (e.g. the RefreshEntity entity-type parameter bug), the only safe workaround would be to generate the activity in a disabled state and let the developer re-enable it after fixing it manually in Studio Pro. Without this, the generated
nanoflow either ships with a misconfigured active activity or requires the developer to manually delete and recreate it.

Proposed syntax:
CALL JAVASCRIPT ACTION NanoflowCommons.RefreshEntity (
EntityToRefresh = CustomModule.BufferDefinition
) DISABLED;

Or as a statement modifier consistent with existing MDL style:

-- @disabled
CALL JAVASCRIPT ACTION NanoflowCommons.RefreshEntity (
EntityToRefresh = CustomModule.BufferDefinition
);

Expected behavior: mxcli should write the activity with the disabled flag set, so it appears in Studio Pro as a greyed-out step that can be re-enabled without losing its configuration.

• mxcli version: (0.22.0)
• Mendix version: 11.12.4

[github-actions]

Issue Triage

Summary:
The request is for a way to mark individual activities as disabled in MDL so that mxcli‑generated flows can include greyed‑out steps that developers can later re‑enable in Studio Pro.

Checklist for feature request

Required info	Present?	Details
Use case – why the feature is needed	✅	Described: need to generate activities in a disabled state when they cannot be correctly configured via mxcli (e.g., RefreshEntity entity‑type bug).
Proposed syntax or behavior	✅	Two options shown: … DISABLED; or a statement modifier -- @disabled.
Mendix version relevance (if version‑specific)	❌	Not mentioned whether the feature depends on a particular Mendix version.

What’s missing
Please let us know which Mendix version(s) you target with this feature (e.g., does it apply to Mendix 9.x, 10.x, or all recent versions?). If the feature is version‑agnostic, a brief note confirming that would be helpful.

Thank you for the clear use case and proposed syntax! Once we have the version information, we can consider the request complete.

---

Automated triage via OpenRouter — workflow source