Jump to content

On-Hold Periods


Jeremy
 Share

Recommended Posts

I know that this has been mentioned many times before, but I used the excel spreadsheet that was provided to work out the on-hold time for this node but it just passes through... is there some that I have missed?

image.png.02982c8426600f64ca57689bca20ceb6.png

In the workflow, it assigned to an account, places on hold then updates the resolution text and emails the customer again (preferably after a year). But in the timeline is does it all at once and does not seem to notice the on-hold node. (timeline and workflow section below)

image.png.65816ad96e742c04f9be790cc262d13a.png

image.png.471c464e081403cd6cb792a042b99056.png

Link to comment
Share on other sites

@Jeremy - I hope you did not give up on workflows/BPs... :)

Just to explain why the solution provided by Martyn is needed. Workflows and requests actions are rather independent... The workflow acts as a guideline for how the request should be progressed and it can be designed to prevent or allow the request to be progressed in a certain way. But in order for requests actions and workflow actions to be tied together, the workflow needs to be configured as such otherwise it will behave independently of the request...

To put this in your example...you have a node that puts the request on hold... this means the request, not the workflow... just because the request is on hold it doesn't mean the workflow is also on hold... if you want both to be "suspended" then the workflow must also be put "on hold" using the node advised by Martyn...

  • Thanks 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...