Docs

FC-UIP-NMG-017: Class name matches default namespace

Workflow class name matches the project default namespace.

mediummaintainabilityuipathUiPath ST-NMG-017

What it detects

Workflow class name matches the project default namespace. Flowcerta surfaces this finding from the active validation pipeline for supported file types and platforms.

Why it matters

Maintainability findings matter because they amplify operational drag over time. Bots with deep nesting, arbitrary waits, or hidden assumptions are harder to review, fix, and safely change.

Example violation

A workflow class is named MyProjectName inside a project whose default namespace is also MyProjectName.

Fix guidance

UiPath

  • Rename the workflow class so it is distinct from the namespace generated from the project name.
  • 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

    Related rules

    FC-UIP-ANA-002FC-UIP-ANA-003FC-UIP-ARG-001

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

    Browse all rule playbooks