Skip to main content

I have a use case where we have a custom, low-volume object called Value Case which we use to track customer-reported ROI. We have a stage-like dropdown field on this object, and we need to keep track of each record’s stage movement. For example, if a record is saved on creation in Stage 1, and later the record is modified to Stage 2, we need to be able to see which date the record moved from Stage 1 to Stage 2. 

However, we anticipate there being several fringe cases or human errors that cause Stage 1 to move to Stage 2 and back to Stage 1, OR for Stage 1 to move to Stage 3 accidentally, when it should move to Stage 2. We want to use Real-Time Rules to capture the movement in (close to) realtime to store this movement in a custom object called Value Case Revision Dates. 

Given the current limitations on realtime rules, we are only able to configure these rules using limited Internal Events as the trigger: Company, Call to Action, CS Task, Relationship, and Relationship Type. 

For Real-Time rules to truly be impactful for our organization, we would need the ability to run them based on custom object events. 

This would be really helpful to us as well. We would really like to be able to track several fields on a custom object so we can see when they were last modified, but that doesn’t seem to be an option without this.


From what I’ve heard, change tracking is like THE primary use for realtime rules right now - and it works really well for the supported subjects. Expanding the supported subjects seems like a clear win for everyone.


Great idea! I can think of several ways to leverage this functionality!
 


Has there been any consideration of this idea (or even some other way to track field history)? I find myself wanting to be able to track field history on custom objects on a regular basis, but being unable to.