|Bookshelf Home | Contents | Index | Search | PDF|
Siebel Business Process Designer Administration Guide for Financial Services > Creating Workflow Policies > Working with Workflow Policies >
Understanding the Conditions Applet
Table 62 defines the Conditions applet fields in the Workflow Policies Policies view.
Table 62. Workflow Policy Conditions Applet Fields Field Description Field The workflow policy component column in the workflow policy object on which the workflow policy condition is based, for example, service request priority or service request open date. Select the workflow policy column instance from the picklist for the field. This field is required. Comparison The comparison to make between a workflow policy agent's column value and the value you specify, for example, equals (=) or greater than (>). Select the comparison from the picklist for the field. This field is required. For more information, refer to Using Comparison Values in the Conditions Applet. Value The value to compare to the workflow policy column value instance, for example, not started or very high. This field is required except when the Comparison field has a value of Is Null, Is Not Null, Is Updated, Is Deleted, or Is Added. For more information, refer to Using Comparison Values in the Conditions Applet and Entering Date Calculations.
Using Comparison Values in the Conditions Applet
You use comparison values in the Operation field. The field exposes the Workflow policy component column for monitoring.
The 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.
LIKE and NOT LIKE allow you to use wildcards, for example, LIKE Smith% or NOT LIKE Sm%th%.
Table 63 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.
Table 63. Comparisons for a Typical Database Comparison Value < 5 > 5 <> 5 >= 5 <= 5 = A LIKE Abc% IN (1, 2, 3) NOT IN (`A', `B', `C') BETWEEN 1 and 2 BETWEEN `A' and `B'
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.
The 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.
- IS ADDED. If a new row is added for this workflow policy component, then trigger this workflow policy to be examined.
NOTE: If used in conjunction with standard comparisons, IS ADDED can be triggered when a record is updated.
- IS DELETED. If a row is deleted from this workflow policy component, then trigger this workflow policy to be examined.
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.
- IS UPDATED. If the field's value has changed, either by adding a new record with the specific field or by modifying the field in an existing record, then trigger this policy to be examined. To monitor if any field for a particular table was updated, use the workflow policy component column that represents the LAST_UPD column for that table.
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 64 describes the specialized comparisons for all database platforms that can be used in creating workflow conditions.
Table 64. Specialized Comparisons Comparison Value IS ADDED Use IS ADDED with a workflow policy component column specified in the Condition field and nothing specified in the Condition value. The condition is met when an instance of the workflow policy component is added.For example, if the Service Request policy component column is selected in the Condition field and IS ADDED is selected in the comparison, the condition will be met when you create a new service request. IS UPDATED Use IS UPDATED with any field specified in the Condition field and nothing specified in the Condition value. The condition is met when the field changes.For example, if service request status is specified in the Condition field and IS UPDATED is selected in the comparison, the condition is met when the Service Request status changes. IS DELETED Use IS DELETED when you specify a child workflow policy component in the Condition field, and nothing is specified in the Condition value. A child workflow policy component is a workflow policy component that is associated with a major entity in Siebel (a parent workflow policy component). For example, a parent workflow policy component might be Service Request. A child workflow policy component might be Service Request Activity. If IS DELETED is used in conjunction with other conditions, the other conditions must be based on the parent workflow policy component.For example, you may want to notify a service request owner if an activity is deleted from a service request that has a sub-status of In Process. The policy would be based on the Service Request Workflow policy object. The first condition would be field = Activity Component, comparison = IS DELETED, value = blank. The second condition would be field = Service Request sub-status, Comparison = `=', value = In Process. The action is to send an email to the SR owner.
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 Calculations
Workflow 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.
|Bookshelf Home | Contents | Index | Search | PDF|
Siebel Business Process Designer Administration Guide for Financial Services
Published: 22 May 2003