I’m failry familiar with the notification service and in the past I’ve looked to modify in the same way. Essentially, I wanted to dynamically fill some of the lines with relevance, pulling the “to” field dynamically from a custom setting (server owner) on the cleint.
However, the notification service template needs to be filled eaxactly to the template, and the already avaialble variables are catered for specifically in the java script when it picks this up. So its not possible to add your own variables without modifying the java app which the notification service is based on.
I also anticipated issues when a large group of servers is targeted, and there is the same owner for multiple servers - they would get flooded with one email for each of the servers int he baseline.
At thsi point, I looked down an alternative route using Webreport’s notification service, and the triggers and variables avaialble there.
However, I did think of an idea arround this, using the REST API.
Essentially, you could have session relevance lookign for sepcific content, in this case the Baselines, and have it trigger an action through the API to generate the notification taks drectly ont he BigFix server, which follows the formatting of the template.
Because you are generating the task on the fly, you could use variables in the building process, which outputs exactly the lines and format that the java app is expecting. This way, you could also account for duplicates, and have a single email cater for multiple servers.
On the face of it, it sounds doable, however I may be over simplifying it a little, so I would anticipate some hurdles that I’ve not thought of if you wanted to go down that route.
Triggering an action over the API is fairly easy, and the session relevance for the trigger should also be fairly straig forward. However the dynamic creation of the action may need fome fettling to get right
Another issue woudl be that, when targeting a large group of servers with a Baseline with multiple server owners within it, you ideally need one email notification for each unique server owner, unless you copy everyone into a single mail (which is supported by the notification service). But then you end up with a fairly long list of “to” emails, and the body would then need to be a consolidated list of all those servers and success/failure, which actually is no better than a simple automatically generated report in WebReports.