# Semantic URL in Constellation

**URL:** <https://forums.pega.com/t/semantic-url-in-constellation/9800>\
**Category:** Pega-as-a-Service\
**Created:** [August 2, 2025, 11:39am UTC](https://forums.pega.com/t/semantic-url-in-constellation/9800 "2025-08-02T11:39:28Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![AVIKCEMK](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@AVIKCEMK](https://forums.pega.com/u/AVIKCEMK)\
**Post date:** [August 2, 2025, 11:39am UTC](https://forums.pega.com/t/semantic-url-in-constellation/9800/1 "2025-08-02T11:39:28Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Nikunj\_Vihari](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/nikunj_vihari/32/16254_2.png) [@Nikunj\_Vihari](https://forums.pega.com/u/Nikunj_Vihari)\
**Post date:** [August 7, 2025, 1:09am UTC](https://forums.pega.com/t/semantic-url-in-constellation/9800/2 "2025-08-07T01:09:20Z")

</div>

@AVIKCEMK

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

---

<div class="post-metadata">

**Author:** ![Kuresh\_Surury](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/kuresh_surury/32/19426_2.png) [@Kuresh\_Surury](https://forums.pega.com/u/Kuresh_Surury)\
**Post date:** [August 11, 2025, 12:52am UTC](https://forums.pega.com/t/semantic-url-in-constellation/9800/3 "2025-08-11T00:52:33Z")

</div>

@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 “-”

---

<div class="post-metadata">

**Author:** ![aniki](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/aniki/32/23301_2.png) [@aniki](https://forums.pega.com/u/aniki)\
**Post date:** [August 19, 2025, 1:34pm UTC](https://forums.pega.com/t/semantic-url-in-constellation/9800/4 "2025-08-19T13:34:53Z")

</div>

Hi @AVIKCEMK , thank you for the question.

Let me ping @Kamil Janeczek who is leading the [UX EC](https://community.pega.com/expert-circle/user-experience), perhaps he would be able to offer guidance.

---

<div class="post-metadata">

**Author:** ![KamilJaneczek](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/kamiljaneczek/32/23339_2.png) [@KamilJaneczek](https://forums.pega.com/u/KamilJaneczek)\
**Post date:** [August 28, 2025, 6:55am UTC](https://forums.pega.com/t/semantic-url-in-constellation/9800/5 "2025-08-28T06:55:41Z")

</div>

@AVIKCEMK URL format looks correct

---

<div class="post-metadata">

**Author:** ![AVIKCEMK](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@AVIKCEMK](https://forums.pega.com/u/AVIKCEMK)\
**Post date:** [September 15, 2025, 1:37pm UTC](https://forums.pega.com/t/semantic-url-in-constellation/9800/6 "2025-09-15T13:37:58Z")

</div>

@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 ?

---

<div class="post-metadata">

**Author:** ![KamilJaneczek](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/kamiljaneczek/32/23339_2.png) [@KamilJaneczek](https://forums.pega.com/u/KamilJaneczek)\
**Post date:** [September 15, 2025, 2:42pm UTC](https://forums.pega.com/t/semantic-url-in-constellation/9800/7 "2025-09-15T14:42:55Z")

</div>

@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.

---

<div class="post-metadata">

**Author:** ![AVIKCEMK](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@AVIKCEMK](https://forums.pega.com/u/AVIKCEMK)\
**Post date:** [September 15, 2025, 3:51pm UTC](https://forums.pega.com/t/semantic-url-in-constellation/9800/8 "2025-09-15T15:51:37Z")

</div>

@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 ?

---

<div class="post-metadata">

**Author:** ![MarcCheong](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/marccheong/32/23266_2.png) [@MarcCheong](https://forums.pega.com/u/MarcCheong)\
**Post date:** [April 14, 2026, 10:59am UTC](https://forums.pega.com/t/semantic-url-in-constellation/9800/9 "2026-04-14T10:59:18Z")

</div>

For those finding this conversation (like I have today), this might help [Deep linking and Semantic URL](https://forums.pega.com/t/deep-linking-and-semantic-url/9722)
