Hi.
I’d like to force a sequence which starts with the user signing up. While this action produces a row in the database, I’m not given the option to use the result in a subsequent action.
I want to be able to call the current user in subsequent actions, but I cannot be sure that it will be populated because I don’t have a way for force the action to wait for the user to be created.
After you sign the user up, you have to log the user in. Then, you can use the result of that step in subsequent workflow actions.
When a user signs up the user is being logged in, so current user is the new user in subsequent actions.
Sure, but how do I enforce the action to happen after the user signs up?
For example, I don’t have the ability to reference the result of step 2 in step 5.
I’m not given the option to reference the log-in (step 2) in a subsequent step (for example step 5).
You’d use “Current User,” the 2nd item in that dropdown list there.
My understanding is that the actions as they’re displayed, can happen in any order unless they reference a prior action. @emmanuel - is this true of login and signup?
No, actions run in order, and the current user is the newly created user after a sign up action.
Okay. It’s odd that that works for signup but not the other actions throughout the app.
Are you saying that Bubble guarantees that actions happen in order? I ask because that’s not been our experience. If this is something new you’ve pushed, then that’s awesome.
Actions happen in order, and if there is a result of previous actions you can use that. There is not change here. And current user is as explained above.
(Your special case was where actions were modifying data that wasn’t accessible as a result action)
I think Whitney’s saying there’s no way to reference the result of signing up a user.
We also know from the behavior of our app that actions start in sequence but don’t finish in sequence. In other words, they run in parallel and not in series.
So, if we can’t reference that action we can’t trust that action’s data is available to us in a later action. So, it’d be nice to be able to reference the user signing up. This would saving us from re-running searches and re-running API calls.
Not a big deal, of course, but it’d be a nice to have if it’s easy enough to add on your end.
As I explained above
The current user after a sign up action is the new user.
I understand. However, is the current user’s data guaranteed to be available in a subsequent step (without referencing the original action)?
The current user after a sign up action is the new user. When I write this I mean it’s guaranteed…
I think we’re talking past each other.
I’m not asking if the user ID is the same. I’m asking if the user’s, say, first name that get’s entered in the “sign user up” action is guaranteed to be available in a subsequent action ?
I’m not talking about a user ID. I’m talking about a user that is a database object, with fields, such as the name.
You can reference your “end user” as the “current user” the moment they sign in or sign up.
To accomplish what you’re looking to do, try this:
In your user data, create a field (yes/no type). Call it first-login. Set default to “yes”.
When a user logs in to your app, test to see if the user’s first-login value is “yes”. At the end of the workflow for first time subscribers, change and save the value of first-login to “no”.
Thanks Emmanuel.
Thanks all.
I tested and confirmed with 100 users that the current user is updated immediately upon signup and login.
