Budget check module (printing)
If this module is present in the workflow, the account balance or the positive budget amount of the user account is checked. This means it decides whether or not a print job can be started (so there is no interruption of a print job). Depending on where the module is used, it has slightly different effects on the process.
It makes sense to use the module directly before the Send print job module, since all information about the print job is already known by this point.
Especially for direct printing, it is useful to inform the user if the budget check fails and the print job cannot be printed.

The module may occur only once in the workflow.

The placement of the module is not restricted. However, different effects result depending on at which points the module is used.

The module can be connected to all modules (this can result in nonsensical workflows).

Passed: This is the module that is to be carried out after the test has been passed.
Rejected: The module that is to be carried out after failing the test follows here.


The user is notified by e-mail if the budget check fails. For functions on the device, a message is also always shown on the device display.
Field | Description |
---|---|
Notification active | Specify whether or not to send an e-mail for this event. If this setting is not available, the notification cannot be deactivated. |
Type of notification | The e-mails can be sent in HTML or text format. In some places a message can also be sent as a push notification with IQ4docs Messenger, see also IQ4docs Messenger. The length of push notifications may be limited depending on the operating system. |
Recipient | Specify one or more e-mail addresses (separated by semicolons) to which the e-mail should be sent. It is also possible to use the e-mail address stored with the user (%EMAIL%), see also Variables. If this field is not displayed, the e-mail notification automatically uses the e-mail address of the user executing the workflow (this field is not available for push messages). When testing the connection, the e-mail address of the user currently logged in to WebAdmin is then used. |
Sender | Specify an e-mail address to be used as the sender of the e-mail. This is also the address that is used when the recipient of the e-mail clicks on Reply in the e-mail program. It is also possible to use the e-mail address stored with the user (%EMAIL%), see also Variables; this can be useful for some events, since the user who has encountered the problem can be contacted by e-mail. If this field is not displayed, the e-mail notification automatically uses the e-mail address of the user executing the workflow (this field is not available for push messages). When testing the connection, the e-mail address of the user currently logged in to WebAdmin is then used. |
Language | Select the language in which the e-mails should be sent. |
Subject | Specify the desired text to be used as the e-mail subject. |
Message | Enter the desired message here. Depending on the type of notification, use plain text or HTML code here. If this field is not displayed, the text will be supplied in full from the message template. |
Send Test Notification sends a test message with the selected settings. For the test, the user data of the user who is currently logged in to the WebAdmin are used (if you make changes to the data of this user, you must log out and log in again in order for this data to be loaded). It might not be possible to resolve variables at this point because the workflow was not actually executed. When testing, also note the settings for the recipient and sender.
Load Defaults fills the fields for Recipient, Sender, Language and Subject with default settings - any values that may have been entered are replaced.


Activities in connection with the billing of jobs, cost centers, postings, etc. are taken care of by the AccountingService. Its log file is Logs\AccountingService.log.