feat: add ArgumentEmail and ArgumentGroupName escalation recipient types#1521
Open
dushyant-uipath wants to merge 1 commit intomainfrom
Open
feat: add ArgumentEmail and ArgumentGroupName escalation recipient types#1521dushyant-uipath wants to merge 1 commit intomainfrom
dushyant-uipath wants to merge 1 commit intomainfrom
Conversation
Adds two new recipient types to support argument-driven assignees in escalation channels. The assignee email or group name is resolved from a named input argument at runtime, rather than being fixed at design time. - ArgumentEmail (type=7): resolves to an email recipient - ArgumentGroupName (type=8): resolves to a group-name recipient Both carry argumentName (snake_case: argument_name) which is looked up in the execution input at runtime by the escalation tool layer. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds two new recipient types to the escalation data model to support argument-driven assignees — where the assignee is resolved from a named input argument at runtime rather than being fixed at design time.
7ArgumentEmailargument_name: str8ArgumentGroupNameargument_name: strBoth extend
BaseEscalationRecipientand are included in theAgentEscalationRecipientdiscriminated union.Changed files
src/uipath/agent/models/agent.pyRelated
Test plan
{ "type": 7, "argumentName": "assigneeEmail" }— verify it producesArgumentEmailRecipient(argument_name="assigneeEmail")ArgumentGroupNameRecipient🤖 Generated with Claude Code