Question
ASB
IN
Last activity: 6 Jul 2023 12:27 EDT
Understanding URL mapping and application alias
We are trying to understand the order of working of application alias and URL mappings.
This is the URL we're using "https://example.com/prweb/app/Lighthouse/createcomplaintcasebytoken/~1" Lighthouse - is the application alias. /createcomplaintcasebytoken - is the URL mapping
How does the order of invocation takes place when the URL we're using here is hit in a browser ?
Will it look for the URL mapping and login to the application alias or first login to the application and then look for alias?
Anyone please share your inputs.
Pegasystems Inc.
NL
I am also investigation this.. what I see that you application needs to have URLmapping named "pyDefault" and you have configure what you would like to do within that URL mapping .. i.e. opening a case is probably most popular one..
When you configure this and hit the URL according to your config, the system gets the request, parses the url (i.e. gets the parameters) and runs the activity you are set as a part of URL mapping.
If you don't create such a mapping rule, the system does not know what to do ..
This is what I understand since the morning, in nutshell:)