I am currently working on a Video Conferencing booking application. I need help with triggering an alert on the guest page of meeting whenever the host triggers the alert/popup with the click of a button. This button is only accessible in the host page and whenever the host clicks the button an alert appears on the guest page of the meeting. Is this even possible?
Assuming you know the admin and guest etc: You should use the DB for alerts and that would be as easy as pie. Just hide a group that would show only when there is an alert targeting guest users. See the example below:
I have this alert structure:
And the group on top just displays when there is an alert targeting the role set on the page:
The rest is classic Bubble stuff.
You can check the editor here if it helps: Tests for Forum 14 | Bubble Editor
Not quite what I’m looking for. But I appreciate your help. Anyone else want to chime in.
“…whenever the host clicks the button an alert appears on the guest (audience) page of the meeting.”
No, I don’t know who the host and guest is. It’s a standard video conferencing app. Anyone can signup.
If it is a video conferencing app, each video conference session should have a host (whoever created it) and guests (whoever joined). And you should keep track of these sessions in any case. Otherwise, it is very uncontrolled environment.
Once you know who is host and guest, example above works.
Did this workflow you created work?
Ummm, but this is being viewed on the same page isn’t it, just in a different window? But anyways, I’m trying to get this functionality (check video below). For some reason, I am unable to get the alert popping up on the guest page every time the host clicks the button. It only pops up once on the guest even though I already set the “Do when condition” to “every time”. Btw, the text would be retrieved from the database. The Database already preloaded will all the texts.
Also, there will be option sets preloaded with the texts. So if anyone can show how this could be done using option sets that would be awesome.
Please check the editor link I put. It is the same page but the alerts are filtered based on the role value.
It works the way you want but only once, right? Looking at your original workflow screenshots, it looks like the host clicks a button and this sets a value in the database. Then in the guests’ browsers, a different workflow acts when the value is not empty to show the alert. What might be missing is a way to turn the value blank again afterward, so the process can be repeated when the host clicks the button again. If there’s only one guest, it’s simple: At the end of the guest’s workflow, after the alert is shown, another action could delete that value. But if there are many guests, the guest with the fastest connection and computer could delete the value before all of the guests have had the workflow triggered. So maybe set a timer so that 3 (?) seconds after the host clicks the button, the host’s workflow deletes the value. It might also be necessary to use a state to tell the button to become unclickable during those three seconds, then change the state back to make the button clickable afterward. Does this make sense? Do I understand the situation?
As for option sets, they’re generally available everywhere all the time. However, option sets are programmed in by the developer at development time and become fixed when the app is deployed. This means that the host can’t change the messages stored in the option sets. If that’s what you want, great. But if not, you can’t use option sets for this purpose. You have to use a data type.
What you’re asking though, is if you have all the texts in the option set, how do we program the workflow to show a different text each time the button is pressed, right? And do you want them sequential (first message first time, second message second time, etc.) or random?
1 Like
I already did. While it’s close to what I want, this isn’t exactly what I want.
I think you are exactly right Andy about a way to turn the value blank again after. I don’t know how to make it blank again without the deleting the entire question from the database. (Questions is it’s own Thing)
Maybe create a separate data type in the database for alerts and copy the alert value there. That way you can delete the value there without affecting the original. But if you have a data type with all conferences, it could just be an extra field there instead of being a separate data type.
Okay, I will give that a try.
What I actually had in mind was a Current Question field. You copy the question there when the host clicks the button, then delete it three (?) seconds later. The next time the host clicks the button, the next question is copied there.
I already have a Current Question field (check 2nd image). So i’m guessing I would have to use a backend workflow to delete it 3 seconds later?
Sorry for not seeing that. Yes, that’s more or less what I was thinking. But since, according to the manual, delays and timer events are handled client-side (such as “Add a pause before next action” or “Schedule a custom event”) (Client-side and server-side processing | Bubble Docs), it could be handled as client-side workflow(s). Remember, I also suggested making the host’s button unclickable during those three seconds, then making it clickable afterward. With the help of states, you can temporarily rename the button while it’s unclickable so the host knows not to keep clicking the button repeatedly (x.com). So, I would either include all this in the host’s client-side workflow or a custom event. But whether it’s a frontend or backend workflow, it contains both frontend and backend actions, as the manual shows.
Thanks Andy, I got it to work. I used a Backend workflow to clear the Current Question after 3 seconds. Rather than delete the Current Question, I just left the Current Question field blank instead. That’s the host page.
The audience page must have a “Do When Condition” that is “Only when Meeting Current Question is not empty”. Make sure you set it to “Every time”.
Host Page
Audience Page
1 Like
This topic was automatically closed after 70 days. New replies are no longer allowed.