[Enhancement]Prevention of multiple creation of Success Plans

Related products: None

Account, Success Plan name, type and status are used as an identifier for the success plan action in rules. So, if there is already a success plan with the initially mentioned four entities (Account, Success Plan name, type and status), then rule will not create new success plan, rather it will just update the existing one.





But the problem occurs when any success plan is created by a rule with draft status, then when the status is changed to active and rule runs again, a new Success Plan will be created with same name with draft status since status is one among the four default identifiers. 





Is there a way by which we can restrict this by a rule or having an optional identifier/s?
Thanks Shiv for posting this.


This is one basic requirement we need. 
@Shiv, Got the context.This is the expected behavior in CTA also. 





@Shravan,Sorry for the inconvenience.There is no workaround to achieve this.


I am redirecting this to our Product Team,since its a request to change the existing behavior pushing this to an idea post. 





@Shravan, We will investigate the possibilities from our end. If you have any best way,please suggest us?





Thanks for posting
This reply was created from a merged topic originally titled [Enhancement]Prevention of multiple creation of Success Plans.





Account, Success Plan name, type and status are used as an identifier for the success plan action in rules. So, if there is already a success plan with the initially mentioned four entities (Account, Success Plan name, type and status), then rule will not create new success plan, rather it will just update the existing one.





But the problem occurs when any success plan is created by a rule with draft status, then when the status is changed to active and rule runs again, a new Success Plan will be created with same name with draft status since status is one among the four default identifiers. 





Is there a way by which we can restrict this by a rule or having an optional identifier/s?
@aditya_marla - do you have any thoughts on this use case and process flow? Any solutions that can be offered here?




Some specifics -- "If Success plan is in Closed status and we run the rule again a new success plan is getting created" -- In our case we do not want another success plan to be created. We do not see any option to set lifetime once kind like in CTA action.





2. "If we change CSM when we have already active success plan, owner will not get updated if we run the rule." -- In our case we would like to update the CSM on existing success plans when CSM changed on the account/relationship.




I’ve just come across a scenario where we need to have custom Status types, but having an identifier for Status in the Success Plan creation process is creating duplicates when a user moves a current Success Plan to a new Status.

I would love the ability to define the identifiers manually, like we can with data loads.