Skip to main content Skip to complementary content


The Governance Dashboard Publisher sheet presents task reload history as well as the latest reload status. The statuses indicated are Completed, Failed, Running and Warning. Error messages are not included.

Task summary

The Task Summary sheet lists all Publisher task reloads for a given period. Tasks are listed by name with the documents they load, the node on which they load, the start and finish times, and the status.

The Doc Tasks Started by Hour graph plots the number of tasks started each of the last 24 hours by the node on which they were run. The timeline starting point zero (0) is 24 hours back from current time, represented by 24 hour.

Red circles indicate warnings or errors exist for one or more of the tasks started at that time. Click on circles to view details in the All Publisher Task Reloads table.

The Complete Document Task List table provides details, including the associated document name, of all Publisher tasks. Documents can be any document type handled by Publisher (QVW, QVD, log, XML).

The task settings listed include whether the task is enabled, its trigger, distribution, and error handling.

The Allow Plugin field indicates whether or not the task can be run by the Internet Explorer plugin.

The Allow ZFC field indicates whether or not the task can be run by the AJAX client  (Zero Footprint Client).

The AccessPoint App Data Aging table shows apps that are being used with old data. Set the value for Apps accessed in last at less-than or equal-to the days since last update. Apps with gaps between days accessed and last updated are candidates for more frequent update. The actual number of days since the last update appears in the right-most column.

Reload heatmap

The Reload Heatmap sheet shows reloads across hours and days or hours and weekdays. The amount of history available in the reload map is determined by the Heatmap and Concurrency Days setting on Configuration sheet.

The setting for day or weekday enables you to view the hourly data for each day by date or by day of the week. Viewing the heatmap by weekday allows you to see the busy periods as measured across weeks and months. This is designed to help with capacity planning.

The Reload Heatmap sheet also includes a table of All Publisher Task Reloads. The table lists all tasks, the document they reload, the node on which they run, start and finish times, duration and status.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!