I am attempting to create a workflow that uses a s...
# suiteflow
j
I am attempting to create a workflow that uses a saved search to follow up with customers that have past due invoices. I can successfully set this workflow up without an approval queue, however I'm having some issues adding in this additional approval logic. Specifically, I want the saved search to generate a list of invoices. Before an email is sent out though, it should go to the Controller where they can approve or reject (decide) if an email gets sent. If they approve, an email is sent to the customer for payment of the invoice. Has anyone done this?
m
You could do this in 2 ways: 1. Create a workflow with 1 state and add the Send Email action to it to send your email with the Subject, Body, Message and attachement you want. Then create a saved Mass Update that initiates this workflow. The criteria of your mass update would be the same criteria of your saved search. Then the Controller could go to this Saved Mass Update whenever they want and select the checkbox next to whatever Invoices they want to send reminders to customers for 2. Have have your saved search be inline edit enalbed and add a custom checkbox to your invoice called "Send Reminder Email". The controller can use the inline edit feature of the saved search to mark the checkbox for each Invoice they want sent out. Then setup a scheduled WF where the criteria is Send Reminder Email = T that runs each night. So each night any invoice the controller marked would be sent out. Put 3 actions in your WF Send Email Set Field Value: Send Reminder Email = F Set Field Value: Last Email Sent = today
This way it will uncheck the box after it is sent and record the date/time it was sent. so when the controller reviews it again the next day they can see it was sent recently so don't send it again
j
Thank you, @MGBC - really appreciate your insight and help. I will look into these approaches, maybe # 2 sounds like how I would like to proceed. Do you think the approval mechanism could be layered into the workflow kind of like how its being done here for Estimate record types in this example? I was trying to follow this sample and somehow tailor it to my specific use case for invoice follow up initially, but ran into issues, making me question if this is compatible with a past due invoice email workflow? https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N2801832.html#Designing-the-Estimate-Approval-Routing-Workflow
m
Yes you could build it out like this
#2 would be easy to adapt into this workflow
j
Ok, great - thank you 🙏
Also @MGBC - do you think it would be possible to use a different template for the email to the customer depending on which number attempt for collection it is? I was thinking, perhaps a new field could be created on the invoice record that serves as a variable that tracks how many emails have been sent to the customer, and would be persisted. At the end of each flow, that field variable gets incremented, and the workflow would determine based off the value of this variable which template it will be using this time through the workflow. Is that how you would recommend solving this?
m
You would need to add multiple send email actions into your workflow
Each with the condition using your number of emails sent field
This article explains how to do something similar
j
Amazing - thank you once again 🙂
m
👍