Logging the check result - BRMlog (BusinessRulesLog)
When the order passes through BRM, a log of changes is recorded. It reflects all the validation rules with the result. There can be several BRM logs - there are no restrictions on the number, each passage is logged.
BRM is triggered,
as soon as the order arrives
to the FS collection - Orders and again when writing an order to CRM.
But, in addition to this, it can be forced to start
from CRM and again when recalculating an order:
The result of checking BRM by an autobot in Jetti CRM is displayed in an auto-generated comment. If the order has been successfully verified according to all the rules, then the comment will indicate - there are no violations of BRM, and the operator will set BRM in the order:
If the order has not been verified according to one or several BRM rules, then in the CPM the operator will be able to see these rules:
BRM log is recorded for each order that passed through BRM in FS (Firestore):
An example of several logs (looking at the last one):
Several logs can be recorded upon successful confirmation of the BRM order. Example, order 426606 (F39196CC-3E61-41AB-972E-0580B1681BB3). The first log was recorded when writing an order
to the Orders collection, the second entry occurred when the payment confirmation arrived. The isPrepaid flag has been set
BRM check statuses:
FALLED - verification was not successful
DISABLED - check is disabled
PASSED - verification completed successfully
ERROR - error
We look at the final result of BRM according to all the verification rules at the end of the log (total):
If at least one check rule results in failed, then BRM auto order confirmation is not successful!
If error = 0 and failed = 0, then auto confirmation was successful.