Feature Request: New keyword for logging debug messages
Hello,
I created a Feature Request ticket a while ago (currently still under pm review) and I'm wondering whether other integrators/developers would also like to see such a feature added?
New Keyword:
LogTroubleShootingEvent[MessageType, Message, AdditionalMessage*]
This keyword logs the given message within the standard "Troubleshooting Event" logs. The keyword logs "Information", "Warning" and "Error" messages. The "Information" messages will only be logged when the metadata "Live Trace Enabled" has been enabled for the BR.
Parameters:
-
MessageType – Predefined list of possible options: "Information", "Warning", "Error" (or, "I", "W" or "E"). The given value determines the "Message Code" value which is used/logged. For example the codes could be: "B0001", "B0002", "B0003". Obviously the codes will have to be reviewed and approved by the Architects/Engineers.
-
Message – The main message to be logged.
-
AdditionalMessage* – Optional additional message to be logged (appears in the Additional Message column within the trace logs). Can be left blank.
The entry that gets created in the logs, should also include the existing information similar to the other messages, "entity", "business rule", "context", "timestamp", etc.
Return Value: The keyword should have a “Boolean” return value, “True” the message was logged, “False” the message wasn’t logged.
The main reason for the return value is so that the keyword can be seamlessly linked (AND/OR) with all other keywords.
The original request can be seen here (not sure if those outside of my organization can access it or not):
https://riversand.atlassian.net/servicedesk/customer/portal/13/EX-41827
Please sign in to leave a comment.
Comments
0 comments