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
Since we have expectedParticipantData now, we should consider save and access participant information (email, name, etc.,) here, and use Keycloak only for identity management, this will
Save a lot of resources and time when processing recruitment/participants related operations.
Save participant information in our database, instead of Keycloak database
Have user information page back on Portal
Requires changes to participants page, as information will not be stored in keycload anymore (or extra work)
Maybe also consider change Participants page --> Recruitment page, and remove deployed participants, since they should be managed in deployments
The process time is expected to reduce significantly for Participants and Deployments page on Portal, and we can keep rely on frontend to do pagination.
The pagination for getParticipant and getDeployment should support filter/search
We should do pagination on database level
The text was updated successfully, but these errors were encountered: