Create CTA when a field has changed from value X to value Y

@pele Thank you for the reply. I appreciate it. I'll put this through it's paces to see how it works and let you know.

Good luck! Do circle back if you run into any hurdles. I took a peek at the old thread you referenced, and I think the blocker 4 yrs ago was not having bionic rules– back then, you could only create rules with 1 dataset from 1 object.

Hi Scott,

I wanted to add a note that @pele's proposed solution is spot on and should solve your ask. Please update the thread if you are able to get the CTA to fire properly using field history tracking!

Hey @pele, can I ask a couple questions:

1. [quote]turning on history tracking for your field "Customer Type" [/quote]I wanted to confirm this is in SFDC...yes?
2. It follows then that the History Object being queried is also in SFDC?
3. Where would I get the "Old Value" "New Value" from? What I see in the History Object is the screenshot I've attached (from our dev site). How are you getting those 2 values?

Appreciate any help here with some of these basics.

1. Yes in SFDC.

https://help.salesforce.com/articleView?id=tracking_field_history.htm&type=5

2. Yes, if history tracking enabled on field on account, object would be "Account History"

3. See image below from GS Reporting

Edit: A small tip: You can't fitler directly on New/Old value in a rule fetch task, but you can do a contains filter on it withn a following rule action. Like below.

Hey @scott_sigsci, happy to give some more context on this:

1. Yeah, this is done in SFDC. If you click "Setup" in the top-right of the screen, and find the field list for the given object, there will be a button for "Set History Tracking":

** You'll know history is being tracked if the box is checked in the "Track History" column.

2. Sorry, I should have explained this a bit more/better. You'll do this in Gainsight, Rules Engine. What happens with History Tracking, is that a seperate object exists that will house the changes that are being tracked. So, whenever there's a change to a field that's being tracked, a new record is created on the history object that will include what field was changed, what the old value was, what the new value is, and when the change was made– and that's what you'll setup the rule to look for. Something like this:

** Note, the Object in the dataset is "Account History" instead of "Account"

3. One bit I kinda forgot, is that the fields "Old Value" and "New Value" can't be added as filters in this first dataset. To add these fields as filtes, just add a "Transform" task:

wrt:

Then you can add additional details as need through additional datasets and merges.

You'll probably want to include some other details in the rule to create CTAs– e.g. you'll probably need to have CSM ID to assign the CTAs. To do this, create another dataset from "Account" with all of the fields that you want to include, and create a merge with this and the "Transformed" history object dataset:

** You'll want to "keep all records" from the transformed history object dataset– i.e. if you put this on the left side in the merge task, select "Retain all records from the left dataset"

@pele This is fantastic....HUGE. This detail is really helpful. I'm working through it now. Will continue to keep you in the loop. :)

As an aside, @spencer_engel hosts office hours on Thursdays, and this is the perfect sort of troubleshooting for those sessions– here's the Community Thread for tomorrow's US office hours.

@pele Thank you for the effort here. This is confirmed to work!

The follow up below your original answer was a huge help to me (and I would imagine to others as well). This should serve as an answer to this type of question, as @scott_496fa0 noted below.

Cool beans! Glad this worked out!