Sunday 29 June 2014

Mendix abbreviatens / prefix types for Microflows

There is no standaard for name convention of microflows within Mendix. During the time there are some best-practises about using name convention of the microflows.  Below there is a list of microflows name convention for the different type of microflows.  


Prefix typeMeaningComment
AD_After Delete
BD_Before Delete
ACr_Before create
BCr_Before create
ACo_After commit
BCo_Before commit
IVK_Invoke
VA_Visual AttributeThese microflow have visual attributes as output/return
OC_On Change(do not use, use OCh)
OCh_On Change
DS_Data SourceThis microflow returns an Object or a lijst of Objects as Output/return
SE_Scheduled Event
EVT_Event handlersThese microflows are attached to Event handlers
NAV_NavigationCalled from navigation (menu item)

Tips:





  • Name convention:
    • MF triggers by an action : <prefix type>_<action to execute>
    • MF that does something: <action to execute>
  • When you have a MF which is called by VA_ and OCh_, then the following:
    • MF should be created with name <action to execute>
    • VA_ --> Call MF <action to execute>
    • OCh_ --> Call MF <action to execute>
  • No comments:

    Post a Comment