Introduction
This page describes examples of typical booking scenarios, and the shape of the workflow that needs to be created automatically from each
Processing Order
Bookings are received from the Client into the system (e.g. via the Booking API endpoint)
Bookings need to be data-enriched as needed, to complete any vital missing information (based on who the Client is) e.g. consignor, consignee, responsible SEKO agent - this completes the Booking Model
SEKO operators see new Bookings on their dashboards, arranged in a priority order e.g. in collection / creation date ascending order
A SEKO operator selects a Booking and creates a Workflow from it
The system generates the Workflow using configured Templates that may be client-specific
Workflows from Booking Scenarios
At a Standard Task level, the system will create Workflows based on the scenario in the Booking, as per the following table, with the tasks in sequence as per the stated top-down order
...