Overview

This module will give you a few microflows to standardize your logging. Most importanly it will add the microflow path to the location in your log, with this you will always be able to originate where your log comes from. 

Documentation

This module will give you a few microflows to standardize your logging. Most importanly it will add the microflow path to the location in your log, with this you will always be able to originate where your log comes from. 

Dependencies:

Module: StringEditing

Module: CommunityCommons

How to implement:

Implement by import this module into your project and use the following microflows instead of the Mendix 'Log message' activity: 

- NOP_Error_LogErrorMessage 

- NOP_ErrorString_LogFunctionalMessage  

- NOP_HttpResponse_LogErrorMessage

NOP_Error_LogErrorMessage is specifically made to log Error object information, and should be used in custom error behavior.

NOP_HttpResponse_LogErrorMessage can be used for error handlers for an external calls (e.g. REST).

NOP_ErrorString_LogFunctionalMessage can be used for all other situations you would want to log messages.

A good implementation uses an interface (= a microflow in your own module which calls one of the above microflows). For Nanoflows this is essential, as the microflow would need access rights otherwise)

Debug and trace are not supported by this module.