Edit agreement metadata (non-budget change / no approval)

[jonnalley]

User Story

As a COR or other team member, I need to edit non-financially impacting contract metadata where there are budget lines in Planned or Executing status (and they remain in the current status), so that I can continue to refine the plan or approach for a particular agreement.

Preconditions

• An existing or new contract exists in OPS with at least one budget line in either Planned or Executing status. Ideally at least one BL in each status

Acceptance Criteria

• Authorized users are able to make and submit contract metadata changes that are not financially-impacting (i.e. not procurement shop) and the changes are successfully persisted without altering the status of Planned or Executing BLs. Authorized users would be limited to Project officer, named team members, Division Director linked to associated CANs, and System Admin(s).
• As an exception to the above, users (still) ought not be able to change the agreement type as only contracts have been done at this time.
• 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
• User cannot make agreement metadata changes if one or more BLs are in Obligated or higher status unless the user is a System Admin (are we able to qualify based on user/group role at this time?)
• Upon successful committal of any edited metadata, 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.
• User can choose to cancel making any changes and leave the pre-existing values for any metadata persisted.

---

Tests

Tasks

UX

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

Dev

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

• Discovery around Editing Agreements with Financial-impacting info requiring Approvals (without a BL status change) #1964 and its resources/context
• A more-narrative document outlining potential scenarios and needs being addressed is here
• FigJam process visual
• Figma dev-ready frame
• Temporary home of business rules