Good afternoon,
I am working on creating a notification system that sends out an email to alert a specific user in the Quality department whenever any Part/Resource is within 3 days of expiring based off the PartLot.ExpireDt data. I am struggling to write a sensible condition in the BPM Workflow Designer that will trigger the email alert.
Any suggestions?
I would create a BAQ report that filters by the expiration date. Then set up a schedule to run that report once a day and email it to that user.
Hi Lena!
The objective here would be to only have the user notified when the expiration date is in 3 days. The user is familiar on how to use the Lot Expiration Date dashboard that i set up, so she is able to view the dashboard and manually identify them. But sometimes there is only 1 or 2 materials a month that will expire, so a daily report would be redundant. She is requesting a method to where this is automated and an email is sent to her only when something is going to expire in 3 days or less.
I’ve tried writing a few conditions, but have not been able to generate a notification email yet 
I’ve tied BPMs like this to data directives on SysTask. You can tie the BPM to fire when a specific scheduled task completes (or errors). I’ve used this for tasks like closing jobs shipped that day or ending activity on labor records.
I would agree with Lena in this case though. A BAQ report that runs daily would is your best option. If you keep the report simple it should only return results if a lot is within your 3 day window. If there are no results, no email would be sent. No need for the BPM.
The problem is how does the system knows “hey, I need to check the expiration of PartLot”?
If there is already a manual task related to PartLot then you could attach the BPM to trigger at some point during this task. Otherwise this is why a recurring process is needed, in this case the recommended report sounds good.
Good morning all!
I think all of your replies have given me a better understanding of why a BAQ report would be the best option. Thank you @YGT, @zwilli526, and @Jonathan for sharing your insight!