CPM issue with interaction context page
When launching multiple interactions in different IE tabs, the content of a custom thread family page is shared between interactions.
Steps to Reproduce
- Create a page which is used to store interaction wide content and promote it to thread family scope in interaction processing.
- Launch an interaction which references said thread family page in multiple locations.
- Launch a second interaction in another thread.
- Navigate back to the first interaction and observe that the references to the thread family page contain information from the second interaction.
An issue in the custom application code or rules. The threads launched in this custom application do not have the tags looked for when extracting an applicable thread family during thread creation.
Core engine pega platform support is there for associating a thread to thread family automatically when we follow a pattern for thread names; pyNS_[ThreadFamilyName]_XXXX. When a thread name is starting pyNS_, thread family will be set automatically. In this case, pxFamilyName will be set using the identifier which is there between ‘pyNS_’ and the next ’ _’.
Here’s the explanation for the reported behavior:
The behavior seen is expected given the lack of tags to have a thread family property extracted at thread creation.
0% found this useful