You are viewing limited content. For full access, please sign in.

Question

Question

Failure of briefcase is not a critical error..

asked on June 6, 2019

Hi,

I'm using a workflow to copy an updated document(X) from one repository(A) to another repository(B). The workflow deletes the document(X) from repository(B) if it exists and then copies the updated document(x)  from repository(A) to repository(B). The workflow I created works fine for this purpose.

Making the workflow more robust seems to be the issue. If I change the document/folder permissions ion repository(B) so as to generate an error my workflow breaks as expected.

If I delete a file from a write protected folder on repository(B) this is a critical error which I can catch with a 'try catch' construct which is fine for me.

If I copy a file into a write protected folder on repository(B) (using briefcase) it only gives me a warning which I cannot catch and as far as I am concerned is a critical error.

Is there any way I could make the failure of exporting a briefcase a critical error? Or a way to catch this warning so I can email the error?

The basic purpose of this robustness is to catch the failure of the briefcase construct, whether it is down to folder permissions, network problems, etc. 

Thanks

 

0 0

Replies

replied on June 6, 2019

In the Workflow Administration Console you can change whether or not an error code is "critical" under Server Configuration > Task Error Handlers and selecting the properties for the associated error code.

The only catch is that it depends on the error code you're getting. Failure to replicate the entries might be caused by a variety of errors; some of them may already be critical, and others may be a code that affects other activities so you might not want them all to be critical.

What I do is include a Find Entry on {destination path}\{entry name} of the transferred folder to make sure it made it to the other repository, if it is found I continue, if not I send an email and terminate the workflow.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.