I need to perform some tasks at a certain time everyday, and can’t find a way to schedule them.
In V8, I created a BAQ and scheduled a reoccurring BAQ export. Then I made a BPM that triggered when the BAQExport ran.
But E10 does not have BPMs for BAQExport
Is there any other process I can schedule - that I can configure to do nothing - and has a BPM capturable event?
Doesn’t matter what the process is, as long as I can ensure it fires every time - and can determine that it was the scheduled process that fired it too (which I can do with a condition block in the BPM design).
My end goal is to generate emails based on the days shipments.
Create an email for each shipment, showing shipped items, previous shipments for related orders, and open items.
Attach a copy of the PDF of the packer to the above email.
Run every day at a specified time.
I have number 1 working just fine as a Data Directive triggered on the ShipHead.ShipStatus changing to SHIPPED. But this causes the the email to be sent the instant the Packer is marked shipped. We want to batch these to go out at the end of the day.
Not being able to attach the PDF of the packer to the original email isn’t a deal breaker.
BPMs run when something happens/changes. DMT changes things. So if you trigger DMT with something like powershell, DMT will change stuff. You can make a BPM to look for the changes that you are making with DMT which will trigger the BPM.
Sorry, we are on 8.03 now and use the BAQ Export to trigger the BPM but we are looking to go live on E10 this summer and I am painstakingly trying to re-write all customisations we need to take over as we are going for a fresh install!
how about creating a data directive on SysTask table update, condition it on any scheduled task, and add your custom code to do what you need, which could be invoking an update method and updating records or/and triggering BPM’s.
This is expensive since Data Directives would run (just to check) every single time any task runs. There should be no reason to run this except when it needs to be run. Hence the schedule BAQ and or Scheduled code.
@tmat - We had the same issue. In V8 we had a BAQ Eport was running on a schedule. It didn’t actually export anything, we just used it to trigger a BPM. When we moved to E10 there was no BAQ Export to shcedule and piggy back off of.
I can’t seem to get the alert to work using a directive on the Ubaq’s GetList method. I have managed to get it to work using a Data Directive on the SysTaskLog table. This is something that will be scheduled to run out of office hours but is there any reason I shouldn’t assign the directive here? My boss is still looking into the process scheduler.
We have a couple of things that we trigger from the SysTask tables and it’s all fine, so on the face of it there’s no reason why you shouldn’t do the same.
But what everybody will warn you is that it can put serious load on your system if you aren’t extremely careful. If you put a data directive on the SysTaskLog table the directive itself will run every single time any task of any type is run, and that can have a massive performance impact.
To avoid the whole risk associated with messing with SysTask, BAQ export call variability by version, or buying the third party software, I’ve started using a user code type called AUTOPROC, then placing a directive on the user code update that runs your custom code if the user code modified is your certain code (e.g. “AutoShipEmail”) and LongDesc is updated (to the current datetime or something). Then, you can call this update through whatever you want: REST, DMT, PowerShell DMT, and the code can be static and the meat and potatoes can be stored in the BPM. This does have the external dependency of the trigger and execution of the simple user code update; I am doing this through PowerShell DMT on a windows task schedule, which is easy enough and requires no SQL permissions.