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

Exception: Cannot resolve source property for pyWorkPage

SA-15565

Summary



There is a reference property linked from a property in a pagelist. The value for this reference property is set in a work object using Property-Ref method and closed. On reopening the work object, an exception is generated in the log.

This was working in PRPC 6.3 SP1 and the issue started after upgrading to Pega 7.1.8.



Error Messages

Cannot resolve source property for pyWorkPage.scheduleForOperator1StartingDate. Link info: Is reference = true; Levels to parent = 1; Relative target = .scheduleForOperator(1).startingDate; Total number of redirections = 1; Rule trace list: []; Reason: source property not found on common top-level page


Steps to Reproduce



1. Create a work object, and set a reference property linked from a property in a pagelist by using Property-Ref method. Then close the work object.
2. Reopen the work object.


Root Cause



A defect in Pegasystems’ code or rules. Prop-Ref does not save value on Work-item Submit.
When you submit a work object which uses property-ref method, reference information is corrupted. When a confirm harness displays after submitting, reference information is on a clipboard. However, reference information in a blob on a database is empty. Reference properties, which are exposed, have values on a database.
When generating a blob from properties used property-ref method, it is somehow corrupted.

Resolution



Apply HFix-24035.

 

Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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