How to do error handling in workflows

Maybe that the LineItemNo is only prepared during insert, so it's not yet available when CO is generated from SalesQuotation.

What if you build in a check if LineItemNo is avaiable and if not use a counter to generate it? The counter could be in a loop until no more Quotation lines to read.

Hi @eqbstal 

I have a quick question about workflows if you don't mind (I tried to directly message you but for some reason, the message wouldnt send, so I’m asking it here). I checked the document you sent me, but it didnt seem to mention lists.

I have a projection task call this function "GetFileExtList(DocType):String" but I am not sure how to format it to handle the output. This is what my workflow looks like.

In that "get document list" section, I am calling that function. I want to read from that but how do I recognize the output in my script function inside the loop?

Any input would be appreciated.

Thanks,

Bryan

Hi @eqbstal 

Sorry about that, I attached the image to the message but I guess it didn’t load correctly.

 

Thanks,
Bryan

Hi @eqbstal sorry about that, the image I uploaded before was an outdated workflow I created. I have functional workflows that handle collections. That list I was grabbing wasn’t the best list to work with either, as the proper projection call should be ‘DocReferenceObjectSet’ from the projection ‘DocumentObjectConnectionsHandling’ with the parameters for keyref.

This is what my more recent workflow looks like 

Sadly, you cannot invoke Aurena agent calls via a workflow, so I could not print these attachments out, so I ended up creating a different workflow that displays a user task to prompt the user to print off the documents attached to this shipment/customer order.

Thank you for your input though!

Hi @eqbstal

Of course, I’m happy to help.

Before that task, for the “Get attached document list” task, I am using a read projection task on the Projection “DocumentObjectConnectionsHandling” and the entityset “DocReferenceObjectSet” while setting the “read collection - Collection variable name” as DocReferenceObjectSet_Set (Bad naming convention)

For that “Prepare condition for gateway” script task, I’m using JavaScript. The code is this

var documentList = execution.getVariable('DocReferenceObjectSet_Set');
var documentsRemaining = false;

if(documentList && documentList.length > 0)
{
  documentsRemaining= true;
}

execution.setVariable('documentsRemaining', documentsRemaining);

Then for the arrow of “Are there more documents to loop through” I have a default arrow pointing to the end for “no” and the “yes” arrow is another javascript bit. Here’s the code for that

execution.getVariable('documentsRemaining') == true

lastly, just define the collection in the subProcess, and define the element, in this case I set this to “document” but truth be told, I’m not entirely sure if that element variable matters too much in my case, as I’m not using it.

If you need help with anything else, please feel free to ask. I’m not the most experienced with workflows, but I’m definitely getting better at creating them.

Thanks,
Bryan

@eqbstal I’m glad you found that helpful! Good luck in future development.

My pleasure,

Bryan

@bdoucette I have only environments to my availability that have either no mail server connected or it has been turned down as the environments are Dev/Test only. More to the point: never had a request to do that, so can't help you now.