Response from Customer

Success Plans Modify Date updated when CTA or Timeline associated is updated


Userlevel 7
Badge +2

It would be great for the modified date on the Success Plan to be based on max date of a timeline entry or CTA modification.

 

We are trying to encourage CSMs to update the CTAs and Timeline entries to help us track how often they are interacting with the plan. Right now, the modify date only updates when you close the plan, which is not a true reflection of how often a CSM is interacting with the plan.


8 replies

Userlevel 7
Badge +2

@andreammelde thank you for sharing this here. I will check the possibility and get back to you.

Userlevel 5

@andreammelde 

Success plan, CTAs, and timeline - each have their respective modified dates. In report builder I think we can build report for timeline-activity/CTA on modified date and filter those which are linked to success plan.
 

Userlevel 7
Badge +2

If a Task is modified under a CTA, the CTA should be considered modified.

If a CTA is modified under a Success Plan, the Success Plan should be considered modified.

If a Task is modified under a CTA under a Success Plan, the entire parentage should be considered modified.

 Shouldn’t have to go through data gymnastics to identify when an SP was last modified.

 

This doesn’t seem like an out of left field expectation to me….?  @bradleymcg @heather_hansen @wayne_baker @spencer_engel am I wrong?

 

@Cornelia may you direct this to the right product team?  Thx!

Userlevel 7
Badge +5

100% I would agree. If you touch any activity type thing associated with the success plan, it should reflect as modified.

Userlevel 7
Badge +3

If a Task is modified under a CTA, the CTA should be considered modified.

If a CTA is modified under a Success Plan, the Success Plan should be considered modified.

If a Task is modified under a CTA under a Success Plan, the entire parentage should be considered modified.

 Shouldn’t have to go through data gymnastics to identify when an SP was last modified.

 

This doesn’t seem like an out of left field expectation to me….?  @bradleymcg @heather_hansen @wayne_baker @spencer_engel am I wrong?

 

@Cornelia may you direct this to the right product team?  Thx!

I think it’s perfectly reasonable. If gainsight wants to preserve when an individual record was updated in absence of any update on a child object, you could just have a different modified date field. One that does what it does now, and one that looks for the most recent modified date for any child records (such as @darkknight describes above).

That would preserve existing functionality if you want to really look at granular modified dates, and also not have to rebuild things, while providing much better reporting functionality in a way that reflects real world usage of an admin trying to answer the question “When was X last updated?”.

Userlevel 7
Badge +2

in a way that reflects real world usage of an admin trying to answer the question “When was X last updated?”.

THIS right THERE.

Userlevel 6
Badge +1

Not that it’s an ideal solution, but this could probably be handled via rule and a couple custom fields for those wanting the functionality of “rolling up” Task Last Modified Date to Objective/CTA Last Modified Date to Success Plan Last Modified Date.

Userlevel 7
Badge +2

Not that it’s an ideal solution, but this could probably be handled via rule and a couple custom fields for those wanting the functionality of “rolling up” Task Last Modified Date to Objective/CTA Last Modified Date to Success Plan Last Modified Date.

Sure, but this shouldn’t require a custom workaround.  If anything within a Success Plan changes, the modified date should be reflected as such. As @bradleymcg noted the functionality should align to the “real world usage.” I’ve grown weary of custom workarounds….:disappointed:

Reply