Naming conversions for public and private microflows

0
When developing modules or units of logic what is the best way to demarcate between microflows that are built so that they can be re-used elsewhere in the system (public microflows) and private ones that should only be used within the encapsulated logic and not for use outside the module or unit?    Is the best way only via naming conventions or can you restrict functionality in any way? 
asked
1 answers
1

We allways put such microflows in a seperate folder.

Regards,

Ronald

 

answered