PPR table displays no registrations and drafts disappear
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
This is from a request from Sharon (ITOPS-238097)
https://sbc-registries.atlassian.net/browse/ITOPS-238097
### Description:
Clients reported that their PPR table displays the message “no registrations to display” even though their account holds active registrations. They also reported that PPR does not save an initial registration draft or an amendment draft. The draft disappears after saving. Clients take screenshots of the draft and rebuild the registration from the beginning once approved.
This issues does not appear to affect staff
### Steps to Reproduce
- User logs in to the affected client account.
- User navigates to the PPR table.
- System displays “no registrations to display” even though registrations exist.
- User creates an initial or amendment draft.
- User attempts to save the draft.
- Draft disappears from the table.
### Impact
Users cannot review registrations through the table. Users lose draft work. Users rebuild registrations from the beginning.
Notes from Sharon:
I created an amendment draft in my account. The draft saved and behaved as expected. I deleted the draft after testing. Staff tables display entries as expected. The issue appears to affect specific client accounts. BCOL Help Desk informed the client that other accounts reported similar behavior. Multiple users linked to the same client account experience the same issue.
Developer Note:
One of the drafts for this client included an invalid character in a secured party business name: "\udb80 BANK OF MONTREAL". Data corrected, OPs ticket updated.
Fix: add character checking to all fields of submitted draft data.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by tracing the PPR table registration query and the initial and amendment draft submission path for client accounts, using the invalid character in the secured party business name as the reproduction case. Done means submitted draft data with invalid characters is handled safely, drafts remain visible after saving, and affected client registrations appear in the table.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100