Page button microflow call: support MicroflowSettings configuration

[engalar]

Problem

When calling a microflow from a page button (ACTIONBUTTON), all MicroflowSettings are hardcoded to defaults in the BSON writer. Users cannot configure progress bar, async execution, form validations, or confirmation dialogs.

Current behavior

ACTIONBUTTON btnProcess (
  Caption: 'Process',
  Action: MICROFLOW Module.ACT_DoSomething(Product: $currentObject)
)

Hardcoded in sdk/mpr/writer_widgets_action.go:

• ProgressBar: "None"
• Asynchronous: false
• FormValidations: "All"
• ConfirmationInfo: nil
• DisabledDuringExecution: true

Expected behavior

Allow configuring these settings in MDL syntax, e.g.:

ACTIONBUTTON btnProcess (
  Caption: 'Process',
  Action: MICROFLOW Module.ACT_DoSomething(Product: $currentObject) (
    ProgressBar: Blocking,
    ProgressMessage: 'Processing...',
    Asynchronous: false,
    FormValidations: All,
    Confirmation: (
      Question: 'Are you sure?',
      ProceedCaption: 'Yes',
      CancelCaption: 'No'
    )
  )
)

Scope

Requires changes across 5 layers:

Layer	File	Change
Grammar	MDLParser.g4	Add settings syntax after microflow args
AST	mdl/ast/ast_page_v3.go	Add settings fields to ActionV3
Visitor	mdl/visitor/	Parse settings from parse tree
PageBuilder	mdl/executor/cmd_pages_builder_v3.go	Pass settings to pages model
BSON Writer	sdk/mpr/writer_widgets_action.go	Use actual values instead of hardcoded defaults

Available settings in Mendix

Setting	Type	Values
ProgressBar	enum	None, NonBlocking, Blocking
ProgressMessage	translatable string	custom text
Asynchronous	bool	true/false
FormValidations	enum	All, None
ConfirmationInfo	object	Question, ProceedCaption, CancelCaption
DisabledDuringExecution	bool	true/false

[github-actions]

Issue Triage

Summary:
The issue requests adding support for configuring MicroflowSettings (progress bar, async execution, form validations, confirmation dialogs, etc.) when calling a microflow from an ACTIONBUTTON in MDL.

Checklist for feature request:

• ✅ Use case / problem it solves – described in the “Problem” section.
• ✅ Proposed syntax or behavior – shown in the “Expected behavior” MDL example.
• ❌ Mendix version relevance – not specified (is this needed for all Mendix versions or only certain ones?).

What’s missing:
Please let us know which Mendix version(s) this feature should target (e.g., 9.x, 10.x, or all versions). If it applies universally, a brief note to that effect would be helpful.

Once we have that detail, the request will be complete. Thanks for the thorough description!

---

Automated triage via OpenRouter — workflow source