Docs

FC-UIP-NMG-002: Argument naming convention

Argument name does not match the configured direction-based naming convention.

lowmaintainabilityuipathUiPath ST-NMG-002

What it detects

Argument name does not match the configured direction-based naming convention. 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 UiPath workflow exposes an input argument without the expected in_ prefix.

Fix guidance

UiPath

  • Prefix arguments with in_, out_, or io_ according to direction and keep the remaining name meaningful.
  • 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