Term Generator - Rulesheet UI

[cholly75]

As a calendar clerk, so that I can adjust the output of the term generator when needed, I need to be able to see and customize some of the rules that it uses to generate the term.

The next step in moving the calendaring process wholly into DAWSON is the ability to customize the rules that the term generator uses when calculating a potential new term. By allowing the Court to adjust scheduling limits and the math governing the term generation, it lets us flex to any scheduling or caseload changes and react to any potential policy changes in our calendaring process.

To begin with, we would like to be able to adjust values used in the initial set of rules used by the term generator.

Pre-Conditions

Acceptance Criteria

• Rules used by the term generator are visible to the user in DAWSON when generating a term
• Numeric values used in each of the rules as seen below in screenshots can be adjusted to any whole number value, with a minimum value of zero for each field
• In rules where both a minimum and maximum value are required, the maximum value must always be equal to or greater than the minimum value
• No rule values may be empty prior to generating a term
• Rule value fields only accept numeric input

Notes

• Suggested maximum values:

• Sessions per week: # of weeks in term
• Sessions per location: # of weeks in term
• Cases per session (regardless of type): 200
• Less than X cases for location: 100

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.
• Verify that language for docket record for internal users and external users is identical.
• 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.
• READMEs, other appropriate docs, and swagger/APIs fully updated.
• UI should be touch optimized and responsive for external only (functions on supported mobile devices and optimized for screen sizes as required).
• Interactors should validate entities before calling persistence methods.
• 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
  • experimental6
  • develop
• Reviewed by UX on a deployed environment.
• Reviewed by PO on a deployed environment. Can be deployed to the Court's test environment if prod-like data is required. Otherwise deployed to any experimental environment.
• Deployed to the Court's staging environment.

[katiecissell]

UX Notes:

Figma File

Change the confirmation button to "Continue" on the create term modal.

Display a new page after the user hits Continue (same browser tab). Page header is the "Term name field (term dates) Term Builder Rules" This page will have an accordion (Expanded by default for now) and list hard coded rules for the user to adjust. Do not allow anything other than numbers in the adjustable fields. (No negative numbers , periods, or characters etc). We are trying to avoid having to validate the numbers so allow them to put whatever number they want.

When the user hits to create term, use the spinner if necessary and create the term the same way we do now. Display any warnings or success message alerts on this page.

[katiecissell]

UX Notes:

• Max limit on digits. Add validation for too large a number? How do we want to handle maximums?

[ttlenard]

Test Cases

1) Petitions Clerk clicks on the Create Term link; Modal now displays "Continue" button.

• Log in as a Petitions Clerk
• Click on the Trial Sessions page
• Click on the Create Term Link

Expected Results:

• NEW FUNCTIONALITY - The Confirm button has been renamed to "Continue"

2) Petitions Clerk Inputs Term info; clicks Continue, new page displays.

• Continuing from the previous test
• Click Continue

Expected Results:

• NEW FUNCTIONALITY - New Term Builder page loads (in same tab)
• NEW FUNCTIONALITY - Term header is "[Term Name] [Term Start Date - Term End Date] Term Builder Rules"
• NEW FUNCTIONALITY - The sub-header Sessions and case inventory is an accordion (opened by default for now).
• NEW FUNCTIONALITY - The list of hard coded rules is displayed with the default values populated in the fields (see mockup).

3) Petitions Clerk leaves the default numbers and clicks Create Term, Term is generated as per normal (excel spreadsheet downloads to computer), and any success/warning messages display on the Term Builder Rules page.

• Continuing from the previous test
• Click Create Term

Expected Results:

• The Suggested Term Excel Spreadsheet downloads to the user's device
• Any warnings/success messages display on the Term Builder Rules Page

4) Petitions Clerk edits the default values for the Term Builder Rules; Generated Spreadsheet reflects updates appropriately.

• Continuing from the previous test
• Edit the Maximum number of trial sessions per week
• Leave all the rest of the rules as the default
• Click Create Term

Expected Results:

• NEW FUNCTIONALITY - The Spreadsheet reflects this new maximum number appropriately
• NEW FUNCTIONALITY - If you typed in less than 6, there are less than 6 sessions per week
• NEW FUNCTIONALITY - If you typed in more than 6, there are more than 6 sessions per week

5) Petitions Clerk edits the default values for the Term Builder Rules; Generated Spreadsheet reflects updates appropriately.

• Continuing from the previous test
• Edit the Maximum number of trial sessions per location
• Leave all the rest of the rules as the default
• Click Create Term

Expected Results:

• NEW FUNCTIONALITY - The Spreadsheet reflects this new maximum number appropriately
• NEW FUNCTIONALITY - If you typed in less than 5, there are less than 6 sessions per location
• NEW FUNCTIONALITY - If you typed in more than 5, there are more than 6 sessions per location.

6) Petitions Clerk edits the default values for the Term Builder Rules; Generated Spreadsheet reflects updates appropriately.

• Continuing from the previous test
• Edit the Small Cases Minimum and Maximum number per trial session
• Leave all the rest of the rules as the default
• Click Create Term

Expected Results:

• NEW FUNCTIONALITY - The Spreadsheet reflects this new minimum/maximum number appropriately
• NEW FUNCTIONALITY - If you typed in less than 40, there can be less than 40 small cases per session.
• NEW FUNCTIONALITY - If you typed in more than 125, there can be more than 125 small cases per session.

7) Petitions Clerk edits the default values for the Term Builder Rules; Generated Spreadsheet reflects updates appropriately.

• Continuing from the previous test
• Edit the Regular Cases Minimum and Maximum number per trial session
• Leave all the rest of the rules as the default
• Click Create Term

Expected Results:

• NEW FUNCTIONALITY - The Spreadsheet reflects this new minimum/maximum number appropriately
• NEW FUNCTIONALITY - If you typed in less than 40, there can be less than 40 regular cases per session.
• NEW FUNCTIONALITY - If you typed in more than 100, there can be more than 125 regular cases per session.

8) Petitions Clerk edits the default values for the Term Builder Rules; Generated Spreadsheet reflects updates appropriately.

• Continuing from the previous test
• Edit the Hybrid Cases Minimum and Maximum number per trial session
• Leave all the rest of the rules as the default
• Click Create Term

Expected Results:

• NEW FUNCTIONALITY - The Spreadsheet reflects this new minimum/maximum number appropriately
• NEW FUNCTIONALITY - If you typed in less than 50, there can be less than 50 hybrid cases per session.
• NEW FUNCTIONALITY - If you typed in more than 100, there can be more than 100 hybrid cases per session.

9) Petitions Clerk edits the default values for the Term Builder Rules; Generated Spreadsheet reflects updates appropriately.

• Continuing from the previous test
• Edit the number for the field that states, "If there are less than..."
• Leave all the rest of the rules as the default
• Click Create Term

Expected Results:

• NEW FUNCTIONALITY - The Spreadsheet reflects this new number of cases appropriately
• NEW FUNCTIONALITY - If the number is larger than 50, and there are less than the number, no scheduled sessions will be suggested
• NEW FUNCTIONALITY - If the number is less than 50, and there are less than the number, no scheduled sessions will be suggested

10) Petitions Clerk edits the default values for the Term Builder Rules; Generated Spreadsheet reflects updates appropriately.

• Continuing from the previous test

• Edit many or all of the default fields

• Click Create Term

• NEW FUNCTIONALITY - The Spreadsheet reflects the new number of cases for each rule appropriately

11) Test all the data input fields above to ensure that only allowable values are allowed.

• No negative numbers are able to be input
• No text/special characters is able to be input
• No decimals are able to be input
• User cannot have a term created if there is an empty value - user receives validation error (Dev Discretion - If no validation - how will they know that they cannot have an empty value?)
• If the user inputs more for the minimum than the maximum, a validation error displays (Dev Discretion - If no validation - how will they know that the proper format for min/max?)
• Maximum values can be equal to the minimum
• User CAN input 0 as a valid number

12) Repeat all of the tests above with other users

• Clerk of the Court
• Case Services Supervisor

[ttlenard]

For the developer that picks up this story - Please see Test Case 11 re: questions about Validation on two of the fields. Thanks!