Skip to main content

Using GRID OOTB Integration

GRID Version​

Fenergo SaaS supports RDC RESTEasy API Version 2.1.5 Integration Pack.

The integration requires Client Alert Decisioning (iCAD) to be enabled in Grid for proper functionality.

GRID Analyst Review​

If a GRID customer has Analyst Review enabled, screening results are sent to a GRID Analyst team to do an initial match resolution before being returned to Fenergo SaaS.

For those Firms that have GRID Analyst Review enabled, Fenergo SaaS will wait for the results to be reviewed and present them in the screening resolution task when ready. The GRID Analyst team operates with an SLA of 24 to 48 hours, meaning we should expect to receive the results in Fenergo SaaS within 48 hours of the search being initiated. To adhere to this time-frame, when a request is sent to GRID for Analyst Review, Fenergo SaaS initially wait for 24 hours before beginning hourly polling. There is a timeout in place if no results are received after 1 week.

info

This depends on a feature being turned on or off at a tenant level.

GRID Service Url US​

For clients using the US version of Grid instead of the EU version, a feature must be activated at the tenant level.

GRID Tracking Id​

The tracking ID enables the assignment of a unique identifier to each submitted name, preventing the occurrence of duplicate hits within the same journey for entities that have already undergone screening. This means that if the same entities is screened twice within a journey, there will be no results returned the second time the entity is screened. It is important to note that this functionality applies within the same journey but not across journeys.

GRID Ongoing Screening​

Ongoing Screening is supported in GRID. When enabled in Fenergo SaaS, all entities screened through Fenergo SaaS will be enabled for Portfolio Monitoring (OGS) in GRID.

info

This depends on a feature being turned on or off at a tenant level.

Grid and Data Migration​

For clients planning a migration and wishing to enable entities for ongoing screening without resolving the hits, we provide this capability through feature enablement. The following steps outline the process for this:

  • Enable the LoadOnly Flag in FenX

    • The LoadOnly flag is passed from FenX to Grid as part of the On Demand Screening (ODS) task.
    • When this flag is enabled, it instructs Grid suppress any hits in the screening response.
    • This prevents the requirement for match resolution during migration and allows screening journeys to complete automatically.
    • Important: This flag is currently a feature flag in FenX, so must ask your FenX contact to enable this flag for the relevant tenant before starting the migration.

  • Ensure Ongoing Screening Is Enabled in FenX

    • Before starting, verify that the "Ongoing Screening" toggle is active in the Grid Screening Configuration within FenX.

  • Run the Event Ingress Call

    • Use the Event Ingress API to initiate screening journeys for the migrated entities. You will need the entityId and Legal Entity name for each entity to make this call.

  • Journeys will be initiated and completed automatically

    • The screening journeys will complete automatically.
    • Entities will be subscribed to Ongoing Screening either as part of the Close Screening task or through a separate Subscribe to Ongoing Screening task - depending on the configuration of journey.

  • Disable the LoadOnly Flag After Migration

    • Once all entities have been migrated, ask your FenX contact to disable the LoadOnly flag for the tenant.
    • This will restore normal screening behaviour, allowing Grid to return hits in future screenings.

  • Important Notes:

    • During the time 'LoadOnly' flag is enabled, no hits are returned from any screening performed against Grid.
    • In order to verify that entities are subscribed for OGS, navigate to the Portfolio tab in Grid where you can search for all entities subscribed for Portfolio Monitoring (Ongoing Screening). Search using the trackingId which is 'FenXEntityId', reportingId which is 'FenXTenantId'- using a name of an entity.
info

This depends on a feature being turned on or off at a tenant level.

Multiple Configuration Sets and Ongoing Screening​

Multiple configurations sets and ongoing screening is not supported in Fenergo SaaS.