Support Article
ReloadSection activity loses tab index
SA-6823
Summary
A repeating tabbed layout is configured to include "Refresh other section" functionality to refresh sections within the tab. This works fine if the operator creates a new tab and performs all the work in that tab. If they switch to another tab, and then go back to the original tab the refresh other section and any associated activity uses the context of the previously opened tab. It appears to the operator as if the action they have just performed has not worked.
A button is configured to refresh another section. This section is used as the content for a tabbed repeating layout.
If the operator has switched back to Tab 1 and back to Tab 2 before clicking the button the refresh happens to the section on the other tab.
Error Messages
No error message.
Steps to Reproduce
- Configure a repeating tabbed layout where the tab content contains multiple sections and "Refresh Other Section" functionality. e.g a button to refresh another section.
- Add a tab (Tab 1).
- Add another Tab (Tab 2).
- Switch back to Tab 1
- Swch back to Tab 2
- Perform the operation that invokes the refresh other section.
- The refresh happens in Tab 1 rather than the currently selected Tab 2.
Root Cause
Refresh Other section doesn't support multiple section refresh if the section is in a repeating layout (i.e the same named section appears multiple times, once in each tab).
Resolution
HFix-20910 for 6.2 SP2 adds support to refresh ALL the occurrences of the same section in UI.
This fix is included out of the box in PRPC 6.3 SP1
Published January 31, 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.