PPR - Block duplicate secured parties from submitting
Goal: Prevent users from entering the same secured party twice.
Rules: A duplicate secured party must have the same name (organization or individual) and full address.
Feedback from Dye and Durham, and Teranet is that they see no need to have duplicate Secured Party codes on a PPR registration.
@mstanton1 - can we get a bug ticket to investigate the potential issue of Secure Parties not displaying in the UI? I chatted with @cameron-eyds and we should probably try and address that if we can.
@mstanton1 also this ticket is ready to groom
@mstanton1 actually we might have a bug ticket already - let me see if I can find it
Policy feedback has identified the only instance where we can block adding a secured party twice is when there is a full match to both the legal name and address.
@mstanton1 moving the story to Done as all the tickets were closed, thanks!