Payroll processes via the queue
You perform tasks, such as processing and approving the salaries, using the queue.
When using the queue, certain tasks are placed into the queue automatically and are performed in the background. After you have started a task it will go to the queue, and you can then continue to work normally in Profit. You do not have to wait until the task has been completed.
For AFAS Online the queue has already been configured, with the exception of the authorisation of the functions to consult and monitor the queue. For a local installation you decide for yourself whether you want to use the queue or not.
Once a task has been started in the queue, you cannot stop or delete it. You can only stop a task if it has the In queue to be carried out or Initialising of batch process status.
Video
Description
The Profit Batch Service can perform tasks from different environments. From the moment that the Profit Batch Service is active, this means the following:
- Queue per environment
Profit maintains a queue for every environment in which the relevant functionality has been activated. If a user starts a task (such as the salary processing), Profit places it in the queue. The user does not have to wait until the task is completed, but can immediately continue to work. A user can start multiple tasks one after the other.
Which tasks you can add to the queue is predefined. Once the queue functionality has been activated, Profit automatically queues such a task when it is started by the user. The user cannot specify whether a specific task must be placed in the queue or not.
We recommend that the tasks processing/approval of the salary processing and checking/preparing of the wage declaration are not placed directly after each other in the queue. If you do this, they can interfere with each other leading to the generation of error messages.
- The Profit Batch Service regularly checks if new tasks are waiting.
The Profit Batch Service checks the selected environments one by one. If a new task is found, the Profit Batch Service checks if it can be performed. The Profit Batch Service can perform up to three tasks (so-called threads) simultaneously.
Processing of large employers in groups
Profit can shorten the processing of employers with large numbers of employees by performing the salary processing in groups. This is only relevant in environments that include employers with large numbers of employees. In this situation, Profit can divide the employees of each employer into groups and process these groups in parallel. This is an (optional) expansion of the default queue functionality
If you use this functionality, the Profit Batch Service will split up the processing task into processing groups when it is the turn of the processing task.
Preparation
Procedure
- Queue tasks
If the relevant conditions are met, Profit automatically queues tasks. If it is not possible to queue a task, Profit will report that. Certain conditions do also apply to performing tasks in the queue. You can display the status of a task in the queue.
- Manage the queue
You can view the queue of the current environment. Profit indicates which tasks have been performed and whether they were performed successfully.
- Notifications about your own tasks
Once a task has been completed, Profit displays a notification. This is a text balloon that is shown in the bottom-right corner of your screen. If you see this notification, you can simply continue working.
- Print documents and retrieve files using the queue
For some tasks, the queue prepares files. For example, pay slips are not printed immediately but instead saved to a print file.
- Temporarily stop using the queue
The rest of this description only applies if you have a local Profit installation.
For a local installation you can disable the queue in an environment. This enables you to perform new tasks from the workstation and these tasks no longer end up in the queue. Tasks that are still in the queue but have not yet been performed, can also be performed from the workstation.