This topic describes a typical workflow of events and tasks.

Events arrive from multiple sources (A) as XML or TXT files in a series of hot-folders on a Back4 server (B), where the Back4 service runs and polls all the hot folders, each with a separate Back4 queue. The service extracts the metadata from the processed content, generates records in database on the database server (C) and populates them with the content. That makes the content available to users through the IIS server(s) (D). The content appears as events.

Also correspondents or in-house staff can create events.

A wire scroller (1) reviews the events, and agrees with section heads which ones are to be covered. Section heads create tasks from events, and assign them to users.

There could exist also the "shift" tasks, e.g. "page designer XY is on shift tomorrow night", "photoreporter AB is on shift Monday morning" etc.

Users review their tasks and then process then accordingly.

Events can also be published on the Web server.

The items involved on the Back4 server:

•Back4 hot-folders

•Back4 queues

•Data source templates with workflows

•Logging of activities

•Images conversion post-processing

The items involved on the Database server:

•Storage

•Searches

•Purging of old wire events

The items involved on the Web server:

•Web export with workflows through publishing destinations

•Web templates

•Web comments