World-Check Customer Risk Screener
Now that you have completed the basic setup of World-Check Customer Risk Screener, established a connection to World-Check One, and created your first case it is time to start designing your processes.
Automated vs. Manual Screening
In World-Check Customer Risk Screener you have the option to configure two types of screening
- Automated – initiated automatically when a specified criteria/condition is met. It requires Flows or Apex to be built to trigger the screening. Each object screened will require its own Flow/Apex. We recommend following Salesforce best practice when creating Flows.
- Manual – initiated by a Licensed User when clicking on the ‘New Screening’ button/quick action which should be added to the respective object page layout. Note the button will only work for licensed users of Customer Risk Screener as it steps the user directly into the World-Check One results page which requires a license in production. You can mimic this behavior for non-licensed users by creating a custom button which would trigger a Flow.
Helpful questions to ask yourself when designing
- What object(s) do I want to screen? Are they Standard or Custom objects?
- Is there going to be a 1:2:1 or a 1:2:Many relationship between a record and the number of Screening Cases it could generate?
- When do I want to initiate the screening of the records? Immediately when the record is created or later when the record, or a linked record, meets a certain set of criteria? E.g. Screen an account when a child opportunity gets to a particular sales stage, or goes through an approval process etc.
- When do I want to set a record for Ongoing Screening? E.g. if the account record becomes an active customer and the record type or status is changed?
- Do I want to disable Ongoing Screening for a record at any point e.g. if an account record is no longer a customer.
- Do I want to keep a screening case updated and re-screened if a value on the source record changes e.g. Account Name or Contact Name is changed, additional secondary identifiers such as Date of Birth are added.
- Do I want to have a method of manually triggering or suppressing screening for my existing data, or data I may later import into Salesforce? E.g. consider the impact that data jobs can have on your trigger conditions
- Do I want to treat all records the same or will some records be screened against different World-Check One Groups with different screening settings e.g. screen accounts in markets X and Y against a "High Risk" Group that includes the full World-Check data set with fuzzy matching, and all other accounts against a "Low Risk" Group which excludes certain World-Check data sets (keywords) and has tighter match thresholds?
Real time Flows, timed based Flows or scheduled Apex?
Once your process is designed you will be able to configure a Flow or custom Apex to:
- define the entry criteria for your paths
- call an Apex Class to trigger the screening and define the variables passed to the screening case
Whether you decide to go with real time Flows, time based Flows or scheduled Apex depends on the volume of records you anticipate will need to be screened.
- Real time Flows work well when there are volumes < 1000 records within a transaction. Create and Update/Rescreens can be handled in the same Flow
- Time based Flows work well when there are volumes < 1000 records when the time based trigger is met. One consideration for time based Flows is that you will need to split Create and Update/re-screen actions into separate Flows
- Scheduled Apex works well for organisations that are dealing with many thousands of records, and do not need an immediate screen results.