Semantic URL in Constellation

Pega-as-a-Service
1

Our use case is to open the case link from email .

In Tradition UI , we used to use correspondence fragment rule to achieve this .In Correspondence fragment , we used to form the base url as https:///prweb/PRAuth/app//CustomAuthService( User’s needs to be authenticated via a custom SAML auth service and they used to have access to multiple applications and they want to directly log in to our specific app( with out switching app) )

As per our understanding , in Constellation , to open any case as a link -we need to use semantic URL like https:///prweb/app/// and once it is formed correctly , we need to embed it in Correspondence rule .

Considering , we are using custom auth , can some one pls clarify , what will be the sematic URL syntax in this scenario ? We are trying with this but it is everytime opening the Portal instead of the Case . :-

https:///prweb/PRAuth/app//CustomAuthService//

We are in Pega Infinity '24.1.2

2

@AVIKCEMK

Try to use URL mapping rule instead to achieve this functionality.

3

@AVIKCEMK this should work for constellation ( verified in 23.1.3)

https:///prweb/PRAuth/app///case-type-description/

Case type should have the description in small cases and spaces replaced by “-”

4

Hi @AVIKCEMK , thank you for the question.

Let me ping @Kamil Janeczek who is leading the UX EC, perhaps he would be able to offer guidance.

5

@AVIKCEMK URL format looks correct

6

@Kamil Janeczek @aniki @Kuresh_Surury

We have formed the URL like below and we are able to open the case directly from email ( Correspondence)

https:///prweb/PRAuth/app//// .

Say the user is having multiple Access group for the application and each access group is having their own portal. With the current semantic URL approach , We are observing , what ever the 1st access group , present in the Operator id, for the respective application -->PEGA is taking that and opening the case . Can some one please guide , how to pass the Portal Name as well in this context , so that this discrepancy will not happen ?

7

@AVIKCEMKthis is exactly the behaviour. It will take first access group for given application and will use the default portal for this AG.

I have seen clients implementing custom logic to set/change AG on the fly, this is possible.

8

@Kamil Janeczek Thanks for the prompt response .

Can you or someone pls guide is there any provision to pass the Access group /Portal name like a query string Parameter to this synatx like https:///prweb/PRAuth/app//// ? portal =X

or is there any other way present ?