Question

1
Replies
78
Views
 Susheel Bonthala (SusheelB0531)
JP Morgan Chase & Company

JP Morgan Chase & Company
US
SusheelB0531 Member since 2018 7 posts
JP Morgan Chase & Company
Posted: August 20, 2019
Last activity: August 24, 2019
Posted: 20 Aug 2019 11:53 EDT
Last activity: 24 Aug 2019 18:44 EDT
Closed

pxGetThreadIDForActiveUI is not showing the correct thread id

We are using pxGetThreadIDForActiveUI function to identify the active thread in UI. But the thread id and other values in Declare_pydisplay are same when the user is on dashboard or the custom harness (noAssignmentsAvaialble) . Is there any other way to differentiate the active thread in UI?

Low-Code App Development User Experience
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 1 year ago
Posted: 24 Aug 2019 18:44 EDT
Susan Liu (SusanLiu_GCS)
PEGA
Principal Software Solutions Engineer
Pegasystems Inc.
US

The function pxGetThreadIDForActiveUI is used to find out the active thread.


Belows can track the active document:



-Declare_pyDisplay.pyDisplay(pyCaseManager7).pyUIActive(1)


-Declare_pyDisplay.pyDisplay(pyCaseManager7).pyUIElements



.pyDisplay is a page group where the index is the portal name. .pyUIActive(1) or .pyUIElements has the information you need.