Thread names appearing wrong in Clipboard
Hi All,
Our app is using the RedirectAndRun activity to launch cases in an older version of our app. Unfortunately, whenever we open a case this way, the names of threads in the clipboard appear wrong (only show ID, not display name). I'm also told that the threads will not go away (be removed from memory) even after the corresponding cases are closed.
Having done a bit of troubleshooting myself, I've noticed that the display names for threads are populated using a page called Declare_pyDisplay, which holds info about the UI components associated with the threads. Unfortunately, after calling RedirectAndRun, it looks like Declare_pyDisplay is not populating properly. I'm not sure why this is, but it's preventing the threads from getting their proper display names.
Does anyone have any idea what's going on with this? Why isn't Declare_pyDisplay updating properly when we open cases using RedirectAndRun?
See screenshots for reference.
Thanks,
Matt K
Accepted Solution
PEG
US
There appear to have been quite a few issues trough the years regarding the proper update of this page. There have been numerous local changes, and a bunch of hotfixes. I suggest that you create an SR for this, as it is quite likely that there is a defect that needs to be addressed, either through another local change, or a hotfix.
Pegasystems
US
I think you'll want to do some sleuth work with this one. Use Pega-tracing to answer these questions:
- Does the activity associated with that declare-page usually get performed, and it isn't being performed in your case?
- If it is being performed, those conditionals within it that may prevent some of its lines to be performed, are they preventing the update?
Accepted Solution
PEG
US
There appear to have been quite a few issues trough the years regarding the proper update of this page. There have been numerous local changes, and a bunch of hotfixes. I suggest that you create an SR for this, as it is quite likely that there is a defect that needs to be addressed, either through another local change, or a hotfix.