We have an existing application in pega 6. In one of our Integration, an external system creates URL to connect to our system and to open a specific search option; to do so it has Tabthread0 as part of the URL creation. Attached is the screenshot of sample URL. Now that we are upgrading to version 8,we noticed pega does not create Tabthread0 anymore. Will it create a problem when upgrade is done ? Or Pega can process it? Do we need to replace Tabthread 0 with Tabthread1?
***Edited by Moderator: Pooja Gadige to change content format from Discussion to Question, add platform capability tags***
@DEBADRITA It completely depends on the Dynamic Container (DC) mode and DC configuration.
On framed portals,
if DC is configured with the section then we are not creating a new thread.
If DC is configured with a harness then we are creating a TABTHREAD0 thread.
On frameless portal launch, we are always creating a single thread (STANDARD/ OpenPortal_pyCaseWorker).
Can you please elaborate this? The application is in production and we need the search option as attached screenshot.Requirement is the external application sends the account number as part of URL and when operator clicks on the URL, the portal as attached screenshot is opened and search results are shown based on account number passed. This is achievable in 8.5 , correct? If so, do we need to make changes in URL as tabthread0 is present in URL.