Docs

FC-UIP-HCD-007: Hardcoded port

Activity attribute contains a literal port number, making the workflow brittle across environments.

mediumcredentialsuipath

What it detects

Activity attribute contains a literal port number, making the workflow brittle across environments. Flowcerta surfaces this finding from the active validation pipeline for supported file types and platforms.

Why it matters

Credentials and secret-handling findings matter because workflow files often travel through source control, export bundles, backups, and admin access paths. A secret in source quickly becomes a secret with a large blast radius.

Example violation

Activity attribute contains a literal port number, making the workflow brittle across environments.

Fix guidance

UiPath

  • Move ports into orchestrator assets or environment-specific configuration so the workflow ports cleanly between dev, staging, and production.
  • Use platform-native assets, credentials, bounded retries, and Log Message checkpoints instead of hardcoded literals or silent failure paths.
  • Revalidate the workflow after the change and confirm the finding no longer appears.

Verification steps

  1. Run validation again and confirm the rule no longer appears in the finding list.
  2. Review the changed workflow artifact directly to verify the risky pattern is gone.
  3. Capture the new validation result as evidence for the relevant owner or compliance review.

Compliance references

This page is generated from the canonical Flowcerta rule registry used by validation scoring.

Browse all rule playbooks