🔴 PS: clearance rule sandbox transaction and person data might be in UPPER case (like IBANs etc)

To learn vanilla JMESPath logic and functions go to https://jmespath.org.

• JSON payload clearance rule can access
• Custom functions

We recommend following structure for the clearance rules:

{ naming variables for readability } |
{ some operations on variables } |
 boolean values to note if a condition is met or not 

Things to note

• | is the pipe operator and @ refers to the current element being evaluated. E.g. the rule below simply returns {"a": [1,2,3]}. )

  {a : [`1`,`2`,`3`]} | @
  

  it is equivalent to write a[0] and a|@[0]

• First two lines (variable definition and variable operations) are optional and are omitted for simpler rules.

• for performance we recommend starting rule with simple checks

hit.type == 'PERSON' &&
(*rule*)

• When arrays of tokens (name parts) are needed for operations we recommend
  • when matching private persons
  • when matching legal entities

Playing around in sandbox

• look for a screening alert

• check the id of screened person or transaction

• go to https://demo.salv.com/screening/clearance-rules/sandbox or https://app.salv.com/screening/clearance-rules/sandbox

• select corresponding Entity Type, insert corresponding External ID and as JMESPath expression type @ , press Search

  

• you can also write dummy “json” for testing rule ideas and put it into JMESPath Expression cell, but you still need the screening alert from the system

{entity: 
	{first_name: 'Sheldon',
	 last_name: 'Cooper',
	 active: `true`,
   expected_turnover: `50000`
	}
} | 
entity.first_name == 'Sheldon'