Suspend node - waiting for attachment

[LorraineS]

I need help to rectify error with suspend node. I need process to wait for an attachment.

[James Ainsworth]

Hi @LorraineS,

Thanks for your post.  Is the error on an existing request where it has failed on a particular suspend node?  Or is the error within the designing of the workflow?

[LorraineS]

Hi James, it is designing a new workflow

 

[James Ainsworth]

Are you getting a particular error message?  Are you able to provide a screen shot of the configuration for that node?

[LorraineS]

[LorraineS]

getting a no matching goto found

 

[LorraineS]

[LorraineS]

Hi James, screen shot of Suspend node

[Steve Giller]

27 minutes ago, LorraineS said:

getting a no matching goto found

That error would indicate an issue with the Decision Node, rather than the Suspend Node.
We strongly recommend that you always have a No Match branch on your Decision Nodes, otherwise you are prone to the error above and without a "No Match" branch it becomes extremely difficult to troubleshoot.

 

[James Ainsworth]

@LorraineS

I'd be interested to see what you have for your expression on this highlighted branch Attachment. 

[LorraineS]

[LorraineS]

@James Ainsworthplease see screenshot

[LorraineS]

On 11/26/2021 at 6:35 PM, James Ainsworth said:

@LorraineS

I'd be interested to see what you have for your expression on this highlighted branch Attachment. 

screenshot above

[Victor]

@LorraineS when would you need the workflow to follow the "Attachment" branch? Why do you want to check for the node outcome as "Wait For Attachment"?

(the expression is incorrect, there is no such outcome value for this node, but I need to understand how you need it to work, what are you trying to achieve, before I can advise)

[LorraineS]

@Victor Hi, The attachment branch would be followed when the customer has attached a new photograph via email. The expiry route would be taken, if no photo was uploaded. 

[Victor]

@LorraineS right, I understand.... well the scenario then seems to be fairly simple. Given this is a two options scenario, I would look at this from the expiry angle.. So, the expiry route would be when the user/customer has not attached the photo... The node waited for the designated time, there was no attachment uploaded to resume the process so it expired. Therefore it is fair to assume the following options:

• expiry: no attachment added
• anything else: the attachment was added - given there was it was not the expiry that resumed the node, it could only be that the node resumed because an attachment was uploaded

To put the above in a workflow the decision node would have 2 branches:

• expiry
• no match (which equates to anything else but expiry in our case)

Sure, you can build branches based on other criteria but in my view it is easier to look at this from this perspective, as you only need to worry about the expiry and not worry about any other criteria/custom expression. Makes sense?

[LorraineS]

@Victor yes, makes sense.