Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Work item reports

Updated on May 11, 2022

Standard reports on work items are based on the exposed columns in the schema of the pc_work table for work items, and the pc_history_work table for history instances for work items.

Work items are stored in the pc_work table, and work item history instances are stored in the pc_history_work table. This relationship is defined by the two database table instances Work- and History-Work-.

When you create new work types and corresponding work history classes using the Application Accelerator, the system maps the new work classes appropriately into these two tables.

However, when you create a concrete class by using the Class form, the default mapping is to the pr_other table (and the pr_history table, for history). These mappings are not appropriate for work items and may cause SQL errors or JavaScript failures. You can remedy this by adding the two appropriate database table instances.

Two standard database views are linked to the Data-Assignment-Summary and Data-Assignment-WBSummary classes. These support custom worklist and assignment reporting. Update these view definitions if you use these views and you change or copy the pc_work table.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us