Jump to content

Wait for Update from Linked Request


Jeremy
 Share

Recommended Posts

I have a process that I would like to wait for a request to be linked to it which I can achieve and I can get the linked child request to update the parent request with some text, however I put a suspend node in the parent request to 'wait for update' and although the linked child request updates the request but the parent does not 'unsuspend' and carry on the process.

Any help appreciated.

Child Request:

image.png.6541287cac0e83c542cea3b5f15701ae.png

Update on Parent Request:

image.png.fc1d60521b9c12923e3d9762ea4f73dd.png

Parent Request node which doesn't recognise the update:

image.png.f772de2e0d14ad30d11562dbcb6b4e78.png

Link to comment
Share on other sites

HI @Jeremy

We have a similar process where we log a 'linked' request and then have to wait for that request to be completed, and the way we had to do it was to suspend and wait for the LINKED request to be updated with some specific text:

image.thumb.png.101196e0083daa5aa4826d36a7c8caf4.png

 

 

In the LINKED request, once the work has been completed, we then added a node to update that request with the same text that the originating request is looking for:

 

image.thumb.png.798b833a30443df84786730ca1f30c96.png

 

This works for us....I think we had a similar problem to what you're describing when we were monitoring the 'original' request rather than the 'linked' request in that it never 'unsuspended' itself. 

 

 

 

Link to comment
Share on other sites

I'm not sure whether you know about this or if this helps...but you can add a decision tree in your process to check for 'Linked Requests' (which will look for a number (I think) of linked requests) and, if it's 'set' then are some, if not, then there aren't!  You can then branch off to do something depending on what you find?

 

image.thumb.png.e4054dd084c4e8059db61b350ad1738b.pngimage.png.900e2ff08c5898ebdfb3b631c7cbb79d.png

image.png

Link to comment
Share on other sites

hmm...is there DEFINITELY going to be a linked request at a particular point in the process? 

if so, you could have a manual activity or a suspend node which expires every x amount of minutes/hours as part of the checking loop which would only move on WHEN the linked request is added? 

If it could happen at any point in the process then I don't have any ideas!! 

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...