Firm Completing Party Updates
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Approach:
- Adjust completing party components in Entities flows so if no address exists in the account the client can input an address. When an address is prepopulated from a client account, the client can still edit that address.
- No changes to existing staff component
- No changes to rules for completing party name
Rules:
**Question: If a completing party address is pre-populated from the account can that be edited?**
If completing party is pre-populated from the account the client users can still edit the address. No rule changes should be made to the staff component.
**Question: Can a logged on user change the completing party name?** Verified that a BCeID user can currently change the completing party name in PROD. Verified component had no errors / ability to move to next step but cannot file in PROD.
**Question: Do we need to keep completing party in the JSON when it is not part of the filing / schema. This was done and added in to cases where the filing does not collect completing party.** If the completing party is not part of the filing schema / not in the UI it should not be added into the JSON. Work is needed to clean this up.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.