Task reminder configuration
Task reminders and escalation structure are initially configured during installation. If you want to configure the reminder escalation process, this is done by editing the reminder table D4_reminder_levels with a sql script to reflect your business requirements.
- Navigate to invoices/database/seeded_data/d4_reminder_levels_data.sql
- Edit the file by changing the appropriate values
See SQL code example below to see the exact position of the changeable values. Values are set by replacing d4 upload data for each reminder group within an organization. The reminder structure contains the following parameters:
If you do not have reminders set up, workflow tasks are automatically escalates when they have not been acted upon for 30 days. This is also the case if a task is at the last escalation level.
| Parameter | Sql command name | Description |
|---|---|---|
| Organization | ORG_ID | The reminder configuration is applied to this Organization ID |
| Reminder group | REMINDER_GROUP | The reminder configuration is applied to this group |
| Reminder level | REMINDER_LEVEL | This is the sequence level for reminder escalation |
| Days | DAYS | Number of days before a notification reminder is sent or escalated (7 days pr. Week) |
| Escalation | ESCALATION | Determines if this level is a reminder (N) or an escalation (Y) |
| Next user | NEXT_USER_SRC | Notification is escalated via hierarchy (H) or to the super user (S) |
Reminder groups
The reminder groups each include specific notification types. Reminders and escalations are sent out according to the specifications for the group notification type.
- ACC Accounting task notifications
- APP Approval task notification
- HLD Invoice hold release task notifications
- MPO Purchase order match notifications
- TWA Two Way Approver encompasses notifications for additional approval.
- SUP This group covers notifications for creating new suppliers.
- STD Standard tasks notifications - This group is used if another group is not specified
Sql code configuration example
Reminders and notification escalations are controlled by the database table D4_REMINDER_LEVELS that can be configured with SQL. The sequence is d4_db.upload_data('ORGANIZATION''REMINDER GROUP'',LEVEL, DAYS, ''ESCALATION'', ''NEXT USER''');
DECLARE BEGIN -- -- Upload table D4_REMINDER_LEVELS -- d4_db.upload_set_table(p_table_name => 'D4_REMINDER_LEVELS' ,p_schema_name =>'d4', p_delete_all_rows => TRUE,p_fail_on_missing_table =>
FALSE,p_unique_violation_ok=>TRUE,p_column_list => 'ORG_ID, REMINDER_GROUP, REMINDER_LEVEL, DAYS, ESCALATION, NEXT_USER_SRC' );
d4_db.upload_data('204,''ACC'',1, 1, ''N'', ''H''');
d4_db.upload_data('204,''ACC'',3, 2, ''Y'', ''H''');
d4_db.upload_data('204,''ACC'',5, 3, ''Y'', ''S''');
d4_db.upload_data('204,''APP'',1, 3, ''N'', ''H''');
d4_db.upload_data('204,''APP'',2, 1, ''Y'', ''H''');
d4_db.upload_data('204,''MPO'',1, 3, ''N'', ''H''');
d4_db.upload_data('204,''MPO'',2, 1, ''Y'', ''H''');
d4_db.upload_data('204,''STD'',1, 3, ''N'', ''H''');
d4_db.upload_data('204,''STD'',2, 2, ''Y'', ''H''');
d4_db.upload_data('204,''HLD'',1, 3, ''N'', ''H''');
d4_db.upload_data('204,''HLD'',2, 2, ''Y'', ''H''');
d4_db.upload_commit_data;
END;
/
Reminders for holds
Hold task notifications are escalated according to their own reminder group and the settings in the parameters controlling timeouts for hold notifications. Please refer to Hold Handling - Escalations for details.
Default Reminder Escalation
If you do not have reminders set up, workflow tasks are automatically escalates when they have not been acted upon for 30 days. This is also the case if a task is at the last escalation level.