fix: populate inputSchema and outputSchema for coded agents #1042
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
Fixes the extraction of
inputSchemaandoutputSchemawhen reporting eval runs to Studio Web, ensuring proper schema population for both coded and low-code agents.Changes
_extract_agent_snapshot()to support low-code agents by reading schemas directly from agent JSON files (e.g.,agent.json)entry-points.jsonTechnical Details
The method now follows this logic:
inputSchemaandoutputSchemafrom the agent fileentry-points.jsonfor coded agentsTesting
Added comprehensive test suite for agent snapshot extraction covering:
Development Package
uipath pack --nolockto get the latest dev build from this PR (requires version range).