credentials: Add AI-generated XAML activity docs for Credentials package [STUD-79292]#530
Conversation
|
claude has found some potential issue (at least one - missing doc for GetCredential - seems valid) |
|
@viogroza Thanks for the review. Reviewed the Claude findings:
No changes were needed for this PR. |
Documentation Accuracy ReviewCross-verified the 5 doc files against the activity source code, ViewModels, and metadata JSON using two independent analysis passes (one treating docs as source of truth, one treating code as source of truth). Confirmed AccurateAll property tables, types, kinds (InArgument vs Property), defaults, required/optional markers, XAML examples, and enum references check out across all 4 activities and the overview. The omission of Issues Found1. DeleteCredential.md — unverifiable behavioral claim
The code at 2. AddCredential.md — password mutual exclusion edge caseThe "neither provided" check uses
The docs say "Provide exactly one of Not doc bugs, but noticed in passing — metadata JSON issues
Summary
|
Documentation changes:
- DeleteCredential.md: Qualify the 'returns false' behavior claim by noting it depends on external CredentialManagement library
- AddCredential.md: Document empty string edge case in password mutual-exclusion validation
Metadata JSON fixes in ActivitiesMetadataWindows.json:
- Fix shortName copy-paste for DeleteCredential (was 'AddCredential')
- Fix shortName copy-paste for GetSecureCredential (was 'AddCredential')
- Fix shortName copy-paste for RequestCredential (was 'AddCredential')
- Fix GetSecureCredential CredentialType displayNameKey (was using AddCredential key)
- Fix GetSecureCredential CredentialType tooltipKey (was using AddCredential key)
- Fix typo in GetSecureCredential Password category name ('Outpu' -> 'Output')
|
Fixed all issues from the documentation accuracy review: Documentation updates:
Metadata JSON corrections (ActivitiesMetadataWindows.json):
Commit: f38b1c1 |
|




What changed?
Added structured markdown documentation for all four activities in the UiPath Credentials package, plus a package overview:
All files follow the per-activity reference format: property tables (type, default, description), valid combinations, and copy-paste XAML snippets.
Why?
These docs are generated to support LLM CLI tooling (Claude Code and similar agents) that need structured, machine-readable activity references to assist with automation authoring. Covers the full Credentials package surface area.
Jira Link
STUD-79292
Dependencies