Writing an BRF+ exception into the brf+ trace / exception content

[andreas_kaiser]

Hello,

I am just evaluating if the brf+ framework could be used to forward the details some code internal rules to the business users.

But I still have issues with the exception handling. If I get an exception from a BRF+ call (e.g. a missing entry in a descision table) the information within the exception object is poor. (No reference to appllication or rule used). This I can fix manually by creating my own exception to catch and re-raise the exception. So I can circumvent this problem.

However I was hoping to find more details in the mt_messages attributes of the thrown exception which is nicely written into the trace in the so called technical trace mode. But unfortunately I can not access this mode if I try to write the trace on my own.

1. Question: Why this assertion? Am I not supposed to show any errors, that will certainly occur if the framework is really used in production?
I would really like to avoid writing my own error Interpretation code just for the brf+ case.

2. Question: Would it be possible to give a more specific error text in the exception itself when such an exception occurs? The error text "Keine Übereinstimmungen zum vorliegenden Kontext (ENTSCHEIDUNGSTABELLE) gefunden" does not give any clue which descission table is in question.

Best Regards,
Andreas Kaiser