Create Budget Lines

[jonnalley]

User Story

As an OPRE staff member, I want to create budget lines on agreements so I can know what items make up an agreement

Acceptance Criteria

• User can create a properly-formatted budget line entry that is persistently stored
• User should see an indication of some kind that the creation was successful
• The budget line's status should default to "Draft"

---

Tasks

UX

• Outline a research plan / approach as needed
• Schedule interviews with budget team
• Conduct interviews with budget team
• Develop a user workflow / process map of a budget line
• Synthesize research findings
• Explore design options
• Share designs with stakeholders and other OPRE team members for feedback
• Refine the design based on Sheila's feedback
• Get more feedback from CORs
• Refine the design based on feedback
• Provide design assets with annotations to developers

Dev

• Software design and flow for a Budget Line Item
• Decide on libraries or frameworks for forms/user input
• Fix/Improve e2e testing upgrading cypress or cypress-axe as needed @tdonaworth
• Create "Research Projects" Search API Endpoints #735 - @johndeange
• Create "Agreement" Search API Endpoints(s) #736 - @johndeange
• Remove dependency of the flask sqlalchemy plugin - @johndeange
• Create "Research Project" Search component(s) #737 - @tdonaworth / @fpigeonjr
• Create "Agreement" Search component(s) #738 - @fpigeonjr
• Create "Project Preview Card" #739 @fpigeonjr
• Create "Agreement Preview Card" #740 @fpigeonjr
• Create "CANs" Search Component(s) #741 @fpigeonjr
• Create "CANs" Search API Endpoint(s) #742 - @johndeange
• Create BLI Details - "Amount" Component (Currency-Component?) #744 @fpigeonjr
• Create BLI Details - "Date Select" Component #745 @fpigeonjr
• Create BLI Details - "Notes" Component #746 @fpigeonjr
• Create BLI Preview Table Component (Bottom of BLI Creation) #747 @fpigeonjr
• Create BLI Details - "Total Summary Cards" Components  #809 - @xlorepdarkhelm
• Create BLI Review - BLI Summary Card Component #748
• Create POST /budget-line-items, and perform server-side validation #749 - @johndeange
• Flush out the SQLAlchemy "Event History" feature (use BLI as our first use-case). #750 - @johndeange
• Add User notification (floating modal) indicating BLI was created successfully. #751 - @fpigeonjr
• Create Workflow Step Validation functions #752 - @fpigeonjr
• Stub out a "Gateway" for the Authorization Checks on the API Endpoints (Use BLI as our first example case). #753 - @tdonaworth
• Populate any sample data needed
• Create additional backend components (i.e. API endpoints, etc..) to accommodate the AC
• Implement (static) "Procurement Shop" data structure and data (model, endpoint, etc) #725 - Procurement shop - @xlorepdarkhelm
• Create React Component to select a PS, (drop_down, with label) #770 - Procurement shop FE - @fpigeonjr @xlorepdarkhelm
• Refactor <Agreement Select /> to use api #818 - @tdonaworth @fpigeonjr
• Add budget lines from Agreement selection to <PreviewTable /> #819 - @fpigeonjr
• Add Project and Agreement Summary Box  #844 - @fpigeonjr
• Rounding of numbers in summary cards
• off by a digit in fee calculation
• NaN for 2024 dates (and beyond?)
  • 🤔can't duplicate in localdev

Definition of Done Checklist

- [ ] UI works as designed see #1008

• OESA: Code refactored for clarity
• Automated unit tests updated and passed
• Automated integration tests updated and passed
• Automated quality tests updated and passed
• Automated load tests updated and passed
• Automated a11y tests updated and passed
• Automated security tests updated and passed
• 90%+ Code coverage achieved
• PR(s) have been merged to main
• Build process updated
  - [ ] Documentation updated or added
• Feature flags/toggles created
• OESA: Dependency rules followed

Additional Context & Resources

• Some refactoring and changing of state management is tracked in DevEx: Refactor Create Budget Lines #982
• "Properly-formatted" can be determined as the story is being worked.
• Don't boil the ocean. Start basic and small, other aspects of this epic are in these stories:
  • Input validation, sanitization, enforcement of required fields, and handling of business rules for the budget line is in Validate Draft Contract Agreement / Budget Lines #675
    -Application logging of record creation and changes is in Logging of New/Modified Budget Lines #676
    -Approval workflow/process for adding budget lines is in Request Budget Line status change from planned to executing (initial action) #677
    -Being able to copy an existing BL values to a new one (or X number) is in Re-using existing Budget Lines to Create New Ones #678
    -Having a view of all changes to BLs aka audit log) with metadata is in Audit Report of changes to Budget Lines #679
    -Summarizing changes at a higher level than each BL is in Summary of high-level Budget Line Changes #680
• https://docs.google.com/document/d/1uAQmZm8DOJtLAFZHLk7oaDApAZnRJZp3do4d1FUG5a4/edit?pli=1#bookmark=id.a4c4eh83zldy
• Drawing

[kimschulke]

Scheduled interview with a member of the budget team for Thursday 2/23 at 1pm ET

[kimschulke]

Creating a workflow to outline what we learned from the Budget Team in terms of their current process

[kimschulke]

Planning to review with OPRE on Tuesday 3/7. We have a few questions to go over and once we confirm the content/information is accurate, we can further iterate on layout, if needed.

[kimschulke]

Design is ready for development! Let us know if you have any questions

https://www.figma.com/file/dsQFe6G2KjcTWNq7NNZujm/OPRE-OPS?node-id=144%3A5515&t=jdcahfZgoOxL88Xx-1

[jonnalley]

marked for review 5/5

[jonnalley]

A big batch of UI issues pertaining to a specific path of creating BLs is now in its own story, #1008