Prerequisites for Configuration
Before executing the test scenarios provided in this documentation, please ensure that the account being configured has the required permissions to access the relevant data source.
If the necessary permissions are not granted, the control will not be able to run properly and the following message will be displayed:
This control is eligible for an external data source.
In this case, verify that the account has been assigned the appropriate permissions and that the required access rights to the data source are in place before proceeding with the configuration or test execution.
Test set for individuals
The rules below apply to all locations. Triggering is based on the presence of a keyword in the person’s name provided in the request.
Keyword to include in the name | Expected | Examples |
|---|---|---|
| MV-M External source: match between bank details and third party validated | Sandy Match |
| MV-U External source: data not eligible | Jason Unknown-moa |
| MV-CM External source: partial match between bank details and third party | Chris PartialMatch |
| MV-NM External source: mismatch between bank details and third party | Meredith weakMatch |
| MV-U Input fields do not meet corridor requirement | Badrequest Suzanne |
| MV-TO External source: technical error | Timeout Michel |
| MV-ER External source: technical error | Robert Down |
For Individual controls, our mock test environment is permissive regarding the bank account details provided. The bank account information entered does not impact the test result. Only the keyword included in the individual's name is used to determine the expected outcome of the control.