PPR UI - Secured Party Amendment issue
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
**Describe the bug in the current situation:**
When a new Business secured party is added to the Amendment, then editing the business name of the newly added secured party and choosing the existing Secured Party from the similar modal displays the badge as 'Amended' instead of 'Added'
**Link bug to the User Story:**
**Impact of this bug:**
Medium
**Chance of Occurring (high/medium/low/very low):**
Only occurs if the user edits the business name of the newly added secured party and chooses the existing Secured Party from the similar modal
**Pre Conditions:**
Complete a PPR Security Agreement registration.
**Steps to Reproduce:**
- Select the PPR Security Agreement registration from the table to start the Amendment
- Navigate to the Secured party section
- Add a new business-secured party without a party code (Eg: THE BANK OF NOVA SCOTIA PROPERTIES INC.), select the business name from the dropdown list and complete all the required fields and click on the Done button (Added badge is displayed as expected)
- Edit the secured party and change the business name manually to 'Bank of Nova Scotia' without using the results from the dropdown.
- Click on the Done button, and the similar secured party modal is populated
- Select the secured party from the 'Use an existing Secured Party' list
- The Badge changes from 'Added' to 'Amended' and unable to undo the change
- Clicking on the Amend button of the existing secured parties disables the user to add a new secured party manually or by using the party code.
**Expected behavior:**
When the user edits the newly added secured party, the badge should display as 'Added'.
**Screenshots/ Visual Reference/ Source:**

Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.