Review page is a read only page for viewing case content (include current assignments of the case), nothing can be updated.
Assignment page is a page display after one of assignment is open, where user can update something and submit.
Assume a requirement is, in review page, no button is displayed, in assignment page, a button need display for some action.
We used to check pyActionInfo.HarnessType (for current harness) to know current page is which of above mentioned two, as use different harness.
However, later we found this solution does not work if case is open by a URL where pyActionInfo.HarnessType is not set. It only works when case is open from a portal.
Want to know any one has similar architecture as above and any other way to know is current page an assignment page or review page. For info, before and after assignment open, case status remain same, so it’s not a way to distinguish this.
In addition to checking whether newAssignPage exists and contains a valid pxInsName, you can also verify whether pyWorkPage.pxAssignmentKey is populated. The pxAssignmentKey property is set only when a user actually opens an assignment—either through Open-Assignment or by clicking an assignment link—making it a reliable indicator that the current page is an assignment view rather than a review page.
Instead of building any custom logic, you could make use of pega OOTB when rule to find the harness type and put your business logic. For finding Review Harness → this is the when rule pzIsReview. Similar to this for each harness we are having OOTB when rules and you could make use of that.
This works fine, thanks, and we would like to use pzIsConfirmOrReview to include “Confirm” harness checking which is similar to Review, displayed after assignment submission.