I have a solution where I use BAM to build a complete audit trail of a message flow.
Custom components write a message to a predefined BAM view whenever you want it to. Normal points where you would use
this functionality is in receive & send pipelines. And if an important business decision was made you could write that to the
audit trail as well. Below is an example of how to do this in an expression shape inside an orchestration.
AuditData(XlangMessage,"The order was rejected because of <Some reason>",bool includeMessage)
By doing it like this you can have a very nice Audit trail for every BizTalk solution without doing too much for it. I was very happy with the Audit trail
created by the applications that used the custom BAM solution. However a person dealing mainly with functional support would want some
added functionality. The wish to add functionality to an entry in BAM stayed in the back of my head and after a while I read a very good article by Gregory van de Wiele
and thought it would be nice to indeed have links that really worked.
After applying his tips I was able to add some extra functionality to the BAM page. Below is an example of this.
- View Audit trail in Audit portal is a hyperlink that will jump to a website that is designed to show an audit trail of a message.
- View Errors in FaultPortal (If any) will show all the errors that have occurred.
- View entire message will use Gregory's tip and show you the entire message. (the field longreferencedata contains the