Condition Settings

Use the Conditions page to define conditions for a rule. When the conditions become true based on changes in the system, a notification is generated.

The following settings are available on the Conditions page:

Title
Provide a name for the rule. The name should clearly indicate the rule's purpose so it can be used by multiple notifications, if applicable.
Workflow/Auxiliary Table
Indicates the workflow or auxiliary table for which the rule is defined.
Override
Rule modifications made at a child workflow level are considered overrides. In this case, you can modify conditions for the rule, but you cannot change the name or workflow assignment. For details, refer to Inheritance Guidelines.

Conditions

The following options are provided for defining conditions.

Option	Description	Example
Operator	Use to join two or more conditions together.	A rule becomes true when any item is closed and the resolution was a software change. Object = Any Item Comparison = Is Value = Closed Operator = And Object = Resolution Comparison = Is Equal To Value = Software Change
Open Parentheses	Use to set the precedence of conditions.
Object	Use to select which data will change to determine when the rule becomes true. Primary and auxiliary items are specified in the Object list as Any (primary or auxiliary item name), such as in Any issue or Any company. Most objects in the list are generated from the fields associated with the selected workflow or auxiliary table. The non-field object Attachment is included, however, to allow notifications to be sent when attachments are added to or deleted from an item, including attachments added to Text fields using the Rich Text Editor. Note that attachments include notes, e-mail messages, files, URLs, and item links. The "Any Paused/Unpaused Issue" operator is a non-field object that you can use to build rules for items that are paused or unpaused from. Note that this operator is available even if you do not add the Pause Status system field to your primary table in SBM Composer. The "Transition" operator is a non-field object that you can use to send notifications when a certain transition occurs. For example, to send a notification when the Close transition occurs, select the "Transition" operator, the "Is" comparison, and the "Close" transition from the value drop-down list.	A rule becomes true when the estimated time to fix an issue is more than five days. Estimated Time to Fix is a field associated with the selected workflow and contains a date/time value. Object = Est. Time to Fix Comparison = Is Greater Than Value = 120:00:00 The date/time value stored in the Estimated Time to Fix field for the issue is compared with the value 120:00:00. If the date/time of the Estimated Time to Fix field is more than 120:00:00 hours, a notification is sent.
Comparison	Use to evaluate the selected object and selected value. Comparisons that appear in the list are determined by the type of field selected as the object. For details, refer to Condition Comparisons.	A rule becomes true when the priority of an incident changes to critical. Object = Priority Comparison = Changes To Value = Critical
Value	Used to compare the selected object and the selected value. For most field types, a value is selected from the list. You must type the exact comparison value for Text, Single Relational, Multi-Relational, Numeric, and Summation fields, as well as Sub-Relational fields based on those field types. Text entered for comparison values must be case sensitive.	A rule might have the conditions that when the state of an item changes to resolved and the submitter of the item is a particular user, a notification is sent. Object = State Comparison = Changes To Value = Resolved Operator = And Object = Submitter Comparison = Is Equal To Value = <Current User>
Closed Parentheses	Use to set the precedence of conditions.

Add
After specifying an object, comparison, and value for each condition, click Add to add it to the rule.
Move
Select a condition, and then click the Move options to reorder conditions as needed.
Modify
Select a condition, change the object, comparison, and value as needed, and then click Modify.
Remove
Select a condition, and then click to remove it from the list.

Condition Comparisons

The following table describes each of the available comparisons, lists the applicable field types, and provides an example of how to use each comparison.

Note: Unless noted in the following table, comparisons for Sub-Relational fields are based on sub-fields. For example, the applicable comparisons for a Sub-Relational field with a Single Selection as its sub-type are the same as those for Single Selection fields.

Comparison	Description	Field Types	Example
Added	Becomes true if the new value of an object contains the item selected in the Value list and the previous value did not.	File, Multi-Group, Multi-Selection, Multi-User, and URL.	Object = Change in Version(s) Comparison = Added Value = V4.5 A notification is generated when the value V4.5 is added to the Change in Version(s) field.
Added to Backlog	Becomes true when items are added to a specific backlog in SBM Work Center.	Any Item object (Primary items only)	Object = Any Work Item Comparison = Added to backlog Value = Sprint 1 Backlog A notification is generated when any work item is added to the Sprint 1 Backlog.
Changes	Becomes true when the selected object's value changes.	Binary/Trinary, Date/Time (except Elapsed Time), File, Folder, Multi-Group, Multi-Relational, Multi-Selection, Multi-User, Numeric, Single-Relational, Single Selection, Text, URL, and User. Also Any Item, Note, and Attachment objects.	Object = Owner Comparison = Changes A notification is generated when the owner changes for an item.
Changes From	Becomes true when a new value for the object changes from the selected value.	Binary/Trinary, Folder, Multi-Relational, Single-Relational, Single Selection, Text, and User	Object = Engineer Comparison = Changes From Value = Laura Engineer A notification is generated when the value of the Engineer field changes from Laura Engineer to another value.
Changes From (None)	Becomes true when a field is given a value after it had no selected value.	Binary/Trinary, File, Folder, Multi-Group, Multi-Relational, Multi-Selection, Multi-User, Numeric, Single Relational, Single Selection, Text, URL, and User.	Object = Customer Comparison = Changes From (None) Value = ACME A notification is generated when the Customer field is given a value.
Changes To	Becomes true when a new value for the object changes to the selected value.	Binary/Trinary, Folder, Multi-Relational, Single-Relational, Single Selection, Text, and User	Object = Engineer Comparison = Changes To Value = Laura Engineer A notification is generated when the value of the Engineer field changes to Laura Engineer.
Changes to (None)	Becomes true when all values are removed from a field.	Binary/Trinary, File, Folder, Multi-Group, Multi-Relational, Multi-Selection, Multi-User, Numeric, Single Relational, Single Selection, Text, URL, and User.	Object = Targeted Release Comparison = Changes To (None) With this condition, a notification is generated when a value is removed from the Target Release field. This may indicate that a work item is no longer planned.
Changes to Paused	Becomes true when an item's Pause Status changes to Paused.	"Any Paused/Unpaused Issue" object.	Object = Any Paused/Unpaused Issue Comparison = Changes To Paused Value = Paused by Demand Manager A notification is generated when the value of the Pause Status field changes on an item to Paused.
Changes to Unpaused	Becomes true when an item's Pause Status changes to Unpaused.	"Any Paused/Unpaused Issue" object.	Object = Any Paused/Unpaused Issue Comparison = Changes To Unpaused Value = Approved by Demand Manager OR Value = Rejected by Demand Manager A notification is generated when the value of the Pause Status field on an item changes to Unpaused because the item is approved or rejected.
Contains	Becomes true if the current value of an object contains the selected value. This condition is evaluated for any records indicated as a change in the change history.	File, Multi-Group, Multi-Relational, Multi-Selection, Multi-User, Single-Relational, Text , and URL	Object = Description Comparison = Contains Value = XML A notification is generated when an item that contains the term "XML" in the Description field changes.
Deleted	Becomes true when a value is removed from a field.	File and URL	Object = File Comparison = Deleted A notification is generated when a file is removed from a field.
Is	Becomes true if the specified change is made to an item, or when the Transition operator is used, and the selected transition is executed.	Any Item, Note, and Attachment objects, and Transition objects	Object = Attachment Comparison = Is Value = Added A notification is generated when an attachment is added to an item. Or: Object = Transition Comparison = Is Value = Close A notification is generated when the close transition is executed.
Is (None)	Becomes true when the object has no specified value.	Binary/Trinary, File, Folder, Multi-Group, Multi-Relational, Multi-Selection, Multi-User, Numeric, Single Relational, Single Selection, Text, URL, and User	Object = Customer Priority Comparison = Is (None) A notification is generated when the Customer Priority field does not have a value.
Is Not (None)	Becomes true when the object is given a value.	Binary/Trinary, File, Folder, Multi-Group, Multi-Relational, Multi-Selection, Multi-User, Numeric, Single Relational, Single Selection, Text, URL, and User	Object = Approver Comparison = Is Not (None) A notification is generated when a user is selected in the Approver field.
Is Equal To	Becomes true when the value of the object is equal to the selected value.	Binary/Trinary, Date/Time, File, Folder, Multi-Relational, Numeric, Single-Relational, Single Selection, Summation, Text, URL, and User	Object = Issue Type Comparison = Is Equal to Value = Bug Report With this condition, a notification is generated when an item changes and the value in the Issue Type field is Bug Report.
Is Greater or Equal	Becomes true when the value of the object is greater than or equal to the selected value.	Numeric and Summation	Object = Price Comparison = Is Greater or Equal Value = 5.00 A notification is generated when an item changes and the value in the Price field is greater than or equal to 5.00.
Is Greater Than	Becomes true when the value of the object is greater than the selected value.	Date/Time, Numeric, and Summation	Object = Submit Date Comparison = Is Greater Than Value = 10/1/2011 A notification is generated when an item changes and the Submit Date is greater than 10/1/2011.
Is Less or Equal	Becomes true when the value of the object is less than or equal to the selected value.	Numeric and Summation	Object = Price Comparison = Is Less or Equal Value = 5.00 A notification is generated when an item changes and the value in the Price field is less than or equal to 5.00.
Is Less Than	Becomes true when the value of the object is less than the selected value.	Date/Time, Numeric, and Summation	Object = Submit Date Comparison = Is Less Than Value = 10/1/2011 A notification is generated when an item changes and the Submit Date is earlier than 10/1/2011.
Mentions	Becomes true when a user is explicitly mentioned in a text field or note. The mention format is `@user`, where user is the user's login ID. Note: By default, only Latin characters are allowed when mentioning users. To change the allowed character set, customize the `ns.userismentioned.pattern` property in the `config.properties` file, located on the SBM server that hosts the Notification Server: installDir\SBM\Common\tomcat\ server\default\webapps\ notificationsrv\WEB-INF\classes	Any Field, Note	Object = Note Comparison = Mentions Value = (Current User) A notification is generated when a note is added to an item that mentions the current user (for example, `@bill` or `@bill@company.com`).
Priority changed in	Becomes true when the priority changes for any item in the specified backlog.	Any Item object (Primary items only)	Object = Any Object Comparison = Priority changed in Value = Backlog Sprint 1 A notification is the priority changes for any item in Backlog Sprint 1.
Removed	Becomes true if the specified value is removed from the field.	Multi-Group, Multi-Selection, and Multi-User	Object = Change in Version(s) Comparison = Removed Value = V4.5 A notification is generated when the value V4.5 is removed from the Change in Version(s) field.
Removed from backlog	Becomes true when any item is removed from the specified backlog.	Any Item object (Primary items only)	Object = Any Item Comparison = Removed from backlog Value = Sprint 1 A notification is generated any item is removed from the Sprint 1 backlog.