I have created a flow at our college that sends out a series of weekly emails to students on a remote learning course. The flow starts with a simple MS Form that collects a student's name and email address, along with a date field as start date for the emails. It's a 12 week course but due to the 30 day flow limit I can only send the first 4. Is there trigger that i can use to send another 4 emails, and then trigger the final 4 emails using the same date from the original MS Form?
We currently use the free version. If we were to subscribe, is there a workflow/trigger with the paid version that we could use?
Thank you,
Nigel.
Related
I'm working on e-learning academy system like udemy every instructor have wallets and wallets have three type of balance
1- total balance and it present total earning
2- available balance and it present earning that he can make payout or transfer it to his bank account
3- hold balance and it present earning that is not available for specific time then will be available to transfer it.
Project build by Laravel my issue how can I hold money for 14 days and after that make this money available without any action from my side I need logical idea to make it
can use cron job, or is anyone have this experience before ?
Let me break down the issue as per my understanding so we make sure I'm answering the correct question;
You have a system that has a wallet feature.
This wallet needs to hold some money and make the money unavailable to be paid out (hold status)
Then after 14 days, the money gets paid automatically without any interaction.
If I'm correct, then keep reading the answer below. If i'm not, correct me with a comment and I'll update my answer accordingly.
Answer:
We will create a new table. Let's call it pending_payments. It'll have the following information: user_id, payment_amount, pay_at
That table will hold information about pending payments and to which user they should be paid as well as the amount and the date it should be paid at.
We'll have a Laravel job that can be automated ( read this for more information: https://laravel.com/docs/9.x/scheduling) which will do the following:
a. Run daily on a specific time. Let's say at 13:00 daily for ease.
b. It'll check the pending_payments table for payments that should be paid today.
c. Pay them ( which means run whatever function/task you have to run in order to process the payment).
d. On a successful payment, remove the row from pending_payments table. And on a failure payment, log the error and insert the row again with a later date to be retried again later.
That's it.
I am migrating sql server database into REDCap. I am new to REDCap and I am still investigating the features of REDCap. I am building a survey form that will collect all the data into REDCap. Once the data is there in the REDCap, I want to send emails based on the date in the future. For example, if there are fields in the instrument as below
Email
Expiry Date
test#gmail.com
12/12/2021
I want to send automated email to that email address(test#gmail.com) on that date date (12/12/2021). Basically, it has to look at the data and send out reminders to the email address on the expiry date.
I looked at alerts and notifications. I can write the conditional logic to send the reminder upon data entry. But, here in my case, the data is already stored.
I looked at the scheduling module. Scheduling module is generating events on the calendar but not sending emails automatically.
Is there a way I can achieve this?
Which version of REDCap is your institution on? Since version 9.9.1 you can have an alert send either before or after a date field in your project. So the alert can be configured to be triggered by data import, and the time to send would be, say, 5 days before the [expiry_date].
Here is the changelog entry:
Improvement: A new send-time option has been added when setting up Automated Survey Invitations and Alerts & Notifications. When defining
when the ASI/Alert should be sent, the option “Send after a lapse of
time” has a new setting added so that, if desired, the user may set
the time lapse relative to the value of a date or datetime field in
the project. In previous versions, the time lapse setting could only
be set relative to the time in which the ASI/Alert was triggered. That
is still an option, but now users may also opt to send the ASI/Alert a
certain amount of time either before or after the date/time of a
specific field. This new setting will allow users to have greater
control with regard to setting when ASIs/Alerts will be sent without
getting too complicated in their setup, such as having to use complex
logic (with datediff, etc.).
As the changelog says, another method is to use datediff logic in the trigger, which you will need to use if you are not on v9.9.1 or later (you should also encourage your institution to upgrade since there are important security patches since then). When an alert has a datediff function in its logic, REDCap will check it every four hours (unless the frequency has been changed by your administrators). This means you can send the alert 5 days before the expiry date with this logic:
(existing logic) and datediff("today", [expiry_date], "d", true) = -5
The true parameter here returns the signed value, so that if the first date is later than the second, it will return a negative value. false returns an absolute number.
This will be true on the exact day when [expiry_date] is 5 days in the future.
i am using laravel 5.2
i want to prepare an email to be sent after 50 days when the user click on a button then go to controller
i found "later" method but i did not work, its sends the email immediately.
also i found "scheduler" but i could not understand how to work with it because its about every day , monthly, yearly,...
what i want is after specific date only
here i try to send email after 5 minutes but it send it immediately
Mail::later(300,'email.final_reminder',['datastd'=>$datastd],function($mail) use ($datastd){
$mail->to($datastd['email'],$datastd['sfname'],$datastd['smname'],$datastd['slname'])->from('everyone#gmail.com')->subject('Final Report');
});
1) Due to the long delay i would recommend an database entry with an timestamp to store the information
2) And than you can set up a queue https://laravel.com/docs/5.2/queues which checks every day, minute etc. for the timestamp being older than 50 days (carbon subdays and now methode), than it can send the email and delete the record
i have a glitch in my magento 1.7. When 2017 come my customers start receive 2 order emails when place order(1 is correct but 2 is one year old). Maybe need to clean email queue ? if so, how ?
It seems like you are creating some scripts for the sales order. While an order is completed then the script is also synced with last order and it affects the order email system.
I have a subscription which happens on four specific dates on during the year according to a custom cycle . I want to get people to subscribe but get billed together on the same day every 2 months. If I set it to 2 month interval everyone gets charged separately according to the day they subscribe . Can a fixed payment date be set with ARB Recurring billing ?
What you need to do is charge the user using the AIM API and pro rate their first payment up to the first scheduled payment date. Then the ARB subscription will take over. That's all there is to it.