FEE and POP Table for Custom Task Fields

Feature Request: Summary Field-Linked Fee and POP Toggles

Summary:
Introduce configurable Fee (%) and Period of Performance (POP) options directly on custom task field values, allowing users to automatically populate Fee and POP dates on task creation based on the selected value (e.g., CLIN). Instead of a separate table, admins toggle Fee and/or POP on for specific custom field values, define the corresponding Fee and POP start/end dates per value, and control whether those values are auto-applied, locked, or editable based on field requirements and user permissions.

Problem Statement:
Today, users must manually enter Fee and POP for each task, even when those values are driven by standardized structures such as CLINs. This is repetitive, time-consuming, and prone to data entry errors. There is no centralized, authoritative configuration that ties Fee and POP directly to the custom task field values in use, and no mechanism to control when users can or cannot override those values. As a result, proposals can contain inconsistent Fee and POP values across tasks, and updating values when business rules change requires significant manual effort.

Proposed Solution:
Add Fee/POP configuration controls directly to custom task field values so that admins can define Fee (%) and POP start/end dates per value, with strict rules about which fields can drive Fee and POP.

• Field-level Fee/POP toggles:

  • For each eligible custom task field, allow admins to toggle on support for Fee and/or POP (start and end dates) on that field’s values list.

  • When Fee is toggled on for a custom task field, add a Fee (%) column to that field’s values list so admins can specify a Fee value per row/value.

  • When POP is toggled on for a custom task field, add two columns to that field’s values list for POP start date and POP end date so admins can specify dates per row/value.

  • Enforce that only one custom task field at a time can have Fee toggled on, and only one custom task field at a time can have POP toggled on. The Fee and POP driving fields do not need to be the same field.

  • Admins enter the Fee and/or POP values directly in the value rows for the field that has Fee and/or POP toggled on.

• Behavior on task creation/update:

  • When a user selects a value in the custom task field that has Fee and/or POP toggled on, automatically set the task’s Fee and POP dates from the corresponding value row configuration (Fee %, POP start, POP end).

  • If the driving field is marked as required:

    • Lock the Fee and POP fields so standard users cannot manually edit them.

    • If the configured Fee/POP values on the values list are updated, automatically propagate updated Fee and POP values to all tasks/proposals using that required field.

  • If the driving field is not required:

    • On selection, populate Fee and POP once from the configured value row, but allow users to edit these values afterward.

    • If the user has already entered Fee and/or POP before selecting the value, display a confirmation popup indicating that their existing Fee and/or POP will be overwritten by the configured values and require acknowledgement before proceeding.

• Permissions and overrides:

  • Introduce a role-based permission that allows designated users to override Fee and POP values even when the driving custom task field is marked as required.

• Handling changes to required status:

  • If an admin attempts to set the Fee/POP-driving custom task field to required when it is already in use on a proposal:

    • If any associated Fee or POP values are blank based on the configured values list, prevent the field from being set to required and notify the admin to resolve missing values.

    • Otherwise, display a confirmation popup that the admin must acknowledge to proceed, then automatically update all existing Fee and POP values on the proposal to match the configured values for the selected field values.

Benefits:

• Reduces manual data entry and minimizes errors in Fee and POP values across tasks by tying them directly to custom task field values.

• Provides a single source of truth for Fee and POP configuration via the values list of the designated driving fields, simplifying maintenance when rules change.

• Ensures consistency and compliance by enforcing required values where appropriate, while still allowing controlled exceptions via permissions.

• Speeds up task creation and proposal setup by automatically applying correct Fee and POP values whenever a linked value is selected.

• Improves auditability and confidence in proposal data through standardized, centrally managed Fee and POP settings on custom task field values.