Skip to main content

Tags

A tag is a weighted label. When it is present on a flow result, its weight pushes the score it feeds. Tags are the “what” of scoring; contextual factors are optional multipliers on top.

This page covers where tags come from, which ones ship by default, and how to create and assign a custom tag.

Where tags come from

AML screening

Global AML tags are attached automatically when a sanctions, PEP, or adverse-media match carries that topic. You do not assign role.pep or sanction by hand; the screening result emits them. See Default AML tags.

Form answers

A field in the form builder can emit a tag when the user answers a certain way. Form scoring.

Flow Builder action

The Assign Risk Tags node attaches tags you already created, typically behind a condition (for example “document review failed”).

Manual review

A reviewer can assign or retract a tag on the flow result. Reviewing Scores.

Default AML tags live on the Risk / AML score definitions. Custom tags you create belong to the definition you attach them to (Risk, or a score you added).

Create and assign a custom tag

Use a custom tag when the signal is yours: an internal classification, a questionnaire answer, a failed manual check. Do not recreate AML topics; those already arrive from screening.

1. Create the tag

  1. In the Zyphe Dashboard, open Compliance → Score Definitions.
  2. On the score that should receive the tag (usually Risk, or a custom score such as supplier_risk), click Manage tags.
  3. Click Add a tag. Give it a name and a weight. Leave it Active.

The tag now exists but does not fire until something assigns it.

AML-only overrides (changing the weight of role.pep without creating a new tag) are done on Risk Scoring Tags, not here. See Configurable tag weights.

2. Assign it, pick one path

From a form (most common for questionnaires): in the form builder, open the field, expand Score, add a score tag, pick the score and the tag, set the weight, and optionally an Only when condition. See Form scoring.

From Flow Builder (conditional, cross-step):

  1. Open the flow in Flow Builder.
  2. Add an Assign Risk Tags action node.
  3. Select one or more custom tags created in step 1.
  4. Wire the node behind a switch (or after the step whose outcome you care about), so the tag is assigned only when the condition matches: for example document verification failed, nationality in a set, or a form field equals a value.

The action only lists tags you have already created. Create the tag first, then associate it.

From review: on the flow result Scores tab, Add tag. Useful for a finding that is not in the flow.

3. Confirm it landed

Complete a test run (or re-evaluate an existing result). The Scores tab lists assigned tags with source (form, workflow action, or reviewer) and weight. If the tag is missing, the condition did not match, or the tag is inactive on the definition.