We are seeking assistance to enhance portal performance by introducing functionality that disables zone refreshes when a Portal Context variable is updated but not referenced in the zone’s filters or hidden filters. This behavior appears to be standard in WACS but is not consistently applied across all portals, and it's significantly affecting performance—particularly in data-heavy screens.
Currently, both custom and standard (e.g., Planning Portal) screens are experiencing unnecessary zone refreshes whenever any context variable is updated, regardless of whether the zone actually uses that variable. This leads to:
Performance degradation due to redundant data loading.
User experience issues, such as zones resetting to default views.
Workflow interruptions, especially when users scroll through an info zone and lose their place after an unrelated action triggers a full refresh.
We believe this enhancement would greatly improve usability and efficiency across multiple portals. Please let us know if further details or examples are needed to support this request.