Use Calculated Properties To Conduct Pipeline Health Checks

Sean - this is great, exactly what I was looking for.

However…

In practice, there are some issues with the workflows I can’t get around.

I work closely with our reps to roll out new HubSpot functionality, and am in involved in deal reviews. Often times a rep will update all the values at once, or we may go back and change an answer after reviewing the deal.

So here are the issues we’ve encountered.

  1. When a rep updates more than one value at a time before saving the record, the workflow only runs once and adds 1 point instead of 2, 3, 4, etc. Potential Fix - I created separate workflows for each property so they can run independently to add points. This seems to be working just fine.
  2. Any time a rep changes their answer (ex. change “Decision Criteria” from Business Decision Criteria to Technical Decision Criteria), it reruns the workflow and adds more points when it should just stay constant. We want Re-Enrollment turned on, but not when a value is changed.

I can’t seem to figure out #2 on my own. I was testing If/Then branches after enrollment triggers to check IF the value was ever known before then don’t increase points, but it’s also not working exactly right.

Lastly, deducting points isn’t really addressed. I’m looking at separate workflows for that, but once again get into issues where it needs to recognize that the value used to be known and is now unknown which doesn’t quite work with HubSpot’s workflows.

Does anyone have any ideas here? Thanks!