Hi,
I see in some of the workflow result status that there are sometimes ERRORS, WARNINGS or MESSAGES reported on some activities like the followings:
Assign Field Values
- Entry is locked,
- Field value is too long to fit in a field
- One or more required fields were omitted
In order to design better workflows, I would like the following to be looked at:
I have tried using the Try-Catch activity but it only triggers when there is an error, and I think it would be great to have an option to allow trapping of messages as well, and we could then adapt the workflow behavior according to the situation.
I think it's important that we trap situations where metadata can't be written to a field so I would like the ability to have a trigger mecanism for this.
Also, if an entry is locked, the WF will be but into a Waiting state for a few minutes and then a retry will be performed. The default retry is OK for many Workflows but I would like to see an option within activities that would bypass the default lock waiting period. This would be very usefull in workflows that are part in a realtime process and need it to retry every few seconds, and this would release the document to the user a lot faster.
If you do implement this, I think this modification should be available to each activity that can be affected by a lock.
If there is an error or a message that was not properly handled within a Script or SDK Script, the Try-Catch is currently unable to trap it. It would be good to allow trapping these situations.
I have also seen the SEARCH activity to return no result because of an invalid response from the server. when this happen, there is a warning message logged in the workflow status but there is no way to trap this within the Workflow and then create an alternative route to perform specific tasks for this situation.
Can this be added to the New Feature Request list?
Thank you
Daniel