Heey Ladi,
What i have seen across multiple projects is that when the ACT prefix is used for a microflow it means that it is being called from a button on a page. So not every microflow within your app should have the ACT prefix. Only the ways that are being called directly from a button. This also means that only these microflows need to have roles configured for it.
Kind regards,
Edo
It is a naming convention that Mendix recommends.
You can see it here https://docs.mendix.com/refguide/dev-best-practices/#343-page-based-microflows
Huy
Hi Ladi,
Using Prefixes can easily understand its purpose by looking at the microflow name itself
Check out the Best Practices: https://docs.mendix.com/refguide/dev-best-practices/
Hi Ladi,
"ACT" is used for Page-Based Microflows like Menu item, navigation item, microflow and action button, drop-down button.
Kind regards, Raphael
Hi Lady,
So it is basically a naming convention you can checkout the mendix docs related to naming convention.
When you performing some action using button suppose on the newEdit page save button you are committing objects. So Naming will be
Action button -> ACT_Save
onChange -> OCH_AnythingName
DataSource -> DS_AnythingName
For more you can checkout the mendix docs.
Hope you like the answer