Use of REPORT ERROR

yuri.rj

I think that i missed something here.
I use REPORT ERROR sometimes, and it usually stops the ENTER NEW process, but i'm using it on a new application and its not stopping... It shows the error message, but still inserts the BO...

Is that correct?

If Category.CategoryLevel>5 OR Category.ParentCategoryLevel=5 Then
REPORT ERROR 'Maximum levels reached'

There are other actions after this one...

aware_support

Please read the User Guide where it talks about transactions. It's important to understand them

e5n_devildog

User Guide Page 70

Rules and Transactions
In Aware IM data processing may occur under the following scenarios:

An external request has been issued to the system, which triggered rule evaluation (see Rule Evaluation). This external request may have been issued either from the User Interface or from an external software system.
A notification has been received by AwareIM, which triggered rule evaluation.
A timer event triggered scheduled processes to start executing (see Scheduling).
The following section describes how Aware IM handles database transactions when processing data under the above scenarios (transactions are described in the Data Storage section).
With scenarios 1 and 3 data processing occurs within a context of a single transaction. This means that if something goes wrong all changes that have been done by any of the rules between the start of the external request (or when the scheduled process started) and the error are discarded (transaction is rolled back).

What can go wrong? First of all a transaction is rolled back if any of the rules issues the REPORT ERROR action. This action indicates an unrecoverable operation error so the current transaction is immediately rolled back and any prior changes are discarded11. A transaction is also rolled back in case of an internal error.
With scenario 2 the behaviour of the system is slightly different. The rules attached to a notification event are considered to be independent and are executed within separate database transactions, so if one rule fails anywhere it does not affect other rules attached to the notification – their changes are committed provided that these changes themselves did not cause errors.

yuri.rj

Actually, in my case its a simple validation.
I don't know why it doesn't work.

But to be honest i have bigger problems now.
I'll see that again in a few days hoping there is something that i missed...

aware_support

UI actions such as ENTER NEW, EDIT, DISPLAY MESSAGE etc COMMIT the current transaction. Everything that happens before these actions is committed, so if the REPORT ERROR is after them only the part starting from the last UI action will be rolled back