Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

WO not found in current application



User is unable  to open the covered work object from search bar.

Error Messages

The work object was not found in the application. Check Id and try again.

Steps to Reproduce

Root cause unknown. Not able to reproduce the issue.

Root Cause

I have analyzed the tracer and could see the ErrorMessage: Work object WORK TS-1505 is not covered by -WORK WIP-168

As per the check made in Step 18 of Work-Open, @IndexInPropertyList(.pzInsKey, pyWorkCover.pxCoveredInsKeys) is set as -1 due to which the above error message is recorded. This triggers the NoWorkID Harness from being displayed in front end.

As observed. pxCoveredInsKeys value list does not exist in the pyWorkCover causing this problem to be there.

This is the root cause for the error to be thrown in front end. In order to re-mediate this, we will have to do a property-set on the pyWorkCover object with pyWorkCover.pxCoveredInsKeys="<CHILD CASE PZINSKEY>". This should make sure that the WhenCondition is skipped and the right harness opens up. Also, we will need to update the pxCoveredCount and pxCoveredCountOpen to “1”.


This issue is resolved through the following local change: Wrote an activity at customer end to update the values in the parent. It is a simple Property-Set activtiy for pxCoveredInsKeys and pxCoveredCount,pxCoveredCountOpen.


Published January 31, 2016 - Updated October 8, 2020

Was this useful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration 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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us