UI Builder Caching On Link To Destination/Redirect

[Kevin Schaub]

I am working on a scoped application in my PDI that is leveraging UI Builder for the front end. When I do a "link to destination", then navigate back to the previous page the page appears immediately (data resources don't appear to refresh), and the values I typed in the inputs and didn't save persist. 

It appears that the UI is caching everything? Anyone else have this issue?

[Tristan Elmore]

Are there any updates on this? This is causing a lot of issues and extra workaround time spent as we start to create new workspaces + experiences (as well as roll over legacy ones on our instance) with UI builder.

The cache issues flat out break dozens of features in UI builder or leads to inconsistent experiences + functionality. I have a set of a few event handlers on a typeahead on a landing page that redirect to a record clicked from the results. While doing so, it sets a loading state—but then if you navigate back, the typeahead still has the same value selected while the loading state blocks any input or changes to the page. That's simply one example of at least five cases building a single Portal experience in UI Builder where I've had to add extra unnecessary parameters or spend hours / days to come up with a workaround due to cache issues.

@Brad Tilton @John Rissone, any insight either of you may have here would be greatly appreciated. Our organization has built out over 15 different legacy 'portal experiences' for different internal departments and groups that we're trying to modernize and get switched over to the Next Experience UI.