Add Resource Code Mapping to Proposal Templates

Feature Request: Resource Code Mapping in Proposal Templates

Summary:
Enable proposal templates to include a Resource Code Mapping tab, allowing users to predefine and maintain a standard mapping between resources and their associated codes. This will let new proposals inherit the correct mappings automatically, reducing repetitive setup and ensuring consistency across all proposals.

Problem Statement:
Today, users must repeatedly configure resource code mappings for each new proposal, even when the mappings are identical across proposals and change infrequently (e.g., annually). This repetitive setup is time-consuming, prone to manual errors, and creates inconsistency when different team members configure mappings slightly differently. The lack of a reusable, template-level mapping mechanism results in unnecessary administrative overhead and configuration drift.

Proposed Solution:
Add a “Resource Code Mapping” tab to proposal templates that allows users to:

• Define and maintain mappings between resources and their corresponding resource codes directly on the template.

• Save these mappings as part of the template so that any new proposal created from the template automatically inherits the predefined mappings.

• Edit mappings at the template level and optionally propagate updates to new proposals created after the change (without retroactively altering already-issued proposals, unless explicitly requested via a controlled update mechanism).

• Validate mappings to prevent invalid or incomplete configurations (e.g., missing codes for active template resources).

Benefits:

• Eliminates repetitive configuration work by reusing the same resource code mappings across all proposals based on a template.

• Reduces the risk of errors and inconsistencies in resource-coding, improving data quality and reporting accuracy.

• Saves time for users, especially when mappings only change infrequently (e.g., annually).

• Standardizes proposal setup across teams by centralizing mapping logic in templates rather than per-proposal configuration.