Configurable validation for BOE calculation discrepancies

Feature Request: Configurable validation for BOE calculation discrepancies

Summary:
Introduce configurable validation options that control how BOE records behave when there are discrepancies between calculated values and direct user inputs. The feature should allow admins or power users to choose whether the system simply warns, blocks workflow transitions, or blocks saving entirely when remaining calculation differences exist, reducing the risk of unnoticed errors.

Problem Statement:
Today, users can save a BOE even when there is a remaining difference between calculated values and manually entered data (for example, when spreading more hours than the calculated amount). These discrepancies can go unnoticed until later in the process, causing incorrect totals, rework, and delays. There is no flexible way to enforce validation rules at key points (such as on save or on workflow transition), which makes it difficult for teams to maintain data quality and consistent review standards.

Proposed Solution:
Provide a configurable validation framework for BOE records when calculation discrepancies (remaining values) are present. This should include:

• An option to only display a warning on save when a discrepancy exists, allowing users to proceed but clearly indicating potential issues.

• An option to validate on workflow transition (e.g., moving the BOE to a review or approval step) and block the transition if discrepancies remain, with clear, detailed messages about the specific problems.

• An option to validate on save and prevent saving the BOE when discrepancies exist, enforcing strict data integrity in environments that require it.

• Clear, actionable error or warning messages that identify which calculations and fields are out of balance, so users can quickly correct them.

• Administrative or workspace-level settings to choose the desired validation mode (warn only, validate on workflow, validate on save) to match different team or project requirements.

Benefits:

• Reduces calculation errors by preventing or highlighting BOEs with unresolved discrepancies.

• Improves data quality and consistency across BOEs, especially in review and approval workflows.

• Decreases rework and downstream corrections caused by unnoticed misalignments between calculated and entered values.

• Gives organizations flexibility to align validation strictness with their processes and compliance needs.

• Enhances user confidence by providing clear, detailed feedback when issues are detected.