fix: don't let the multipart body envelope param shadow real body fields

[andreitava-uip]

Summary

• For IS activities using a multipart body (bodyStructure.contentType: "multipart"), the raw connector parameter list includes an envelope-marker parameter whose name equals jsonBodySection (e.g. body, fieldLocation: "multipart"). This is IS's own convention for "wrap the JSON entity in one multipart part named X" — not real data.
• When an activity's entity schema also nests real fields under that same top-level name (e.g. Teams' chatMessage.body → body.content, body.adaptiveCardContent, fieldLocation: "body"), both got classified under the identical key in convert_to_activity_metadata. Since multipart_params was checked before body_fields, the real value was misrouted there and silently dropped by the existing "don't duplicate the envelope part" guard in uipath-platform's _build_activity_request_spec.
• Reproduced live against the Microsoft Teams "Send Individual Chat Message" IS tool: the LLM-supplied message body was silently missing from the outgoing request.
• Fix: skip the envelope-marker parameter by identity (name matches jsonBodySection and its own fieldLocation is multipart/file) so it never competes with the real body-field grouping derived from its children.

Test plan

• Added test_multipart_envelope_marker_does_not_shadow_nested_body_field — confirmed it fails without the fix and passes with it
• uv run pytest tests/agent/tools/test_integration_tool.py — 69 passed
• uv run pytest (full suite, all extras) — 2799 passed, 3 skipped (unrelated, uip CLI not on PATH)
• ruff check / ruff format --check / mypy clean on changed files
• Verified live end-to-end against a real UiPath tenant's Teams connector: the message body now reaches the actual HTTP request and a real Teams message is sent successfully

[Copilot]

🟢 Approval recommended

The change is narrowly scoped, matches the described root cause, and is covered by a focused regression test that exercises the reported failure mode.

Pull request overview

Fixes a subtle parameter-classification bug in the Integration Service tool metadata mapping for multipart activities, preventing IS’s multipart JSON-envelope marker parameter (e.g. name == jsonBodySection) from shadowing real entity fields that share the same top-level name (e.g. body.content).

Changes:

• Compute content_type and json_body_section early and skip the multipart/file envelope-marker parameter during location mapping in convert_to_activity_metadata.
• Add a regression test ensuring nested body.* fields are preserved and not misrouted into multipart_params.
• Bump package version to 0.16.17 in project metadata and lockfile.

File summaries

File	Description
src/uipath_langchain/agent/tools/integration_tool.py	Skips the multipart JSON-envelope marker param so it cannot compete with real body.* fields during parameter location mapping.
tests/agent/tools/test_integration_tool.py	Adds a regression test covering the multipart envelope-marker vs nested body-field name collision.
pyproject.toml	Bumps package version to 0.16.17.
uv.lock	Updates locked editable package version to 0.16.17.

Review details

• Files reviewed: 3/4 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud