Hi,
We are trying to work with a User's Repository to load secondary users, just like it is used in Rapido. The downside for our current customers is that they have to either wait for a full build to be completed (triggered by a scheduled task OR a user save notification), or manual force it.
Request
We would like to be able to have partial builds for Users, and/or have them triggered when a user's profile is saved/updated. That would keep the UX the same as it currently is for the customer, without having a big overhead generating a full build.
Is the Full Build slow?
Yes because we have customers with hundreds of thousands of records. It still takes a minute or so. With a partial build it would be instantaneous and we could also assign it to scheduled tasks and whatnot. The way it is currently, our customer has to do a few aditional (techie) steps.
(go to Settings > Repositories > Users > Users index > Build instances one at a time OR Settings > Integration > Scheduled tasks > Find repository task and run [although it builds more than just Users])
Acceptance Criteria
(These are the steps our customers end up doing while performing their tasks, hence the request to streamline it)
- Log in with a user that has secondary users
- Go to a Query Publisher page where Seconday Users are listed (you can use a Rapido site with impersonation to do this)
(our customers may have logged in and impersonated other users for the past 30 min, before they realize they need to add additional ones) - Go to the backend and assign a new user (or group) to users you can impersonate and click "Save"
- Go back to the frontend and hit refresh
- The new users should be available
Best Regards,
Nuno Aguiar