Step 1 of Procurement Tracker - Acquisition Planning

tdonaworth commented 1 year ago

User Story

As a COR, I want to update and advance a contract through the acquisition planning step of an executing contract so that I can track deliverables optimally.

Preconditions

One or more budget lines of a contract is already in executing status

Acceptance Criteria

[ ] The user can see a visual understanding of the overall procurement process and the current progress in it
[ ] The user can affirm that they have sent the pre-solicitation package to the procurement shop. This is a required step to complete this step.
[ ] The user can select the OPS user who sent this. The list of possible users would be any users associated with the contract including team lead(s) and division director(s).
[ ] The user can select the date it was done. The date must either be the current or a prior date.
[ ] The user can optionally provide any notes limited to 750 characters
[ ] The user can reset all unsaved form input
[ ] The user can commit their input which will advance the contract to to the next milestone.
[ ] If any error is encountered in persisting the change(s), that error should be presented to the user
[ ] The relevant entries should be recorded in the event/history table(s) and be able to be properly rendered properly in the history of changes to the agreement

Tasks

UX

[x] Review design options with team
[x] Review design with stakeholders
[x] Refine steps with stakeholders
[x] Provide designs to developers
[ ] Iterate based on ChangeRequest edits and processes

Dev

~- [ ] #1948 - @tdonaworth~

[ ] Create initial procurement based endpoints for creating the workflow
[ ] Create additional WorkflowStepTypes as needed - initially need an Attestation step and Workflow step

Test Plan

User can navigate to the procurement tracker tab within the agreement's details
User can view an overview of procurement steps with an indication they are at Step 1. User can open/close all accordions but input fields of all other steps other than the current ones should be disabled excluding target completion dates.
All user input fields but the affirmation checkbox would be disabled and once the checkbox is checked, the other user input fields would become enabled.
User can open the dropdown the list of persons that has sent the pre-solicitation and select one (and only one)
User can enter a date that is today's date as well as a date prior to the current date (separate tests)
Notes field should be trimmed.
Save Changes button should allow a user to click but Vest should throw errors until validation is complete.
Cancel: Cancel link is clicked, confirmation dialog is presented and if confirmed, the uncommitted form input is removed
Once Save Changes is clicked with all required entries filled, a user can see their progress at the next uncompleted step of the Procurement Tracker, even if they've navigated away and come back
Once Save Changes is clicked with all required entries filled, the viewable history event should record the user who completed step 1, the selected user who sent the out of band email as part of the acquisition planning step and the selected date.
Once Save Changes is clicked with all required entries filled, step 1 shouldn't be editable any further