Bookshelf Home | Contents | Index | PDF |
Siebel Business Process Designer Administration Guide > Workflow Policies > About Creating Workflow Policies > About the Conditions AppletTable 45 defines the Conditions applet fields in the Workflow Policies Policies view.
Using Comparison Values in the Conditions AppletYou use comparison values in the Operation field. The field exposes the Workflow policy component column for monitoring. Standard ComparisonsThe Comparison field supports <, >, <>, >=, <=, =, LIKE, IN, NOT IN, BETWEEN, IS NULL, and IS NOT NULL operators. An 'AND' is implied between multiple conditions defined using these comparison values. 'AND' means that all conditions must be met before the action occurs. When you specify values for the comparison operands LIKE, IN, NOT IN, and BETWEEN in the Value field of the Conditions applet of the Workflow Policies Policies view, it must be in a form that the underlying database expects. IN, NOT IN, and BETWEEN require you to enter the database specific format for the field being examined, for example, IN ('a', 'b', 'c') or IN (1, 2, 3, 4) and BETWEEN 'A' and 'M' or BETWEEN 1 and 10. NOTE: It is up to the policy creator to make sure the syntax is correct. Siebel Business Process Designer only passes the BETWEEN clause to the database. It does not verify syntax, except for date and time. For date and time fields, Siebel Business Process Designer converts the date and time columns to the format of month/day/year, hour:minute:second. LIKE and NOT LIKE allow you to use wildcards, for example, LIKE Smith% or NOT LIKE Sm%th%. Table 46 shows comparison values for a typical database (your specific database syntax requirements may vary). Note that when using LIKE, IN, NOT IN, or BETWEEN with character fields, you use single quotes around the value. In addition, when using IN or NOT IN, you must place the value within parentheses. NOTE: On an MS SQL Server database, when you create a workflow policy condition on a LONG column, the available comparisons are IS NULL, IS NOT NULL, LIKE, and NOT LIKE. Specialized ComparisonsThe Comparison field also supports the specialized operators IS ADDED, IS UPDATED, and IS DELETED. The following comparisons work at the workflow policy component level. They do not operate at the field level.
The following comparison operates at the field level. To monitor if a field within the workflow policy component was modified, use the field that is named after the workflow policy component.
The IS operators serve as a starting point for the examination of the workflow policy. NOTE: When creating a batch type workflow policy, the comparison operators IS ADDED, IS UPDATED, or IS DELETED must be used in conjunction with regular conditions. These comparison operators are considered special conditions intended for Dynamic mode when triggering rows to look up regular conditions. Table 47 describes the specialized comparisons for all database platforms that can be used in creating workflow conditions. NOTE: 'OR' is implied between conditions defined using these specialized comparison values, where 'OR' means that one or more of the conditions must be met before the action occurs. An 'AND' is implied between conditions using standard comparisons and conditions using specialized comparisons. For example, you may want a service representative to receive an email when an open service request has an activity added to it. You would then create a policy that has conditions Service Request Status = 'Open', Service Request Activity Component IS ADDED. Entering Date CalculationsWorkflow Monitor considers both date and time when evaluating Workflow Policy conditions that perform a date comparison. CURRENT can be used when entering a value for a date comparison. The format for using CURRENT is CURRENT +/- d:h:m where "d" is day, "h" is hours, and "m" is minutes. You can use CURRENT in the comparison value for date fields. You can also use CURRENT when you specify the activation and expiration dates for a message broadcast action. |
Siebel Business Process Designer Administration Guide |