Date: Thu, 28 Mar 2024 14:24:46 -0500 (CDT) Message-ID: <292599455.38715.1711653886405@kodak01.contegix.mgmt> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_38714_1198319238.1711653886375" ------=_Part_38714_1198319238.1711653886375 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
One problem with handling exceptions is that the name of the rul= e set is not readily available the way the name of the rule is. As a result= it may not be obvious which rule set an exception is originating in. With = the introduction of rule set variables it is now possible to create a strin= g rule set variable that contains the name of the rule set. The name of the= rule set can then be included in the logging of the exception by referenci= ng the rule set variable.
To create a string rule set variable that contains the name of a rule se= t:
Rule_Set_Name
.=
li>
Anywhere an exception is logged or reported, the #Rule_Set_Name variable can now be referenced to include the name of the rule set.
For example, to include the rule set name in an email subject line, the = Subject parameter of the Send Email actio= n could be:
Rule set: %#Rule_Set_Name% rule: %triggerEvent.RuleName% failed
A limitation of this approach is that you are responsible for keeping th= e value of the variable accurate because the name of the rule set stored in= the variable does not get updated automatically when the rule set is renam= ed or copied.