How messages are generated
Every night, the Wise system runs a background task that identifies and selects all items that require a customer message. These items are included in the Notification file and remain in the file until the reminder is printed or sent by the branch. The system checks the status of the items and immediately adds lines to the Notifications file. Hold requests remain in the file until they are printed or sent.
During the nightly creation of messages, hold requests, and invoices, the system also checks the status of items. Items that have been returned are removed from the Notifications file. The Notifications menu is only available to employees with proper authorization. In addition, branches can be included in what are known as print groups so only those branches are visible for the messages to be printed.
For more information regarding the message types available, see Notification formats and types.
Message workflow
Message jobs and reports can be viewed in the Wise configuration manager at systemWise > Dashboard > Dashboard. Jobs appear in the Job lines tab and reports can be viewed in the Reports tab.
For each message type, a job runs to select notifications to be sent. A separate job runs to send the selected messages to the appropriate recipients. The table below displays how messages are selected for a job, and information regarding the names of jobs and reports for messages:
| Notification class | Message selection is based on | Selection job name | Runs | Report name | Sending job |
|---|---|---|---|---|---|
| Alerts (A) | My account settings |
BLDAAN (Used for new items) ATTENT |
Once every 24 hours | Alerts (0000) | ATTVZM |
| Notifications (H) | Overdue process settings | HERVZM | Once every 24 hours |
hervzm_xxxx_seq_nr bericht_inlever_verzamel_2021xx-xx-xx Itiva_overdue |
Notifications (0000) |
| Return reminders (I) | Overdue process settings | HERVZM | Once every 24 hours |
hervzm_xxxx_seq_nr bericht_inlever_verzamel_2021xx-xx-xx Itiva_preoverdue |
Notifications (0000) |
| Public messages (P) | Customer request or action | PUBVZM | Constantly | Public messages (0000) | Public messages |
| Hold requests (R) |
BALRSV (Used for email) RSRVZM (Used for print messages) |
BALRSV - Once per hour RSRVZM - Once every 24 hours |
Holds (0000 email) Holds (rsrvzm mail) Itiva-holds |
Holds (0000 email) Holds (rsrvzm mail) |
|
| Fees (C) | Membership settings and Card configuration settings |
CONTRN OPENPOST |
On demand |
Open Period xxxx Invoicing (0000) |
CONTRN |
| Bills (N) | Overdue process and Overdue materials billing process |
HERVZM NOTAS NOTVZM unique_export |
Once every 24 hours |
nproc_xxxx_seq_nr invoicing procedure_date |
Notas (0000) UNIQUE export |
| Location messages (V) | Customer email sent to the email address defined in Branch settings | VSTVZM | On demand | Branch messages (0000) | Branch messages (0000) |
| Marketing (M) | Messages are generated from the Marketing workbench. | MRKTNG | Hourly | MRKTNG | MRKTNG |
| Newsletter (B) | Newsletter is sent to customers within the Wise client. |
NWSBRFA (For BSA and BKA message types.) NWSBRFM (For BSM and BKM message types) |
NWSBRFA - On demand NWSBRFM - Hourly |
bericht_inlever_verzamel_<date> |
NWSBRFA (For BSA and BKA message types.) NWSBRFM (For BSM and BKM message types) |
View sent messages
After messages have been sent, they can be viewed within the Wise staff client.
To view messages sent to one specific customer, navigate to the customer account and go to Customer > Customer correspondence.
To view all messages sent, navigate to Branch management > File management > Berichten. To view system-wide messages, select 0000. Branch-specific messages are in the corresponding folders.