When an error occurs during an OpenContent-driven Alfresco Transaction, the error that Alfresco provided is wrapped within an OpenContent runtime error. This is done by our Alfresco Advice class which wraps our OpenContent calls into Alfresco transactions.
For example, if on bulk upload, a user doesn't have access to create their document, an OpenContent runtime error will be reported to the user, which does not provide information either to us or the user's support. Rather than wrap this in an OpenContent runtime error, we should report the error that caused the Transaction to fail, as this can provide further information to the support as to what went wrong.
When an error occurs during an OpenContent-driven Alfresco Transaction, the error that Alfresco provided is wrapped within an OpenContent runtime error. This is done by our Alfresco Advice class which wraps our OpenContent calls into Alfresco transactions.
For example, if on bulk upload, a user doesn't have access to create their document, an OpenContent runtime error will be reported to the user, which does not provide information either to us or the user's support. Rather than wrap this in an OpenContent runtime error, we should report the error that caused the Transaction to fail, as this can provide further information to the support as to what went wrong.