Understanding the Flow
Steps:
User Logs In: The user accesses the Benchmark Web Application.
Navigates to Judicial Viewer: The user opens a specific case in the Judicial Viewer.
System Checks User Rights:
The system verifies if the user has the "View Petitions" right.
The system checks if the court type of the case allows petitions to be displayed.
Displays Petitions Section:
IIf the logged in user has the right to view petitions and the court type of the case is configured to display petitions, the petition section should be added to the summary screen.
The Petitions section can be either collapsed or expanded depending on user settings. Petitions are visible, default to collapsed or expanded, and can specify the order they see the petition section in the summary screen.
The user can customize the order in which the Petitions section appears in the summary screen.
Expected Fields in the Petitions Section:
Petition Type
Petition Date
Disposition
Disposition Date.
Save Settings: Users can customize the visibility, collapsed/expanded state, and order of the Petitions section in the Case Summary settings.
Test Cases
ORDER | SECTION | VISIBLE | COLLAPSED | |
|---|---|---|---|---|
12 | Petitions |  |  |  |
13 | Motions | | | |
To be added to below Case Summary :
Web view case detail should be the same as window case detail view with Petition tab like mentioned below.
Use Case 1: View Petitions
Primary Actor: Case Manager
Precondition: The user has the "View Petitions" right, and the court type allows petitions.
Trigger: The user navigates to the Judicial Viewer and opens a case.
Main Success Flow:
The system checks if the user has the "View Petitions" right.
The system checks if the court type is configured to show petitions.
The Petitions Section is displayed (either collapsed or expanded as per user settings).
The user views the petition details, including Petition Type, Petition Date, Disposition, Disposition Date, and any other relevant fields.
Alternate Flow:
If the user lacks the "View Petitions" right or the court type does not allow petitions, the Petitions Section will not be displayed.
Use Case 2: Edit Petitions
Primary Actor: Case Manager
Precondition: The user has update access to the case.
Trigger: The user navigates to the Petitions Section and clicks to edit the details.
Main Success Flow:
The user selects a petition from the section.
The user edits (sort, make it visible and set it as collapsed or keep it as expanded by default) the petition details, such as Petition Type, Disposition, or other relevant fields.
The system validates the input data.
The changes are saved and reflected in the Petitions Section.
Alternate Flow:
If the user does not have update access, the system will not allow any edits.
0 Comments