Rate Attribute Checkboxes for Resource Fields

Summary:
Enable users to mark individual Resource Fields in Proposal Properties as “Rate Attributes,” determining whether each field contributes to the Bid Rates or Base Rate uniqueness key for Services (Rate Builder) proposals. This gives users explicit control over rate-key behavior instead of relying on implicit field scope rules.

Problem Statement:
Currently, which Resource Fields count toward the Bid Rates uniqueness key is determined implicitly by whether a field is configured at the Proposal level or Global level. This limits user control and can make rate setup harder to manage, especially when proposal-specific requirements do not align with the existing scope-based behavior. As a result, users may be unable to define uniqueness logic in a way that accurately reflects their pricing model, leading to confusion, inconsistent rate behavior, and extra manual workarounds.

Proposed Solution:
Add “Rate Attribute” checkboxes to Resource Fields within Proposal Properties for Services (Rate Builder) proposals.
Allow users to select, on a per-field basis, whether a Resource Field should be included in the Bid Rates uniqueness key or Base Rate uniqueness key.
Decouple rate-key inclusion from the field’s Proposal or Global scope so scope no longer determines uniqueness behavior by default.
Ensure the setting is clear and easy to manage within the existing Resource Fields configuration experience.
Preserve existing proposal behavior unless a user explicitly updates the new checkbox settings, minimizing disruption to current configurations.

Benefits:
Provides users with precise control over how rate uniqueness is defined.
Reduces reliance on implicit system behavior that can be difficult to understand or predict.
Improves flexibility for complex Services (Rate Builder) proposal configurations.
Helps align rate setup with real-world pricing and resource management needs.
Decreases the need for manual workarounds and improves overall usability for users.