There are a few scenarios where we would want to schedule a workflow to run periodically.
One in particular - Where the users have an LTU, they cannot do much with a workflow due to the limitations on the permission set. The workaround i have to use is to “schedule the BPA”, so that it runs as a different user with high privileges. As long as we have the LTU concept, we are going to have to do this to solve customer requirements.
So, it would be good to have a proper approach to support scheduling a BPA. Currently we have to mess around setting up a dummy migration job so that we can use the job scheduler there. This is confusing to customers, looks pretty unprofessional and introduces a lot of baggage such as the need to import/export migration jobs.
It would be quite straightforward to enable scheduling a BPA via Scheduled tasks. The method bpa_sys.register_async_bpa would work fine, but is not considered “schedulable” because the package ends in _sys, not _api. So it is not possible to add it as a Database Task.
