Appendix 3: AMDL Scopes

The following is a list of allowed scopes in AMDL, detailing which are supported in Business Rules. A scope allows you to write expressions that refer to another value (or operand), or provide definitions. For example, the following is a scope as a reference event.amount > 100 or lists.negativeList ~# event.card. The following shows how a scope is used for a definition, rules.rule1: event.amount > 100 or state.example: event.amount). You can use certain variables for definition and reference, as highlighted in the following table.

Scope	Business Rules
	Definition	Reference
event Event data fields		✓
rules Business rules	✓	✓
state Entity-level profile data	✓	✓
globals Population-level profile data	✓	✓
values Static values	✓	✓
features Feature extraction logic for third party models(see Features) This option is currently not available.	Only in Features Editor	✓
var Transient variables	✓	✓
lists Data lists	✓	✓
acglists Public/overridable data lists (MT)	✓	✓
external External service callouts This option is managed by Thredd.		✓
models Model outputs (including risk scores)		✓
param Workflow Parameters
support Support Variables
tests Unit test expressions

 

* For more information, see Unit Tests for AMDL.