Prevent Practitioner Employer Change When Associated with Open Cases

[cholly75]

As an admissions clerk, so that I do not cause data problems with practitioner and case records, I need DAWSON to prevent me from modifying the Employer of a practitioner when they are still associated with open cases.

Currently DAWSON allows a court user to switch the Employer of a practitioner user between IRS, Private, and DOJ. When this occurs while the practitioner is still associated with one or more open cases, it leads to mis-filings and incorrect displays for the practitioner user in addition to preventing Docket clerks from successfully adding the practitioner to additional cases with the correct role.

We need to check to ensure that when making an update to the Employer value of a practitioner that they are not associated with any open cases.

Pre-Conditions

Acceptance Criteria

• When saving an update to a practitioner record on the Edit Practitioner Details screen, if the value for Employer is being changed and the practitioner is associated to one or more open cases (i.e., not in "Closed" or "Closed-Dismissed" status), prevent the entire update from completing.
• When the above condition occurs, inform the user that the update couldn't be completed because the practitioner is still associated with one or more open cases.

Notes

Private Zenhub Image

Tasks

Test Cases

Story Definition of Ready (updated on 12/23/22)

The following criteria must be met in order for the user story to be picked up by the Flexion development team. The user story must:

• [ ] Is framed in business/user need, the value has been addressed.
• [ ] Includes acceptance criteria
• [ ] Has been refined
• [ ] Pre conditions have been satisfied.

Process: Flexion developers and designers will test if the story meets acceptance criteria and test cases in Flexion dev and staging environments (“standard testing”). If additional acceptance criteria or testing scenarios are discovered while the story is in progress, a new story should be created, added to the backlog and prioritized by the product owner.

Definition of Done (Updated 5-19-22)

Product Owner

• [ ] Acceptance criteria have been met and validated on the Court's migration environment
• [ ] Add scenario to testing document, if applicable (https://docs.google.com/spreadsheets/d/1FUHKC_YrT-PosaWD5gRVmsDzI1HS_U-8CyMIb-qX9EA/edit?usp=sharing)

UX

• [ ] Business test scenarios have been refined to meet all acceptance criteria
• [ ] Usability has been validated
• [ ] Wiki has been updated (if applicable)
• [ ] Story has been tested on a mobile device (for external users only)

Engineering

• [ ] Automated test scripts have been written, including visual tests for newly added PDFs.
• [ ] Field level and page level validation errors (front-end and server-side) integrated and functioning.
• [ ] New screens have been added to pa11y scripts.
• [ ] All new functionality verified to work with keyboard and macOS voiceover https://www.apple.com/voiceover/info/guide/_1124.html.
• [ ] Swagger docs have been updated if API endpoints have been added or updated.
• [ ] UI should be touch optimized and responsive for external users.
• [ ] Interactors should validate entities before calling persistence methods.
• [ ] Features have been optimized where possible to reduce response times. For example, reducing api response times, parallelizing client network calls, optimizing database reads, etc.
• [ ] Types have been added to all added and updated functions.
• [ ] Code refactored for clarity and to remove any known technical debt.
• [ ] If new docket entries have been added as seed data to efcms-local.json, 3 local s3 files corresponding to that docketEntryId have been added to web-api/storage/fixtures/s3/noop-documents-local-us-east-1.
• [ ] Acceptance criteria for the story has been met.
• [ ] If there are special instructions in order to deploy into the next environment, add them as a comment in the story.
• [ ] If the work completed for the story requires a reindex without a migration, or any other special deploy steps, apply these changes to the following flexion branches:
  • [ ] experimental1
  • [ ] experimental2
  • [ ] experimental3
  • [ ] experimental4
  • [ ] experimental5

[swongCO]

UX Notes

From the practitioner details page, when the user clicks on the edit link, Dawson will check if there are any open cases associated with the practitioner. If there are, display as shown in the mockup:

• the other two options for Employer are disabled
• display an alert banner beneath the Employer section

[ttlenard]

Test Cases

1) Admissions Clerk attempts to update the employer information for a practitioner that has open cases; Receives an alert on the Edit Practitioner screen.

• Log in as an Admissions Clerk
• Click on the Advanced link in the upper right corner of the screen
• Click on Practitioner header
• Search for a Practitioner that has at least 1 open case (can click on the print case list to confirm)
• Click on the Edit link

Expected Results:

• [ ] NEW FUNCTIONALITY - Employer can't be changed alert is displayed under the employer section
• [ ] NEW FUNCTIONALITY - The radio buttons for the other employer types are greyed out and the employer cannot be changed.
• [ ] Clerk can update other contact info and save the record appropriately - app navigates back to the practitioner profile page and changes are saved.
• [ ] Clerk can cancel out of editing the practitioner record and the app navigates back to the practitioner profile page

2) Admissions Clerk attempts to update the employer information for a practitioner that has no open cases; Clerk can update employer successfully.

• Log in as an Admissions Clerk
• Click on the Advanced link in the upper right corner of the screen
• Click on the Practitioner header
• Search for a practitioner that has only closed cases, no open cases (can click on the print case list to confirm)
• Click on the edit link

Expected Results:

• All of the Employer radio buttons can be selected
• Clerk can change the employer and the save the record appropriately - app navigates back to the practitioner profile page, changes are saved.
• Clerk can cancel out of editing the practitioner record and the app navigates back to the practitioner profile page.

3) Admissions Clerk attempts to update the employer information for a practitioner that has no open or closed cases; Clerk can update employer successfully.

• Log in as an Admissions Clerk
• Click on the Advanced link in the upper right corner of the screen
• Click on the Practitioner header
• Search for a practitioner that has only closed cases, no open or closed cases (can click on the print case list to confirm)
• Click on the edit link

Expected Results:

• All of the Employer radio buttons can be selected
• Clerk can change the employer and the save the record appropriately - app navigates back to the practitioner profile page, changes are saved.
• Clerk can cancel out of editing the practitioner record and the app navigates back to the practitioner profile page.