We have Build a Landing Page , which is getting sourced from a Report defination , that returns work item. In App studio, in the respective View , we have enable the respective setting so , that , it can be opened as Link to a new tab ( User will be accessing multiple case via this) .
When , we click -Open in New Tab —>Its not opening the case and it is opening the entire portal . When , we tried to copy the Link , we can see the case id is not present .
We have attached the configuration details .
Can some one pls check and tell us , whether we are missing any thing here ?
@AVIKCEMK what class is the datapage in? Open object will only work for the class the datapage is in, if youre datapage is joining data from other classes it won’t work.
The more likely cause of the issue is the pyRoutingTable, if the case is new then it might not have the semantic URL for the case to open this. I have seen this commonly. Try regenerating the table.
@MarcCheong My Dpage is sourcing from a RD which brings data only from Work table ( No Join present in that RD ) . We have an other use case -where we have implemented, worklink from Correspondence using Semantic URL configuration as recommended. That Worklink part is working Fine. However , we see the issue with this “Open in Tab”.
@AVIKCEMKit is possible your worklink is working fine as you are explicit in the semantic URL, where as Open in Tab would be using the pyRoutingTable to generate the worklink.
Though having re-read you description, now I am thinking it is your datapage itself. I’d want to check to see if your OOTB generated datapage for the case, under “use existing lists” works for this configuration. That would suggest its something in the datapage (join, response datatransform, not marked as “queryable”).
We have raised an SR for this issue. After investigation by the Pega Support team it seems to an issue with the amount o pyRoutingTable in the application stack.
In our application stack we have several versions of the pyRoutingTable but when making the changes the pyRoutingTable was saved in the dev ruleset of our development application.
To solve this issue we have to make sure the the pyRoutingTable is is updated on the lowest application in the stack that needs the pyRoutingTable.
In our case , we were using a Custom Dpage to source the content of the table and Dpage was getting sourced via a DT . Inside DT , we were calling RD ( From work group table) to get the details .
When we update the Dpage source , to RD directly ( in place of DT ) -->Then it started working .
In our case as well , pyRoutingTable rule is present in many ruleset versions of a particular ruleset .
So as per the conclusion -it seems , the Dpage sourcing method creates an Issue .
