Difference between revisions of "About Policy Triggering Criteria"
From LongJump Support Wiki
imported>Alice (Updated examples per case 2010-11-06-16531) |
imported>Aeric |
||
Line 1: | Line 1: | ||
==About Policy Triggering Criteria== | ==About Policy Triggering Criteria== | ||
To see if a data policy should be triggered, tests are run on its ''Triggering Criteria''. There are three kinds of criteria you can specify, alone or in combination: | |||
:;Data Criteria: | |||
::Trigger the policy when one of the date fields in the record (date created, date modified, or date of change in workflow state) is within a specified date range: | |||
::* Within the current, next, or previous week, month, or day. | |||
::* Within a specified calendar year or calendar quarter. | |||
::* Within a specified financial period | |||
:;Field Criteria: | |||
::Trigger the policy when one or more fields compare successfully against specified values. (For example, order_total > $5,000.) | |||
:;Formula-based Criteria: | |||
::Create a formula-expression from a combination of object fields and [[User]] fields, where the user is the person performing the action on the record. | |||
'''Considerations''' | '''Considerations''' | ||
*Policy | *If no criteria are specified, the criteria resolves to <tt>TRUE</tt>. (The actions associated with the Data Policy are always performed.) | ||
*If a combination of criteria is specified, ''al''l must true for the Data Policy to fire. | |||
*Formula-based Criteria are [[Expressions|Expression]]s, which must resolve to <tt>TRUE</tt> or <tt>FALSE</tt> | |||
*If the [[Expressions|Expression]] described by the criteria is <tt>FALSE</tt>, the associated actions are not applied. If <tt>TRUE</tt>, the Data Policy is executed, and any associated Actions are invoked. | *If the [[Expressions|Expression]] described by the criteria is <tt>FALSE</tt>, the associated actions are not applied. If <tt>TRUE</tt>, the Data Policy is executed, and any associated Actions are invoked. | ||
*Calendar Policies have additional, date-based Triggering Criteria available | *Calendar Policies have additional, date-based Triggering Criteria available | ||
Revision as of 20:59, 9 June 2011
About Policy Triggering Criteria
To see if a data policy should be triggered, tests are run on its Triggering Criteria. There are three kinds of criteria you can specify, alone or in combination:
- Data Criteria
- Trigger the policy when one of the date fields in the record (date created, date modified, or date of change in workflow state) is within a specified date range:
- Within the current, next, or previous week, month, or day.
- Within a specified calendar year or calendar quarter.
- Within a specified financial period
- Field Criteria
- Trigger the policy when one or more fields compare successfully against specified values. (For example, order_total > $5,000.)
- Formula-based Criteria
- Create a formula-expression from a combination of object fields and User fields, where the user is the person performing the action on the record.
Considerations
- If no criteria are specified, the criteria resolves to TRUE. (The actions associated with the Data Policy are always performed.)
- If a combination of criteria is specified, all must true for the Data Policy to fire.
- Formula-based Criteria are Expressions, which must resolve to TRUE or FALSE
- If the Expression described by the criteria is FALSE, the associated actions are not applied. If TRUE, the Data Policy is executed, and any associated Actions are invoked.
- Calendar Policies have additional, date-based Triggering Criteria available
Triggering Criteria in Action Based Data Policies
In these action-based criteria expressions examples, note that the Field Display Type and Formula Function are used together to create a Logical result for the Policy Triggering Criteria.
These examples are presented as questions, because the result must be Logical: YES/NO or TRUE/FALSE.
Example | Expression |
---|---|
Is the submitted date more than seven days before the departure date? |
|
Is the inventory count less than 25? |
|
Is an essential field blank? |
|
Available Triggers and Eligible Objects
This list describes the available triggers, and eligible objects:
- Note: Data policies can be created for all objects, except Products and Price Books
Trigger Triggered when... Eligible Objects Add Adding a new record All Update Updating an existing record All Delete Deleting an existing record All Ownership Change Changing a record's owner All, except Tasks/Appointments Workflow State Change Changing a record's workflow state All Import Batch During a batch import All Import Record During a record import All, except Tasks/Appointments Merge When converting a Prospect to an Account with the Merge option Prospects and Accounts Only Convert to Account When converting a Prospect to an Account without the Merge option Prospects Only When Due When a Task or Appointment becomes due Tasks/Appointments Only On View Retrieving a single record All List View Retrieving a list of records All
Triggering Criteria in Calendar Based Data Policies
Calendar Based Data Policies offer an additional, date-based criteria, as well as field-based policy triggering criteria.
- Learn more: Filter Expressions in Reports and Data Policies