Docs
FC-UIP-TPL-001: Invoked file template
Project contains template provenance markers indicating a workflow was created from a file template.
What it detects
Project contains template provenance markers indicating a workflow was created from a file template. Flowcerta surfaces this finding from the active validation pipeline for supported file types and platforms.
Why it matters
This finding matters because it weakens workflow reliability, security posture, or audit readiness.
Example violation
A UiPath project still carries local template artifacts or workflow metadata showing a file template was used as the base model.
Fix guidance
UiPath
- Remove template-derived workflows or rebuild them from approved blank or standard workflow starting points.
- 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