Worklink is opening the case without displaying the themes defined in the Portal linked to the operator.
Welcome to the community!
Would need some more details on your configuration
- How are you constructing the work link?
- Are you blending with traditional UI?
- What is the configuration of the user / access group
- do you have multiple access groups for the same app in one user?
This article might be useful, if you have not read it: Deep linking and Semantic URL
Hi Marc,
Please find the details below.
- By using pega OOTB. (pega_rules_utilities.pzEncryptURLActionString(tools, “Global”, “pyActivity=Work-.Open&Action=Review&HarnessPurpose=Review&InsHandle=”+ insHandle+“&FocusKey=”+tools.getParamValue(“FocusKey”));
- No, it is mainly for constellation.
- Operator is connected to only one access group and role.
In Constellation, you can refer the below article by @JayachandraSiddipeta along with the one in the above reply to understand how to form the work link. The link you are using is for traditional UI.
As @VVNagaSaiN says, that approach is Traditoinal UI.
- Deep linking and Semantic URL covers the URL formation and comments have the examples of implementations
- Example: pxRequestor.pxReqContextURI + “/” + pxRequestor.pxReqServletNameReal + "// " + … etc
- Some traditional examples
- Building a Case link in Email body for Constellation application - Novitates from @JayachandraSiddipeta
- Theme-Cosmos: Open work object in Full portal on Copy sharable Link by ManikandanK17103558 (I used this alot of both Theme-Cosmos and Constellation)
The last time i did this (2023 for Infinity '23) I used:
pxRequestor.pxReqContextURI+“/”+pxRequestor.pxReqServletNameReal+“/”+Param.CaseName+“/”+Param.ID
OR
D_SystemConfiguration.pyPublicLinkURL+“PRAuth”+“/”+Application.pyProductAlias+“/”+Param.CaseName+“/”+Param.ID
