Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Workflow structures and tasks

The aim of workflow is to separate the business logic of bookings into separate and distinct tasks which interact with each other. This will be brought in once the bookings are in a stable position for the business to work with.

Real Life Scenario

Linear (Non-Task Based)

Bookings are all in a sequential process where recording of bookings, transport, warehouse are all recorded together in one screen, with no flexibility.

Task Based

Tasks are added to a Bookings workflow and configured as required. This keeps the tasks independent whilst allowing interactions between them to be automatically monitored and processed. So for example, if there was no warehouse involved the booking could contain a final mile facility with a pre-alert being sent from the source of goods rather than from the warehouse.

  • No labels