Client - Self-serve Request New Party Code

As a client user of the PPR, I want to request a new party code, so that I can manage my registrations independently.

Context:
The current Secured Party Code (SPC) Management system in the Personal Property Registry (PPR) needs enhancements to better support both Registries Staff and client users who manage registrations. Improving this system will streamline processes, enhance data integrity, and empower users with more self-service capabilities.

## Client Use Case

As a **client user of the PPR**, I want a self-service option to:
- Request new party codes without staff intervention.
- Update addresses on existing party codes.
- Transfer existing registrations from one party code to another, assigning a new code to both prior and subsequent registrations.

Providing self-service tools will reduce manual workload for staff and give clients more flexibility and control over their registrations.

---

### BA Notes
The current procedure for managing SPC's is manual. Clients either call in, send mails or use the form 3.
- For a new code request, The user provides name and address information for a new code assigned by the registrar.
- For a code change to new code, the user provides updated name and address information for an existing SP code. A new code is assigned by the registrar.
- For SP code change with global change, the user provides updated name and address information for an existing SP code. Code number remains the same. Global change is applied for all occurrences of the SP code in existing registrations.
- For a global change without SP code change, the change is applied for all occurrences of the SP code(s) in existing registrations.
- The request is then forwarded to IT Operations through a staff‑initiated ticket so the required changes can be completed.
- he BC OnLine account number is quoted in the request for billing purposes where necessary.
- A change of name or address attracts a $100 fee

#### Data Inputs and Data Types
**New Request**
| Field | Data Input | Data Type| Comments |
|-----------|------------------|--------------------|--------------------|
| Name | Name the code would be issued to | String | Can be an individual or a business |
| Address | Address, City, Province, Postal code | String | |

**Edit/Amend existing SPC**
| Field | Data Input | Data Type| Comments |
|-----------|------------------|--------------------|--------------------|
| Name | Previous name, | String | Name currently on file |
| Address | Previous Address, City, Province, Postal code | String | Address currently on file |
| Name | New name, | String | New name to change to |
| Address | New Address, City, Province, Postal code | String | New address to change to |

**Authorization**
| Field | Data Input | Data Type| Comments |
|-----------|------------------|--------------------|--------------------|
| Name | Applicant's Name | String | |
| Date | Date of signature | Date | |

The issue names no files, tests, or entry points. Start by reviewing the stated client use cases and data-input tables, then locate the PPR client interface and supporting request workflow; done means the requested new-code, amendment, transfer, and authorization flows are defined and implemented with their stated inputs.

Written by the indexing model from the issue text.