Support Article
User pages are not removed when tab is closed in portal
SA-19237
Summary
User has multiple work objects opened and the respective threads are reflected in the clipboard. However, when some of the work objects are closed and the clipboard is re launched, the clipboard still holds the threads details of the closed work objects and is not reflecting the exact current state. This is leading to piling up of data in the clipboard, leading to performance issue.
The use case has "pyCaseManager" portal with customization.
Example:
1. Using pyCaseManger portal(old)
2. The Thread “PS!_TABTHREAD1/$WorkProcessing1” is still present after closing the thread.
3. Data is also present for the thread
Error Messages
Not Applicable
Steps to Reproduce
1. Create multiple flows.
2. Run the created flows to create multiple work objects.
3. Open the clipboard and notice that the threads are created respectively.
4. Further, close some of the work objects and re launch the clipboard.
5. Notice that the clipboard is not reflected the current threads. Instead it is showing even the threads of closed work objects.
Root Cause
The issue was replicable because of the usage of WorkArea container.
Resolution
Perform the Local-Change :
Replace WorkArea container with Dynamic Container (with tabbed layout as per the requirement).
Published January 30, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.