-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retrieve Partner-information from HC and StUF-BG when user is logged in with DigiD #3351
Comments
joeribekker
added
the
triage
Issue needs to be validated. Remove this label if the issue considered valid.
label
Aug 10, 2023
Requires merging of client stuff. |
joeribekker
removed
the
triage
Issue needs to be validated. Remove this label if the issue considered valid.
label
Oct 2, 2023
Refinement: Partner needs to be added to this component. |
SilviaAmAm
added a commit
that referenced
this issue
Oct 4, 2023
SilviaAmAm
added a commit
that referenced
this issue
Oct 4, 2023
SilviaAmAm
added a commit
that referenced
this issue
Oct 4, 2023
SilviaAmAm
added a commit
that referenced
this issue
Oct 5, 2023
SilviaAmAm
added a commit
that referenced
this issue
Oct 5, 2023
SilviaAmAm
added a commit
that referenced
this issue
Oct 5, 2023
SilviaAmAm
added a commit
that referenced
this issue
Oct 5, 2023
SilviaAmAm
added a commit
that referenced
this issue
Oct 6, 2023
SilviaAmAm
added a commit
that referenced
this issue
Oct 6, 2023
SilviaAmAm
added a commit
that referenced
this issue
Oct 6, 2023
SilviaAmAm
added a commit
that referenced
this issue
Oct 6, 2023
SilviaAmAm
added a commit
that referenced
this issue
Oct 6, 2023
SilviaAmAm
added a commit
that referenced
this issue
Oct 6, 2023
SilviaAmAm
added a commit
that referenced
this issue
Oct 6, 2023
…nfo-in-family [#3351] Partner info in family component
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reference: Utr 76
At minimum we need firstname, last name, bsn, birthdate... but maybe we need to retrieve what is needed by prefill? We also can combine this with co-sign to determine who needs to co-sign?
Needs some refinement.
The text was updated successfully, but these errors were encountered: