BOE Name and Resource Templates Proposal property level vs system level

Feature Request: Proposal-Level Resource ID Templates

Summary:
Enable users to define the Resource ID field format at the proposal level instead of only at the system level. This would allow each proposal to control which resource fields are used in the Resource ID sent to CE, whether the proposal was created from a template or built independently.

Problem Statement:
Currently, BOE Pro only allows the Resource ID field format to be configured globally, such as [Resource Name][Cost Center]. Because this setting drives the Resource ID field in CE, all proposals must use the same format regardless of their specific needs. This creates inefficiency for teams that need different combinations of resource fields for different proposals and limits flexibility when a proposal requires a simpler or more tailored Resource ID structure.

Proposed Solution:
Allow the Resource ID field format to be configured at the proposal level in addition to the existing system-level setting. Proposal templates should support a default Resource ID configuration that can be carried into new proposals. Users should also be able to define or override the Resource ID format directly within an individual proposal, even if the proposal was not created from a template. The configuration should support selecting different resource fields or a single field as needed, and the selected format should drive the corresponding Resource ID value passed into CE.

Benefits:
Provides greater flexibility for proposal-specific resource formatting needs. Reduces the need to force all proposals into a single system-wide structure. Improves alignment between BOE Pro and CE by allowing Resource ID values to reflect the needs of each proposal. Supports more reusable and adaptable proposal templates while still allowing manual control when needed.

* * *