feat(action-center): extend taskSourceMetadata on CreateTask/CreateEscalation - #1873
Draft
dushyant-uipath wants to merge 2 commits into
Draft
feat(action-center): extend taskSourceMetadata on CreateTask/CreateEscalation#1873dushyant-uipath wants to merge 2 commits into
dushyant-uipath wants to merge 2 commits into
Conversation
…k/CreateEscalation HITL tasks created via interrupt(CreateEscalation(...)) have no way to carry caller-supplied context (e.g. a conversational-agent id) in taskSource.taskSourceMetadata today: it is built entirely from UiPathConfig state with no extension point. Add an optional task_source_metadata dict to CreateTask (inherited by CreateEscalation) and TasksService.create/create_async, threaded through _create_spec and merged into taskSourceMetadata on top of the built-in InstanceId/FolderKey/JobKey/ProcessKey keys. Additive only; no change for existing callers.
…ustom_metadata Clearer internal param name; no behavior or public-API change.
dushyant-uipath
commented
Aug 27, 2026
|
|
||
| def _apply_task_source( | ||
| payload: Dict[str, Any], source_name: str, is_debug: bool = False | ||
| payload: Dict[str, Any], |
Contributor
Author
There was a problem hiding this comment.
Get the alignment back to the original one so the difference doesn't look this big
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
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.
AGVSOL-123456 / ACTN-123
Summary
interrupt(CreateEscalation(...))cannot carry caller-supplied context (e.g. a conversational-agent id) intaskSource.taskSourceMetadatatoday. That dict is built entirely fromUiPathConfigstate (InstanceId/FolderKey/JobKey/ProcessKey) with no extension point.task_source_metadata: dict[str, Any] | Nonefield toCreateTask(inherited byCreateEscalation) and toTasksService.create/create_async, threaded through_create_specinto_apply_task_source, where it's merged on top of the built-in keys (caller keys win on collision).UiPathResumeTriggerCreator._handle_task_triggerso a coded agent'sinterrupt(CreateEscalation(task_source_metadata={...}))actually reaches the API call.None, no behavior change for existing callers.Context
Raised from an internal ask (Verticals HITL / conversational-agent integration, tracked as ACTN-123). A coded agent needs to pass a
conversationalAgentIddownstream on the Action Center task so a Slack/Teams bot can resolve which conversational agent to associate with a HITL task.taskSourceMetadatais the natural home for this since it already carries job/process correlation ids, but the current model has no way to extend it. This is a draft for the platform team's review; the field name/shape can change, and it could instead fold intoactionable_message_metadataif that fits the wire contract better.Test plan
test_create_merges_task_source_metadata,test_create_async_merges_task_source_metadata,test_create_omits_extra_task_source_metadata_when_unset) inpackages/uipath-platform/tests/services/test_actions_service.py