Mario, I want to make sure I understand you correctly. In your SQL tags, do you have separate tags, on which you are setting up alarming, for each project?
if so, then the method I described will work. I just tested it. And Robert, whenever I create a new alarm, the DisplayPath property is blank, and if you use it in the alarm email subject or message, it will show as null. So I see no reason why it couldn’t be used for a switch statement. But if that is not something we should be doing, then there is another way, which I also tested.
You can set up a custom parameter in the alarming properties of the tag on which you are setting up alarming. Below is a custom property named Project, which I have set, in this example to the expression of “ProjectB”.
[attachment=1]Capture.JPG[/attachment]
Now, you can set your switch in the pipeline to switch on this Project property and it will pick the appropriate pipeline. To select the Project property in the switch block, you just put curly braces around it in the expression section, as shown below.
[attachment=0]Capture.JPG[/attachment]
I tested this and if I change the Project property value to “PropertyA” or “PropertyC”, it selects the appropriate notification block via the switch.
One other thing that I could not find in the documentation anywhere is the Custom Subject and Custom Message in the alarm properties. You can set these to whatever you want, and then in the notification block, you can set the subject and/or message to use these properties by enclosing them in curly braces, making the c in custom lower case, and removing the space between words, as in {customSubject}.