Notification center
The notification center keeps users informed about relevant events within fulfillmenttools. It allows configuring email notifications for specific events on the network and facility level.
The following events are available:
PICK_JOB_CREATED: A pick job was created in a facility.UPCOMING_TIME_TRIGGERED_REROUTE: An order will soon be re-routed.ROUTING_PLAN_NOT_ROUTABLE: An order couldn't be assigned to a facility.ROUTING_PLAN_WAITING: A routing plan is waiting for external events to be routed.
Notification channels
The notification center supports two types of notification channels:
Email channel
When this channel type is configured, one or more email addresses can be added as recipients. Whenever a triggering event occurs, all configured recipients receive an email notification containing relevant event details.
Client channel
When this channel type is configured, a database entry is created each time a triggering event occurs. External clients can retrieve and display these entries via the notification API.
Configuration
Notifications can be configured either on the network or facility level:
Network-level configuration: Notifications are received globally for all applicable facilities.
Facility-level configuration: Notifications are received only for specific facilities (for example, for orders routed to that facility).
A channel must be defined to set up a notification.
A channel defines the source (event) and, if applicable, the target (receiver) of the notification.
We recommend defining separate channels for different receiver groups or facilities.
Quotas may be imposed on this in the future
fulfillmenttools reserves the right to impose a quota per customer on this feature in the future.
Create a notification configuration
To create a notification on the network level, you'll need to use the Global notificaiton endpoints.
To create a notification on the facility level, you'll need to use the Facility notification endpoints.
Examples
Network notification for routing plan not routable
In the below example, we'll create a notification that sends an email to a user if a routing plan is not routable across the entire network.
Facility notification for pick job creation
In the below example, we'll create a notification that sends a notification to Backoffice when a pick job is created.
You can then use the id to
Network notification for time-triggered reroute
In the below example, we'll create a notification to inform a supervisor before a time-triggered reroute due to inactivity occurs.
Firstly, we have to define when the notification is triggered using the reroute times configuration.
We're defining that a task is rerouted after 120 minutes of inactivity. A notification is sent 30 minutes before the reroute occurs, which is after 90 minutes of inactivity.
You can then use the id to
Next, we can configure the notification channel.
You can then use the id to
A scheduled CRON_JOB in the tenant is responsible for triggering the dispatch of emails. Depending on the configured interval of this job, a delay may occur between the actual event time and when the email is sent.
Last updated