Applies to Pega Platform versions 8.4 through 8.7
This article provides answers to frequently asked questions about Application Alias.
Introduction
Application Alias enables you to log into multiple applications using a browser. It also enables you to access all the applications simultaneously on different tabs.
For more information on Application Alias, read the following articles:
Answers to frequently asked questions
What happens on creating a new application without configuring Application Alias?
What characters are allowed or accepted while defining Application Alias?
Can I log in with old Alias after updating Application Alias to a new value?
What happens on creating a new application without configuring Application Alias?
The new application is created without issues since the value of the pyProductName Clipboard property is considered as Application Alias by default.
What is considered as Application Alias by default when an application is created with Unicode characters?
Unicode characters are not accepted for Application Alias. The base64 encoded value of pyProductName is considered as Application Alias by default when an application is created with Unicode characters.
Why am I unable to log in using the URL, prweb/app/appalias1/, when I define Application Alias as AppAlias1?
Application Alias is case sensitive when you attempt to log into the application whose alias is AppAlias1. You must log in with the URL, prweba/app/AppAlias1/.
Why am I encountering the error message, URL Alias is already in use, while attempting to define Application Alias for my application?
The following are the reasons for the occurrence of the error message:
- Same Application Alias is not allowed or accepted for different applications
- Different versions of an application can have same Application Alias
What characters are allowed or accepted while defining Application Alias?
The following table illustrates the characters that are accepted while defining Application Alias on different Pega platform versions:
|
Pega platform version |
Characters accepted |
|
Pega 8.5 and earlier versions |
Alpha numeric characters |
|
Pega 8.6 |
Alpha numeric characters and hyphen (-) |
I have TestApp1( alias= testalias1) configured as the default application and TestApp2(alias = testalias2) as the secondary application in my Operator. What would be the context of the session if I log in with prweb/app/testalias2?
Session context would be TestApp2(testalias2) when you log in with an explicit Application Alias in the URL.
I have the application, TestApp1 (alias = testalias1), configured in a Pega instance and my Operator has access permission to TestApp1:Administrators, TestApp1:Authors, and TestApp1:Users. What would be the context of the session post login?
Scenario 1 - Operator has access permission to TestApp1:Administrators, TestApp1:Authors, and TestApp1:Users. However, neither of them is selected as the default AccessGroup.
Access Groups are picked based on the order in which they are defined in the Operator.
Scenario 2 – Operator has access permission to TestApp1:Administrators, TestApp1:Authors, and TestApp1:Users. TestApp1:Authors is selected as the default AccessGroup.
AccessGroup selected as the default AccessGroup is picked first irrespective of the order in which the AccessGroups are defined in the Operator.
The error message 'You do not have access to the application with alias ‘Alias1’' displays while attempting to log into Pega instance. How to address this issue?
This error indicates that none of the AccessGroups that are configured in the Operator has access to the application with alias as Alias1.
Perform the following steps to debug the issue:
- Open the Operator record and verify the available AccessGroups for that operator.
- Verify that the AccessGroup corresponding to Alias1 application is present in the Operator record.
Why is an underscore (_) suffixed to the alias name in the URL when Application Alias is configured as TestAlias1?
Scenario 1 - Application Alias is provided in URL before logging into Pega instance
When you provide Application Alias in the URL before logging into Pega instance, you are redirected to prweb/app/alias/AGHash post login. No characters are suffixed to Application Alias.
Scenario 2 – Application Alias is not provided in URL before logging into Pega instance
Entering Application Alias in the URL is not mandatory. When you click, prweb/PRServlet, and attempt to log into Pega instance, the following steps or work flow is executed:
- You are redirected to prweb/PRServlet/app/default/. The Login page displays.
- You are redirected to prweb/PRServlet/app/Alias1_/. This occurs when Alias1 is the Application Alias for the default AccessGroup of the Operator. The appending of Underscore (_) indicates that you do not have an explicit Application Alias.
- You are redirected to prweb/PRServlet/app/default on logging out. The Underscore (_) is used to redirect you to prweb/PRServlet/app/default/ on logout. This is to support backward compatibility.
Can I log in with old Alias after updating Application Alias to a new value?
No. The old Alias cannot be used to log in after Application Alias is updated to a new value. All the URLs that are generated with old value (for example, emails, and so on) stop working when the URL is updated to a new value.
I have not set Alias for my application so far. How does this affect the already generated URLs if I set Alias now?
pyProductName(Product Identifier) is used as the default Alias if the Application Alias is not defined. Hence, any URL generated or all URLs have the Product Identifier as Alias. All the URLs that generate from the Product Identifier work even when you set Application Alias for the first time.
How to make sure that the URLs generate correctly when sending emails that require Pega URLs to be constructed in different formats?
Use the URLBuilder functionality to build URLs dynamically. PegaURLBuilder is used to construct Pega URLs in various formats. Based on the specified methods, it identifies individual URL components and then constructs the final URL. It can be used to build external and current session URLs.
Read this Pega Community article for more information regarding the URLBuilder functionality, Interface PegaURLBuilder
Related Content
Simplify access with an Application URL alias (8.4)
Adding an application URL alias
Custom application URL alias in the application definition
Developing applications that open in multiple browser tabs or browser windows
