Run investigation

Once the Adverse Media Monitoring skill is installed and the configuration is complete, you can initiate investigations in one of the following ways:

• Start Business Process from Control Tower
• Run search via Launcher
  • Start Launcher
  • Run ad-hoc search
• Call AMM REST API

Start Business Process from Control Tower

You can initiate Adverse Media Monitoring in Control Tower by running the core or Launcher Business Processes. The main difference between them is that the Launcher creates an ad-hoc search screen that enables analysts and business users without access to Control Tower to initiate investigations from Workspace as part of a transaction monitoring fraud alert investigation.

To start the core Business Process, do the following:

1. In the Control Tower menu, click the Digital Workers section, click View All, and find the Evelyn: Adverse Media Monitoring group.

2. In the group, find the variation you wish to use and click it.

   

3. Click the Adverse Media Monitoring Business Process to expand the process definition, then click the Menu button (...) and select one of the following steps:

   • If it is not processing, click Edit and Run. The Edit Business Process window appears. Or

   • Click Copy to create another instance of the process. Thus you can run a new instance without impacting an existing one.

     

4. In the Business Process window, go to the Data tab and select Upload your data. The Upload your main data window appears.

5. In the window, click Add, select a CSV input file, click Open, and then click Upload. The data is uploaded to the Business Process.

   note

   If you are using the Human-in-the-loop feature, you can “pre-assign” tasks to workers in your organization. To do this, enter the worker’s id in the _sys_mt_hit_assignee column for the required entity rows of the input CSV file.

   Currently, real time validations are not supported. If a BP can't recognize a value in the sys_mt_hit_assignee column, the associated task is not assigned to any worker.

6. Go to the Run tab and click Run this process to start the Business Process.

   

If the Manual Task is enabled, the investigations appear within Workspace as they are complete. If it is disabled, the reports are generated and stored within the location that was specified during the installation and configuration of AMM.

note

Occasionally no results are found for the search. If this occurs, a report for each entity is created. A separate email with a link to view and download the report is sent for each entity that does not have search results. A copy of this report is also stored in the location specified during the installation and configuration of AMM.

Once all of the entities within the input file have been processed, the Business Process automatically ends.

Run search via Launcher

The Launcher is a business process that allows customers to trigger Adverse Media Monitoring from the Workspace user interface. It is available after installing and configuring Adverse Media Monitoring.

Start Launcher

To start the Launcher, do the following:

1. In the Control Tower menu, click the Digital Workers section, click View All, and find to the Evelyn: Adverse Media Monitoring group.

2. In the group, find the variation you wish to use and click it.

   To configure the number of ad-hoc search tasks that will be created in Workspace, click Prepare, and go to the Investigation step > Variation. By default, a variation is created when you configure the Investigation step after the installation.

   

3. Click the Adverse Media Monitoring Launcher group to expand it, then click the Menu button (...) and select one of the following steps:

   • To run the Launcher, click Edit and Run. The Edit Business Process window appears.
   • To create another instance of the BP, click Copy. Thus you can run a new instance without impacting an existing one.

   

4. In the Business Process window, go to the Run tab and click Run this process to start the Business Process.

   

Run ad-hoc search

To run an investigation using the ad-hoc search screen, do the following:

1. Log into Workspace, find Submit Adverse Media Monitoring Investigation request vX.X, and open it:

   

2. In the Entity information group, enter data for the entity you wish to screen.

   Only Entity name is required to initiate a search. All other fields are optional but encouraged since more information on the entity enables the automation to eliminate more false-positive results.

   Information can either be uploaded via a CSV file or entered manually.

3. Review the settings in Requests details group. If necessary, in the Search Time Period box, select a different time for scanning.

   Here, you can only change Search Time Period. Other fields are configured in Control Tower and listed on this screen for reference only.

4. Review the settings in Results group:

   1. Select the Assign to me checkbox to automatically take the investigation results.
   2. Enter the one or several email addresses where to send the results. A group email is recommended to be specified in the Send copy to box, so that other team members can refer to previous investigations and their results.

5. Click the Submit button.

Once the results are ready, an email notification is sent with a link to the assignments within Workspace.

If your organization does not use the Human-in-the-loop feature, you only receive a final report. This is also indicated on the Ad-hoc search screen.

note

In some cases no results are found for the search. If this occurs, a report for each entity is created. A separate email with a link to view and download the report is sent for each entity that does not have search results. A copy of this report is also stored in the location specified during the installation and configuration of AMM.

Call AMM REST API

Adverse Media Monitoring can be invoked by calling the WorkFusion AMM REST API.

You must first configure a variation as it requires the Business Process associated to a configured variation. For the details see the Configure REST API endpoints part.

Also see Running skills via REST API.