FC-UIP-HCD-008: Hardcoded database name
Activity attribute embeds a literal database / catalog name, making the workflow tied to a specific environment.
What it detects
Activity attribute embeds a literal database / catalog name, making the workflow tied to a specific environment. 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 embeds a literal database / catalog name, making the workflow tied to a specific environment.
Fix guidance
UiPath
- Use a connection-string asset, environment variable, or configurable input so the database can change 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
- Run validation again and confirm the rule no longer appears in the finding list.
- Review the changed workflow artifact directly to verify the risky pattern is gone.
- Capture the new validation result as evidence for the relevant owner or compliance review.
Compliance references
Related rules
This page is generated from the canonical Flowcerta rule registry used by validation scoring.
Browse all rule playbooks