feat: add RunAsMe support to ProcessesService#1567
Open
dsuresh-ap wants to merge 1 commit intomainfrom
Open
Conversation
Add run_as_me parameter to ProcessesService invoke/invoke_async to support running child jobs under the calling user's identity. Also add is_conversational property to ConfigurationManager for reading runtimeOptions from uipath.json config. JAR-9434 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
github-actions
bot
added
the
test:uipath-langchain
4 tasks
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
run_as_me: Optional[bool]parameter toProcessesService.invoke()/invoke_async()/_invoke_spec()— when provided, includesRunAsMein the StartJobs payloadis_conversationalproperty toConfigurationManagerthat readsruntimeOptions.isConversationalfrom the uipath.json config fileContext
JAR-9434 — Conversational Agent API Workflow tools fail with HTTP 409 ("no unattended robot") because RunAsMe is not propagated to child StartJobs calls.
Test plan
test_invoke_with_run_as_me_true— payload containsRunAsMe: truetest_invoke_with_run_as_me_false— payload containsRunAsMe: falsetest_invoke_without_run_as_me_excludes_from_payload— no RunAsMe key in payloadtest_is_conversational_true/false/missing— ConfigurationManager reads runtimeOptions correctly🤖 Generated with Claude Code