Budget Change: Edit Procurement Shop (including prompt for send to approval)

[jonnalley]

User Story

As a COR, I need to edit the procurement shop on an agreement with with no BLs in a status higher than Planned, and know that it requires an approval, so that I understand how my edit will impact the overall budget

Preconditions

• A contract exists with at least one budget line in Planned status but no budget lines in any status higher than that.

Acceptance Criteria

• On a given existing contract, authorized users are able to select a different procurement shop from the one currently selected and the changes are successfully persisted without altering the status of Planned budget lines. Authorized users would be limited to Project officer, named team members, Division Director linked to associated CANs, and System Admin(s).
• Changing the procurement shop should not be allowed if the contract has any BLs in Executing or higher status unless the user is a System Admin (are we able to qualify based on user/group role at this time?)
• The user should be aware that making the procurement shop change will require re-approval
• Validation rules would still need to be enforced on contract metadata such that required attributes based on the associated BL status can't be emptied out or otherwise made invalid
• Upon successful committal of the pending procurement shop change, if a given contract has one or more BLs in Planned status such that changing the Procurement shop requires approval, the stored fee amount should not change at this time
  • A contract with only draft BLs should have all the fees updated based on the procurement shop change.
• Upon successful committal of the pending procurement shop change, relevant entries should be recorded in the event/history table(s) of who made what changes when and this event should be properly rendered in the history of changes to the agreement.

---

Test

• Upon submitting the new procurement shop for approval, the agreement should still have the original procurement shop in place/rendered until it's approved.
• If all BLs are in draft state, no approval would be required anyway.
• If at least one BL is in planned state, approval for the proc shop change would be required.
• Even if approval is required, original fees shown pre-change would still persist until approved.

Tasks

UX

• designs are already done as part of Discovery around Editing Agreements with Financial-impacting info requiring Approvals (without a BL status change) #1964

Dev

• essentially encompassing what Update the storage and reference data for a BLI procurement shop fee. #1473 was intended to do.

Definition of Done Checklist

• UI works as designed (UX team)
• PR(s) have been merged to main
• Design/tech debt eliminated
• New design/tech debt documented (if applicable)
• Build process updated
• Documentation updated or added
• Feature flags/toggles created

Additional Context & Resources

• A more-narrative document outlining potential scenarios and needs being addressed is here
• FigJam process visual
• Figma dev-ready frame
• We heard that fees can change for each fiscal year. Reference discussion

[fpigeonjr]

🤔wonder if this bug #2079 will be resolved with this user-story?