Criteria for the Work Cache

The Work Cache comprises of a number of work items that get mirrored to the Work Cache.

Criteria for inclusion

Work items from the following list are included in the Work Cache.

• Tasks (List type 171), Project Tasks (BrightWork), older task lists (List types 150 and 107)
• Project Goals
• Project Risks
• Project Issues
• Project Change Requests

• Project Requests

• Custom list (BrightWork)
• Custom List (SharePoint)
  The contents of these two custom lists will ONLY be added IF the column bwAddItemToWorkCache exists in the list and that column returns True.

By default only open items are included in the Work Cache. Items are considered open when:

• The items Completed Flag is 'No'.
  or
• If a Task's % Complete value is not 100%.

However other criteria can be applied to include items in the Work Cache if:

• A list column called bwAddItemToWorkCache exists in the list

• Its calculated value is Yes

Criteria for exclusion

Some items may not meet the criteria to appear in the Work Cache. The following items are not mirrored to the Work Cache.

By default closed items are excluded from the Work Cache. Items are considered closed when:

• If Completed Flag is 'Yes'.
  or
• If a Task's % Complete value is 100%.

All items in a site are considered closed when:

• If the checkbox for Exclude from Reports is ticked in the Project Statement.
  or
• If the Project Status is Completed the items from the site will not appear in the open Work Cache.

However other criteria can be applied to exclude items from the Work Cache when:

• A list column called bwAddItemToWorkCache exists in the list

• Its calculated value is No

Troubleshooting

If you notice any anomalies in the Work Cache data it may be because of one of the following reasons, which can be fixed with a refresh:

• Renaming a site: if a project site is renamed the change is not reflected in the Work Cache until a refresh, covering the project site, is run.

• New permissions: if a new user or group is added directly to a site or Site Collection, the change is not reflected in the Work Cache until a refresh is done.

• Server issues: if a SharePoint server experiences issues and the SharePoint administrator deems it necessary to restart services on the server, e.g. IIS, then some changes may get lost during the restart and a refresh will be needed to fix the content of the work cache.

If these do not resolve the anomaly and you want to take a closer look at how the refresh works, your SharePoint administrator can enable Work Cache logging.

There's two levels of Work Cache logging: medium and verbose.

Medium logging returns data on the site collection, sites and lists.

Verbose logging returns data on all of the above and all items in the site collection.