Proper way to Fast-Track Leads through Lifecycle stages?
SOLVE
1 Accepted solution
Proper way to Fast-Track Leads through Lifecycle stages?
SOLVEHi @JKieley,
The short answer is that – using only the default properties – this isn't possible. If a user selects a lifecycle stage value, there isn't any way to retroactively force the record through previous stages so that their dates are collected for reporting.
The only workaround I see and have implemented involves creating a second custom lifecycle stage property and making the actual default lifecycle stage property not editable and remove if from being displayed in records, views etc.
You would encourage users to only use your new custom lifecycle stage property (which is a clone of the original property).
In a contact-based workflow, you would then re-enroll contacts when this new property is known and use a value equals branch.
In each branch, you would then use the "Set property value" action and send the contact through each of the previous lifecycle stages (a contact can't go back so we can make use of that) up until they reach the value specified in the custom property.
Users would maintain the custom property, in reporting you can use the default property which would then be fully maintained.
Best regards!
| Karsten Köhler |
 | Did my post help answer your query? Help the community by marking it as a solution. |
Proper way to Fast-Track Leads through Lifecycle stages?
SOLVEHi @JKieley,
The short answer is that – using only the default properties – this isn't possible. If a user selects a lifecycle stage value, there isn't any way to retroactively force the record through previous stages so that their dates are collected for reporting.
The only workaround I see and have implemented involves creating a second custom lifecycle stage property and making the actual default lifecycle stage property not editable and remove if from being displayed in records, views etc.
You would encourage users to only use your new custom lifecycle stage property (which is a clone of the original property).
In a contact-based workflow, you would then re-enroll contacts when this new property is known and use a value equals branch.
In each branch, you would then use the "Set property value" action and send the contact through each of the previous lifecycle stages (a contact can't go back so we can make use of that) up until they reach the value specified in the custom property.
Users would maintain the custom property, in reporting you can use the default property which would then be fully maintained.
Best regards!
| Karsten Köhler |
| Did my post help answer your query? Help the community by marking it as a solution. |
