This process would be a common process for your users. This allows users to submit long-running tasks to the server, allowing them to continue using AX while the server processes the task. This is often underused, leaving users to watch an unresponsive screen while they wait for complex routines to finish (for example, a set of delivery notes to be printed).
Most users will be able to submit jobs as batch tasks. This example submits a Master plan schedule to be run as a batch task, so we will require appropriate privileges. The process is similar for most tasks that utilize the batch framework.
We proceed as follows: