Hello,
I want to set an option for new visitors to create a Demo Account for my web app to try its’ functionality, but I am unsure what’s the best practice to perform this. I have tried it and it gave poor performance (it took too much time to create).
A database structure looks like this, and a demo account should populate data within the same structure (sorry for my not-the-best sketching):
For each demo account, all these should be populated.
I have tried to make this step by step in API workflow, but as expected it gave poor performance (taking too long to create all these things):
What do you think is the best solution for this situation? Is it possible to create a pre-made data structure and just “paste it” when it creates a demo account? How would you approach it?
Any help would be very appreciated!
Best regards,
TP
@petrovic.teodor
Fastest way would be to have them pre-created and just assign the new demo account to them.
Another way would be to copy from a templated list. Not sure how much faster this could be.
Pre-creation or copying could likely work better and faster recursively.
2 Likes
Hey @cmarchan , thank you for your response.
If I may ask, how would you pre-create them and just assign the new demo account to them?
We do precreation. On a new account we just to update the account field
1 Like
Hey @gaimed , in short, how do you pre-create and assign it to the new account? You do not need to be very detailed, just sort out the steps shortly.
Each of our things has a account field. We use that to create privacy rules. On pre-creation they are added to a new account thing. When someone signs up, we give them one of the account things and they automaticly see it filled. Then on the background we precreate an other one. We always have 10 in the queue.
3 Likes
