Transaction Monitoring clients can now set up sanctions screening checks for the counterparties that their users are transacting with to ensure ongoing compliance and mitigate counterparty risk. The transacting counterparties will be checked for exact and ‘fuzzy’ matches (e.g. abbreviations, misspellings, transliterations) against the most up-to-date watchlists using our data providers.

As with entity sanction screening, results are surfaced in Case Management to allow agents to take prompt action upon suspicious activity.

To get started with ongoing sanction screening, please reach out to your CSM or [email protected].

Clients can now set expiration dates for Journeys which will move applications to an end state based on the configured time-frame. This ensures applications do not remain in a pending state indefinitely and enables more accurate reporting on application decisioning.

To set an expiration time-frame for a Journey, navigate to the Journeys page and click on the ellipsis menu for the Journey and select ‘Set Application Expiration’.

Toggle the ‘Expiration Off’ button and set the expiration timeframe in the ‘Days to Expiration’ field before clicking ‘Save’.

If an application then runs through this Journey and hits the expiration date, the application will automatically move to a ‘Expired’ terminal node and end state.

SDK Theme Customizations

Clients using the Alloy SDK can now customize colors and components for Alloy-built plugins in the SDK. This feature allows Alloy clients to style plugins to better match their own branding. For example, this SDK matches the green and grey colors of the company.

There are three ways to pass styling into the SDK, listed in hierarchical order:

1. initParam.colors (the color parameter that previously existed in the SDK init params)
   1. “Primary” will override the color of the buttons
   2. “Secondary” will override the hover color of the buttons
2. initParam.customStyle.componentOverride
3. initParam.customStyle.theme

See API docs for more details here.

Clients can now have applications automatically assigned to agents when they require a Review. This feature evenly distributes applications across all agents that have permission to review an application.

Instructions below

1. If a client wants to use the auto-assignment functionality, they’ll need to add permissions to the specific role types through the ‘Settings’ page

• The ‘Agent can be auto assigned Journey Applications’ permission should be checked off

2. Once that permission is added, anytime an application requires a Review, it’ll be automatically assigned to the agent with the least number of applications assigned to them.

A new type of OAuth has been added to our webhooks called “Password” flow. This flow is compatible with Salesforce. Teams can use the username-password flow to authorize a client via a connected app that already has the user’s credentials.

Users can configure this in the webhooks modal in the Settings page

Required Fields:

• Client ID
• Client secret
• Token URL
• Username
• Password

Optional Field:

• Access token encoding

Transaction Monitoring clients can now manually create new cases in Case Management to track cases that are identified outside of the Alloy system (such as an email or phone call) to better consolidate all information and documentation relating to a suspicious activity investigation. Previously, cases were automatically generated based off of the workflow outcomes.

To create a case:

• Click ‘Create Case’ on the Case Management home page
  

  

• You will be prompted to enter an entity identifier (known as the entity token in the Alloy system or an external ID that is passed from your system to Alloy), associate a manual alert type, and enter any notes you may have on the case.
  
  
  
  

  • Please note that cases can only be created for known entities (i.e. it must be an existing entity in the Alloy system).

  • You can only have one open case per case type for a given entity.
    
    

• Click ‘Create Case’ and you will be redirected to the new case page.

• The new alerts will appear in the ‘Alerts Triggered’ section with “(manual)” identifier.
  

  

Note: Agents must be appropriately entitled (i.e. have case editing permissions) in order to create cases manually.

Transaction Monitoring clients can enroll users in recurring sanctions screening checks against the most up-to-date watchlists to stay on top of risky customers. Once enrolled, the entity will automatically be screened in real time every time a watchlist is updated in the future. Coverage can be tailored to include sanctions lists, PEP screens, and/or adverse media checks through our pre-built integrations with data partners specializing in watchlist screening.

If there is a match, a case will automatically be created for action in Case Management. Agents conducting due diligence can further drill down into the specific watchlist that triggered the alert and match confidence score to make informed decisions.

To get started with ongoing sanction screening, please refer to our support article or reach out to your CSM or [email protected].

Users can now assign applications to either themselves or to other users - depending on their role & permissions.

Users can filter by Assignee so they can only view applications assigned to the filtered user. Filters will also now automatically be saved per user that’s signed in and will only be cleared if the user manually clears them.