Corporate Disclosure Statement: E-Filing Flow Changes

[cholly75]

As a Petitioner or Practitioner, so that I can e-file the appropriate form, I need the e-filing flow to reflect changes to the Court documentation rules.

With the approval of the upcoming rules package by the Court, the Ownership Disclosure Statement (ODS) is being renamed/replaced as the Corporate Disclosure Statement. We need to update all appropriate areas in DAWSON to reflect this change.

This story will address the E-filing flow for petitioners and practitioners.

We anticipate these changes will need to be live in mid-March 2023.

Pre-Conditions

9827

Acceptance Criteria

• On the landing page for Petitioner/Practitioner, p.1 - the verbiage is updated to replace" Ownership" with "Corporate"
• On the landing page for Petitioner/Practitioner, p.1 - the hyperlink to the ODS is replaced with a hyperlink to the new CDS form
• On the before filing a petition page, in the "If you're filing jointly with a spouse, for someone else or for a business..." section, the verbiage is updated to replace "Ownership" with "Corporate"
• On the before filing a petition page, in the "If you're filing jointly with a spouse, for someone else or for a business..." section, the hyperlink to the ODS is replaced with a hyperlink to the new CDS form
• In the "Create A Case" flow, Step 3 - when "A business" is selected, the verbiage is updated to replace "Ownership" with "Corporate"
• In the "Create A Case" flow, Step 3 - when "A business" is selected, the hyperlink to the ODS is replaced with a hyperlink to the new CDS form
• In the "Create A Case" flow, Step 5 - the verbiage is updated to replace "Ownership" with "Corporate" if displayed

Notes

• Assumption is that "File a Document" flow - dropdown menu for selecting document to file requires update to event code (story #9827)

• Landing page for Petitioner/Practitioner:

• Before filing a petition page (menu expanded):

• Create a Case, Step 3:

• Create a Case, Step 5:

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, JSDocs 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
• [ ] 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
• [ ] 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.

[ttlenard]

Test Cases

1) Petitioner with no Cases logs in; Option number 3 verbiage is updated to "Corporate", hyperlink opens the updated document.

• Log in as a Petitioner, making sure that they do not have any cases.
• Review the landing page

Expected Results:

• [x] NEW FUNCTIONALITY - number 3 on the UI states "Corporate Disclosure Statement (CDS)"
• [x] NEW FUNCTIONALITY - The Hyperlink states "Download Corporate Disclosure Statement (T.C. Form 6)
• [ ] NEW FUNCTIONALITY - The new document is available for download when clicking the hyperlink.

2) Petitioner expands the menu on the before-filing-a-petition page, verbiage is updated to "Corporate", hyperlink opens the updated document.

• Continuing from the previous test
• Click Start a case
• Expand the menu option for "If you're filing jointly with a spouse, for some else or for a business..."
• Review the section for "A Business"

Expected Results:

• [x] NEW FUNCTIONALITY - verbiage under "A Business" states "Corporate Disclosure Statement"
• [x] NEW FUNCTIONALITY - The Hyperlink states "Download Corporate Disclosure Statement (T.C. Form 6)
• [ ] NEW FUNCTIONALITY - The new document is available for download when clicking the hyperlink.

3) Petitioner selects a Business as the Party type; verbiage is updated to "Corporate", hyperlink opens the updated document.

• Continuing from the previous test
• Click Got It, Let's Start a Case
• Upload a STIN, click Continue to Step 2 of 5
• Upload a Petition, select yes or no, click continue to Step 3 of 5
• Select "A Business"
• Select any option for A Business and scroll down to view the section for uploading of the Corporate Disclosure Statement.

Expected Results:

• [x] NEW FUNCTIONALITY - verbiage in the header is updated to "Corporate Disclosure Statement"
• [x] NEW FUNCTIONALITY - verbiage in the information box is updated to "Corporate Disclosure Statement (CDS)"
• [x] NEW FUNCTIONALITY - verbiage in the Upload section states, "Upload your Corporate Disclosure Statement"
• [x] NEW FUNCTIONALITY - The Hyperlink states "Download Corporate Disclosure Statement (T.C. Form 6)
• [ ] NEW FUNCTIONALITY - The new document is available for download when clicking the hyperlink.

*Be sure that you repeat this test with all of the Business types to ensure that verbiage displays "Corporate", and hyperlink is correct.

4) Petitioner reviews the case; verbiage is updated to "Corporate Disclosure Statement"

• Continuing from the previous test
• Fill in the information for the business, upload a Corporate Disclosure statement form
• Click Continue to Step 4 of 5
• Select a case procedure
• Click Continue to Step 5 of 5
• Review the "Review your case" screen

Expected Results:

• [x] NEW FUNCTIONALITY - verbiage in the Petitioner Information card is updated to "Corporate Disclosure Statement"

5) Repeat all of the above test cases, but instead of a Petitioner, log in as a Practitioner.

• [x] Test case 3 passes with Practitioner user
• [x] Test case 4 passes with Practitioner user

[rachelschneiderman]

@ttlenard The test cases include The new document is available for download when clicking the hyperlink. (referring to Download Corporate Disclosure Statement (T.C. Form 6), we linked to what we expect that new form will be called, using the same URL structure for other links to USTC resources but we don't have the new form or permission to upload it to the website.

Just wanted to point that out since that is failing for me right now and unfortunately that's not something I can fix 😃

[cholly75]

Story go-live date confirmed 3/20

[rachelschneiderman]

Blocking until story can be deployed since we did not implement a feature flag. Test cases are passing.