1 Overview
OFS ECM API offers services to populate events identified in your source systems into the OFS ECM layer and services to allow the Behavior Detection Framework (BDF) to consume trusted pair information present within ECM.
In transaction monitoring systems, events are generated using various scenarios through batches. Then, the generated events are processed further, and cases are created. This whole process takes time. There may be some outliers for which a case can be created or extended to an existing case. This service helps users avoid the lengthier process of transaction monitoring systems. Also, these API services help Analysts create ad-hoc events if they come across any negative news on a customer or some other external incidents for an interested party for further investigation.
Trusted Pair is the concept of reducing the number of false positive events by identifying transactions between parties viewed as having a trusted relationship. The Trusted Pair API will allow full or filtered Trusted Pair data to be loaded to BDF based on inputs provided.
Event Suppression enables the automatic suppression of a particular entity's newly generated alerts based on criteria such as highlight, scenario, and suppression rule begin and end date. The Event Suppression API will allow full or filtered Suppression data to be loaded to BDF based on inputs provided.
Process Flow
The following figure shows the process flow of how to use services.
Table 1-1 Task Details
| Task | Details and Documentation |
|---|---|
| Select and identify the service | Select and identify the service which serves your purpose from the list of services. For more information, see Types of Services. |
| User Authentication | Identify the ECM user to use the service. User credentials must be set in the BASIC AUTH HEADER of the service request. |
| Validate JSON with configuration Tables | Compare the sample JSON with your required configuration. If it matches, then it can be used. Otherwise, it must be modified. |
| Perform respective changes in JSON or Configuration Table (if any) | Identify the necessary columns and add missing information to the configuration table as required. The columns added must be mapped back to the JSON. For more information, see Services. |
| Calling the Service | The Service is called using any REST Client. |
Types of Services
- Create Event: This service saves the event generated in the source system to the consolidation layer. The saved event is available for correlation when the next batch is triggered.
- Create Event and Promote to Case: This service creates a new case for the event generated from the source system. For example, if an event is created for a customer in the Customer Screening application, on triggering this service, a case is created for the event on the ECM layer.\
- Create Event and Extend to Existing Case: This service links a generated event to an existing case mentioned in the service. For example, an event generated in AML, which is related to another event for which a case is already created in ECM. On triggering this service, the new event is added to the existing case.
- Trusted Pairs - This service allows Behavior Detection Framework (BDF) to consume trusted pair information present within ECM. This API will have non-mandatory inputs. If these inputs are provided, they will be used to filter data. If these inputs are not provided, full data will be loaded as JSON output.
- Event Suppression - This service allows Oracle Financial Services Behavior Detection (OFS BD) to consume Event Suppression information present within ECM. This API will have non-mandatory inputs. If these inputs are provided, they will be used to filter data. If these inputs are not provided, full data will be loaded as JSON output.
- Create or Update Case Description - This service allows the Case Description to be added or updated. Any change will lead to an update to the audit history.
- Get ECM Case Status - This service will allow the determination of the current status of the Case. The service will have a JSON input. It will accept the case ID for which the status needs to be known.
- Add Customer to Case – This service will allow customers to be added to an existing case. All information about the customer will be added via the API. So, this is independent of whether the customer exists in the business data.
- Remove Customer from Case – This service will allow customers to be removed from an existing case.
- Add Account to Case - This service will allow accounts to be added to an existing case. All information about the account will be added via the API. So, this can be independent of whether the account exists in the business data.
- Remove Account from Case - This service will allow accounts to be removed from an existing ECM case.
- Add External Entity to Case - This service will allow external Entities to be added to an existing case. All information about the external Entity will be added via the API. So, this can be independent of whether the external Entity exists in the business data.
- Remove External Entity from Case - This service will allow removal of external Entities from an existing case.
- Add Transactions to a case - This service will allow addition of transactions to an existing case. All information about the transaction will be added via the API. So, this can be independent of whether the transaction exists in the business data.
- Remove Transactions from a case - This service will allow removal of transactions from an existing case. It will accept multiple case IDs and transactions information to be removed from a case.
- Update Event Risk Decision - This service will allow updating event risk decision for events in existing ECM case. It will accept multiple case IDs and event information whose risk decisions are to be updated for the case.
- Add Narrative to a Case - This service will allow addition of Narratives to an existing case. Only plain text will be captured. Formatting, images and screen shots will not be captured.