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
{{ message }}
This repository has been archived by the owner on Apr 12, 2019. It is now read-only.
Currently it seems that there are some very specific fields in our classes which are used between the adapter and the node.
The following fields should be discussed:
internalReference
internalPersonId
techID (currently removed since not in use)
The goal would be to define a clean API which does not have anything VE-specific (like e.g. PAKT).
Would it be sufficient to identify a match by the following three fields:
retirementFundUID
OASI Number
commencement / termination date
Or should we provide a single field that identifies on record.
How ever this should be discussed in the team.
The text was updated successfully, but these errors were encountered:
Currently it seems that there are some very specific fields in our classes which are used between the adapter and the node.
The following fields should be discussed:
The goal would be to define a clean API which does not have anything VE-specific (like e.g. PAKT).
Would it be sufficient to identify a match by the following three fields:
Or should we provide a single field that identifies on record.
How ever this should be discussed in the team.
The text was updated successfully, but these errors were encountered: