Pseudonym Resolver
On this page
Purpose
Pseudonym Resolver resolves every intact tag a Deidentifier component minted earlier in the same flow back to its original value. It closes the protected segment that component opened, so values are raw again once Pseudonym Resolver has run.
Pseudonym Resolver can resolve only tags created earlier in the same flow and chat session. Place it downstream of Deidentifier in that flow.
A Run Flow step between the two breaks that chain. Text coming back from another flow keeps its tags, because those tags belong to that flow rather than this one. Give that flow its own Deidentifier and Pseudonym Resolver pair instead.
When to use it
- Put the real value back into an Agent's or model's response right before the user sees it.
- Restore a real identifier immediately before the step that needs it, rather than only at the end of the flow. For example, restore an actual email address or record number before a lookup that requires it.
How to use it
- Place Pseudonym Resolver downstream of the Agent or model that consumed a Deidentifier component's output earlier in the same flow.
- Connect that Agent's or model's response to Input.
- Connect Restored Output to Chat Output, or to any further step that needs the original values instead of tags.
Every component placed after Pseudonym Resolver receives the original values, not tags. Place it after the last step that should see a tag and before the first step that needs the real value.
Configuration
| Setting | What it controls | Recommended starting point |
|---|---|---|
| Input | The Message value checked for known tags. | Connect the response coming out of the protected segment, right before it needs to leave that segment. |
Pseudonym Resolver has no other setting. There is nothing to select or tune beyond what value to restore.
Expected result
Every tag Pseudonym Resolver recognizes from the current flow's session is replaced with its original value. A tag it does not recognize is left unchanged. Only the Message text is restored; every other field passes through unchanged.
Example
Input
Contact [EMAIL_ADDRESS_1] for details.
Restored Output
Contact john@example.com for details.
For a complete raw-to-tagged-to-restored round trip across a protected segment, see the Deidentifier example.
The tag number is an example. The actual number depends on tags already used in the session.
Related components
- Deidentifier is the required upstream pair. Pseudonym Resolver has no standalone use without it.
- Chat Output is the typical destination for the fully restored answer.