Difference between revisions of "About Policy Triggering Criteria"
From LongJump Support Wiki
imported>Aeric |
imported>Aeric |
||
(20 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
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: | 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: | ||
:;Date Criteria: | :;Date 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: | ::Trigger the policy when one of the standard date fields in the record (date created, date modified, or date of change in workflow state) or when one of the custom date fields defined in the object is within a specified date range: | ||
::* Within the current, next, or previous week, month, or day. | ::* Within the current, next, or previous week, month, or day. | ||
::* Within a specified calendar year or calendar quarter. | ::* Within a specified calendar year or calendar quarter. | ||
::* Within a specified | ::* Within a specified [[Financial Period]]. | ||
:;Field Criteria: | :;Field Criteria: | ||
Line 15: | Line 15: | ||
'''Considerations''' | '''Considerations''' | ||
:*If no criteria are specified, the criteria resolves to <tt>TRUE</tt>. (The actions associated with the Data Policy are always performed.) | :*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, all of them must true for the Data Policy to fire. | :*If a combination of criteria is specified, all of them must return 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> | :*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. | ||
Line 37: | Line 37: | ||
:In this example, the Field Display Type for <tt>Inventory_Count</tt> is <tt>NUMBER</tt> | :In this example, the Field Display Type for <tt>Inventory_Count</tt> is <tt>NUMBER</tt> | ||
|-valign="top" | |-valign="top" | ||
|Is an | |Is the inventory value missing? | ||
| | |||
:<tt> Inventory_Count = BLANK</tt> | |||
:The test for an empty numeric or date field is <tt>BLANK</tt>. | |||
|-valign="top" | |||
|Is a text field empty? | |||
| | | | ||
:<tt> state = <nowiki>''</nowiki></tt> | :<tt> state = <nowiki>''</nowiki></tt> | ||
: | :The test for an empty string is '''two single quotes (<tt><nowiki>''</nowiki></tt>)''', not the double-quote character (<tt><nowiki>"</nowiki></tt>). | ||
|} | |} | ||
Line 69: | Line 73: | ||
|- | |- | ||
|Import Record || During a record import ||All, except Tasks/Appointments | |Import Record || During a record import ||All, except Tasks/Appointments | ||
|- | |||
| Signed || This event occurs when a record is signed using a [[Digital Signature]] || All | |||
|- | |||
| Unsigned || This event occurs when a [[Digital Signatures#Invalidating a Signature|signature is invalidated]]. It also occurs when a user clicks '''Verify Signature''' on an invalid signature. || All | |||
|- | |- | ||
|Merge|| When converting a Prospect to an Account with the Merge option ||Prospects and Accounts Only | |Merge|| When converting a Prospect to an Account with the Merge option ||Prospects and Accounts Only | ||
Line 75: | Line 83: | ||
|- | |- | ||
|[[When Due]]|| When a Task or Appointment becomes due ||Tasks/Appointments Only | |[[When Due]]|| When a Task or Appointment becomes due ||Tasks/Appointments Only | ||
|} | |} | ||
===Triggering Criteria in Calendar Based Data Policies=== | ===Triggering Criteria in Calendar Based Data Policies=== | ||
Calendar Based Data Policies offer additional date-driven triggers that don't depend on any particular action. | Calendar Based Data Policies offer additional date-driven triggers that don't depend on any particular action. |
Latest revision as of 19:34, 24 April 2014
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:
- Date Criteria
- Trigger the policy when one of the standard date fields in the record (date created, date modified, or date of change in workflow state) or when one of the custom date fields defined in the object 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 of them must return 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.
Field and Formula Triggers
In these examples of criteria expressions, 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? - DATECOMP(departure_date, submit_date) > 7
- Note that the Field Display Type is DATE for both arguments
Is the inventory count less than 25? - Inventory_Count < 25
- In this example, the Field Display Type for Inventory_Count is NUMBER
Is the inventory value missing? - Inventory_Count = BLANK
- The test for an empty numeric or date field is BLANK.
Is a text field empty? - state = ''
- The test for an empty string is two single quotes (''), not the double-quote character (").
- Learn more: Filter Expressions in Reports and Data Policies
Triggering Criteria in Action Based Data Policies
This list describes the action 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 Signed This event occurs when a record is signed using a Digital Signature All Unsigned This event occurs when a signature is invalidated. It also occurs when a user clicks Verify Signature on an invalid signature. All 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
Triggering Criteria in Calendar Based Data Policies
Calendar Based Data Policies offer additional date-driven triggers that don't depend on any particular action.