Control Automatic RAM Workflow Assignment for PBS

Feature Request: Control Automatic RAM Workflow Assignment for PBS

Summary:
Ensure that users are not automatically assigned to workflow steps when adding PBS items from the RAM view. Automatic assignment to workflow steps should only occur when PBS is created from the BOE/Estimates views, preserving intentional ownership and workload control.

Problem Statement:
When PBS items are added from the RAM view, the system currently (or is expected to) auto-assign the creating user to associated workflow steps. This can result in unintended ownership, inaccurate responsibility mapping, and additional manual cleanup. Users managing PBS from RAM often act in a coordination role rather than as the actual responsible party, so automatic assignment from this context is misleading and inefficient.

Proposed Solution:
Disable automatic assignment of the current user to workflow steps when PBS items are created or added from the RAM view.
Retain existing behavior where the user is automatically assigned to workflow steps when creating PBS from BOE/Estimates views.
Optionally, provide a configuration toggle or policy setting so administrators can control whether RAM-driven PBS creation ever triggers automatic workflow assignment.
Ensure that this behavior is clearly documented in the UI or help text so users understand when automatic assignment will occur.

Benefits:
Reduces incorrect or unintended ownership assignments on workflow steps.
Minimizes manual cleanup effort to reassign or remove auto-assigned users.
Improves accuracy of RAM and workflow responsibility mapping.
Aligns system behavior with user expectations across different creation contexts (RAM vs. BOE/Estimates).