feat: resolve ArgumentEmail and ArgumentGroupName recipients at runtime#735
Open
dushyant-uipath wants to merge 1 commit intomainfrom
Open
feat: resolve ArgumentEmail and ArgumentGroupName recipients at runtime#735dushyant-uipath wants to merge 1 commit intomainfrom
dushyant-uipath wants to merge 1 commit intomainfrom
Conversation
Updates resolve_recipient_value() in escalation_tool to handle the two new argument-driven recipient types. Each type carries an argument_name that is looked up in the tool's runtime kwargs to produce a concrete email or group-name TaskRecipient. Follows the same pattern as AssetRecipient resolution. Backward compatible -- input_args defaults to None. Depends on uipath-python adding ArgumentEmailRecipient and ArgumentGroupNameRecipient to uipath.agent.models.agent. 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
Updates
resolve_recipient_value()inescalation_tool.pyto handle the two new argument-driven recipient types. At runtime, each type'sargument_nameis looked up in the tool's input kwargs to produce a concreteTaskRecipient— the same pattern used forAssetRecipientresolution today.Changed files
src/uipath_langchain/agent/tools/escalation_tool.pyArgumentEmailRecipientandArgumentGroupNameRecipienthandling;resolve_recipient_valueaccepts optionalinput_args; call site passeskwargsNotes
input_argsdefaults toNone, all existing callers unaffectedArgumentEmailRecipientandArgumentGroupNameRecipientRelated
Test plan
ArgumentEmailrecipient,argument_name="myEmail", run withmyEmail="test@example.com"— verify Action Center task created with correct assigneeArgumentGroupName🤖 Generated with Claude Code