You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As sharing member of BPDM,
I want to be able to update the LegalAddress for an existing BPNL, and SiteMainAddress for an existing BPNS,
so that information that is already present in the BPDM Pool can be updated.
Acceptance Criteria
BPDM Pool is able to update the LegalAddress for a given BPNL
BPDM Pool is able to update the SiteMainAddress for a given BPNS
Clear definition of which updates are allowed and how the BPDM Pool should behave
Invalid update requests are rejected with an appropriate and understandable error message
Additional Information
Follow-up ticket to address the out-of-scope content for #1121
Resolving conflicts between information shared by different parties
Changes that would move a BPNA between two distinct BPNLs
Changes that would affect which BPNA is considered the SiteMainAddress for BPNS
Changes that would affect which BPNA is considered the LegalAddress for a BPNL
Open questions (this is not an exhaustive enumeration!):
How should the Pool react in case a second LegalAddress or SiteMainAddresss is provided for the same BPNL or BPNA?
How should the Pool react if a BPNA is provided together with a BPNL that is distinct from their currently assigned BPNL?
Cases differ depending if the chosen BPNA is a LegalAddress or SiteMainAddress
How should the Pool react if a BPNA is provided together with a BPNS that is distinct from their currently assigned BPNS?
Cases differ depending if the chosen BPNA is a LegalAddress or SiteMainAddress
The text was updated successfully, but these errors were encountered:
Description
As sharing member of BPDM,
I want to be able to update the LegalAddress for an existing BPNL, and SiteMainAddress for an existing BPNS,
so that information that is already present in the BPDM Pool can be updated.
Acceptance Criteria
Additional Information
Follow-up ticket to address the out-of-scope content for #1121
Open questions (this is not an exhaustive enumeration!):
The text was updated successfully, but these errors were encountered: