Skip to main content


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

Updating related item counts

Updated on July 27, 2021

Pega Agile Studio uses the PPM_RELATEDITEMCOUNTS. table to store a count of the attachments, tags, dependencies, related updates, and notes for each Pega Agile Studio work object. When updating from PMF 6.3.1, you must manually set the initial counts for pre-existing work items using the stored procedure RefactorCounts to process and display related item counts correctly.

Pega Agile Studio Update Guide

The procedure RefactorCounts is available for all supported databases and is located in the PostUpdate folder of the release media. To use it, database administrators should compile it and use the database administration program of their choice to execute it on the database used by Pega Agile Studio.

To verify, for any known existing work object with attachments, tags, or related updates, run the query, replacing <work item ID> with the actual work object ID:

SELECT ATTACHMENTSCOUNT, TAGSCOUNT, RELATEDUPDATESCOUNT FROM PPM_ RELATEDITEMCOUNTS where WORKITEMID = '<work item ID>';

The result shows the actual number of attachments, tags, and related updates present on the work object. The bug shown below has two attachments, 1 tag, and 0 related updates.

    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.

    Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us