MF / NF Calls - Optional Parameters Mapping Update - Mendix Forum

MF / NF Calls - Optional Parameters Mapping Update

33

Hi,

 

With the new addition of optional parameters I think Mendix needs to revisit how parameters are shown when calling a Microflow / Nanoflow / (soon to be Page).

 

- A way to properly order parameters (instead of by order of adding to the flow).

- Separate out Required / Optional parameters (At the minute the list is joint and not easy to tell apart).

- Show default values for optional parameters.

- Ability to see the parameter description / documentation.

 

This is only going to get more complex with primitive parameters for pages as well and really needs reworked.

 

Thanks,

Adam

 

asked
4 answers

Hi John,


I've seen the update and showing if the mf param is optional / required is definitly a good step.


Sorry my post wasn't very clear, I meant for it to be a bit more focused on from where the microflow is being called from. Eg sub microflow call or calling a mf from a page.


  1. Currently if I call a microflow I can't see what are optional / required params and what there default values are. You have to open the mf to and click through the params to see them.
  2. The ordering can't be controlled / might be an idea to split out required / optional params
  3. Documentation could be viewable from this page as a tool tip or something.


See the example of my SUB_Log:

  • The commit is an optional param with default true. It has documentation saying "Use this to commit the object in the sub microflow, or ignore the commit to add it to a list of toCommit_Log in your main flow for performance optimisation"
  • The detail is optional with empty value
  • The RecordedAt is optional and default to CurrentDateTime

But these details aren't immediatly available


Thanks,

Adam

Created

Thanks for the feedback! From SP 11.11 onwards we visually distinguish between required and optional parameters, so this should be a bit easier now.


Good suggestions regarding showing the default value and/or documentation field - would you see this as a tooltip on hover? Something else? There are UX considerations to keep things visually simple, but understand users have a need to see more at a glance.

Created

Bumping this to hope it gets more traction, I'm still constantly struggling to do sub mf calls without opening the sub mf to see exactly what is optional / what default values there are

Created

Agree.

Created