What is it?
The prior value field capability makes it possible to build conditions on or compare to the prior value when creating conditions. The history tracking fields can be used when configuring message body fields on a notification. Please see the additional information section below to ensure you have historical tracking enabled in SFDC.
When to use it?
When creating a condition that triggers based on a change in field value, using the prior field facilitates the ability to do so with a high degree of specificity.
When selecting message body fields, adding the history tracking value can provide additional context to why the alert was triggered or how the record changed over time.
How is it set up?
Prior value conditions:
Each condition will have a clock icon to the right of the condition configuration options.
On the condition you would like to leverage the prior field value, click the clock icon. The icon will turn purple and a "Prior Value" banner will appear above the field to indicate that this condition is referencing the prior value of the field.
History Tracking message body fields:
For each field you would like the prior value to display alongside the current field value in the message body of a notification, click the clock icon on the field card once you've added it to the message body.
How does it work?
Where a condition includes the prior value of a field, the workflow will only fire if the prior value of the field makes the condition true.
Where a prior value is available and history tracking is on, it will display alongside the current value in the message body of the notification.
Additional Information
History tracking must be enabled in SFDC for fields that are leveraging the prior value capability.
If history tracking is not enabled, the prior value is not available for Rattle to leverage when triggering a condition or populating the message body.
You can enable history tracking for up to 20 fields on a standard or custom object under the object's management settings.
SEE ALSO: