DRS: External Check

Currently, there are 2 options for running an external check (passive and active).

Development and implementation of an event bus is underway, which will guarantee event delivery. To ensure business code immutability, it is recommended to separate the check launch method from the check implementation. For example, the check class constructor accepts leadId and ruleTaskId, and the iterator runs the check class. This way, the launch method can later be replaced with an event bus.

1. Passive. GET /bs-core/main/scoring-rule-task-by-code (recommended)

{
  "ruleStepTypeCodes": ["SOME_REMOTE_CHECK_NAME"],
  "recommendation": "NOT_COMPLETED",
  "afterRuleTaskId": 5,
  "countFrom": 0,
  "resultsQty": 100
}

In the afterRuleTaskId field, you need to pass the last successfully processed record. The interval between calls depends on the required processing speed and server load.

2. Active. Sending an HTTP request from DRS to the check service

The service needs a method that will accept ruleTaskId and leadId in the URL (GET parameters or part of the query string)

Attention: This method is not recommended, as the service requires 100% uptime. If the service is unavailable at the time of notification - the request will not be resent. You will need to manually restart the check, there are no automatic mechanisms for this.