Custom BAM revisited

Carlo adds to my previous blog on custom BAM, that it is of course possible to combine these techniques with the things that are provided by the TPE (Tracking Profile Editor).  Thanks for pointing this out Carlo.

Even better: I would suggest using the TPE for whatever it can provide you!  The described techniques are only useful if the out-of-the-box tools don't fit your needs.  (As always: custom code requires your own support, maintenance, deployment, testing, ... while anything out of the box is supported by a great team of specialists, available 24/24h, 7 days a week.  You got my point.)

If even the suggested approach does not fit your BAMming needs, don't worry: BAM has even more advanced API's! 

Just as the orchestration engine does, it is possible to "instrument" your own orchestration steps and .NET code with BAMmable data.  This can be done by what is called the "BAM interceptor".  (Same object as the orchestration engine internally uses.)  The main advantage of this (way more advanced) technique is that you may configure the BAM needs afterwards.  (While in what I explained previously in the BAMming blog entry, you kind of "hardcode" what is BAMmed exactly to which kind of activity items...) 

So if you'd like to create your own TPE: go ahead, it's all possible! Just let me know if you succeeded please :-))))