When one participants approved flow continous, BUT i want to wait till all of 3 participants approves! How it could be done?
Related
Background
A workflow I have allows users to book meetings. The time/day of the meeting is stored in a table along with other details like the email address.
I send them an email reminder 30 minutes in advance.
Problem
In order to send them an email, a recurring event is set up once a week to go through the table and schedule the email to be sent on time - 30 minutes.
I've added the ability to reschedule the meeting. The problem that creates is that the emails are already scheduled, so users get the reminders at the original time, which is confusing.
What I want to do
I want to be able to send them the email at the rescheduled time, but there are technical limitations to the platform I use, which are:
I cannot set up cron/recurring more frequently than every day. This would probably be better than every week, but if someone rescheduled within the day, they would still get the wrong email.
I cannot remove scheduled events - so any recurring events-based workflow would still send the original email.
I know - this is pretty limiting, but am I even approaching this in the right way?
given your constraints, I'd probably go with 'resign'.
But in all seriousness, if you can't remove scheduled events (and I'm guessing you can't 'move' them because this is too advanced for your CTO to get their head around) then the only way I see it is to break the email send process into two steps - send scheduled event to PROXY in-front of your email sender, check if there is another event (i.e. can you add some 'cancelled/moved to data to the original one) and if so don't send it.
We are implementing an SMS tracking feature for our app using Twilio where we will send an SMS to our customer and once they reply with Yes/No
we will take action accordingly. For normal case, where each customer has one single phone number we can easily track the replies and
take action. But if the customer use the same phone number for multiple accounts and we send multiple SMS to the same customer
(eventually in a same phone number) we are not able to track which specific SMS they have replied for.
Lets take an example,
User Tom has three accounts with us. Each of the three accounts uses the same phone number P.
Twilio SMS are tracked by a combination of From/To pair.
Assuming, we are using one Twilio proxy number as sending number which is S.
Case 1: Tom has one booking canceled for a short notice period. An SMS has been sent from S->P. When a reply is received, we can easily track the reply and take the action.
Case 2: Tom has two or more bookings canceled due to a short notice period.
For each canceled booking, an SMS has been sent from S->P. When the user replies, we are unable to detect which booking to mark the reply for.
It is not possible to know which message a person has responded to in SMS. The only way to efficiently handle this is to send messages from different numbers. So, if a user signs up with the same phone number as another user then you need to assign a new Twilio number to them. Then you can tell which user you are contacting or receiving messages from by the number.
If you send out messages about bookings on the same account at the same time, then you need to be even more granular with the number access. Each notification should assign a number to use and then when a reply comes to that number it was about that notification. Then if you need to send a second message simultaneously, you attach a different Twilio number to it. And so on for more messages.
Is it possible to enter in two meetings and to record only one of them in microsoft teams? For example i'd like to record meeting 1 and to attend meeting 2 without recording audio of meeting 2.
Thank you in advance.
#Gennaro, You can't be part of two calls. If you dial second one, first one will go on hold - which you can resume after disconnecting second one.
Probably the option is to attend one and ask someone from meeting two to record. You will receive the recording or someone from meeting can share it with you.
I'm implementing meeting feature. Users come and pick slots and send to invitees. Once invitees pick the slots, the meeting gets confirmed Here I need to cancel the meeting if the slots expires. I'm using scheduler for every 2 min to perform this check. I think its bad to check frequently. Is there any other solution ?. Its a Rails 4.x application with Mysql database.
I want to implement websocket-based push notifications in a website. I already serached here on SO and on google, but my question is a bit different.
My use-case:
when userB replies to a comment posted by userA, userA will receive a push notification with a link to the article/comment (It is similar to SO)
My research:
on the web, people seem to agree that (in terms of scalability) it is better to limit the total amount of websocket channels. That leads to 1 channel per every user (= each channel will only contain 1 user). Why? Think about a group chat where 1 user could participate in 10 or more discussions --> that would mean 10 or more channels per user.
So, 1 channel per user is the best solution (until now).
I plan on using this bundle https://github.com/GeniusesOfSymfony/WebSocketBundle
In the docs, there is a page about How to Send a message to a specific user https://github.com/GeniusesOfSymfony/WebSocketBundle/blob/master/Resources/docs/SessionSetup.md . This method allows you to send a message ONLY to 1 user between all the users that are subscribed to the same channel. You do this by passing the user's username to the function.
This opens a new possiblity: creating only 1 big channel with all the logged in users subscribed to it INSTEAD of creating N channels where N is the number of authenticated users.
In other words, which is better: 1 channel with 1000 subscribers or 1000 channels with 1 subscriber?
I suggest you use a publish/subscribe framework and rely on the implementation of that framework to scale. You seem to be solving a problem that has been solved many times before. Search for ActiveMQ publish/subscribe, Kaazing JMS, Kaazing AMQP, Pusher, IBM MQTT/WS, etc.