Hi,

I have the same issue as well, I already applied both:

• RefreshOnDocumentSwitch - Yes
• RefreshOnTabSwitch - Yes

In the IAM Model - Extended Properties and the Global settings - Extended Properties and it's still not working.

I'm having the same problem in Universal 2023.1.16.0

A custom process flow to refresh a specific document upon activation also doesn't work either

We have received a ticket of this, and will be looked at

Hi all.

We're not linked to the ticket in TCP, so i am not in the loop. But we re still facing serious refresh issues and questions from users looking at stale data.

Any progress on this?

It turns out it requires the exact value of "true” now to get activated. So this is your workaround for now.

We will improve the logic to also allow values like "yes” and "1”.

Hi Erik,

Thanks for your reply. I've configured the Extended Properties as you described (see picture)

However, it still looks like it's not working. I don't see refreshed data on reopening a document.

Is there anybody out there using these properties and can confirm it is working?

​Please add this setting to your Runtime Configuration in the Software Factory and synchronize it to your IAM application. 

It seems like there is an issue with extended properties directly added to the application through IAM. Looks like it gets filtered out from being available for the Universal GUI now.

@André Romijn Would you mind reporting a TCP ticket for this to follow this up, or shall I do it for you?

​

@Erik Brink
Thanks for the research on this issue. I've removed the Extended Properties from the IAM and set them in the Runtime Configuration and synchronized it to the IAM. However, this still doesn't resolve the problem.

Would you be so kind for reporting a TCP ticket. Thanks in advance!

I will.

What value did you gave the Extended property in the Software Factory? It still has to be "true” for now and the checkbox "Expose to front-end” should be enabled.

 

@Erik Brink see our settings below
 

I had to give my browser a hard refresh (Ctrl+F5) before the new settings came though from IAM. 

The GUI uses a so called "Serviceworker” to cache model definition within case we lose connection and we want to continue working offline.

Does this do the trick for you too, @André Romijn ?

I don't think so @Erik Brink . The properties are coming to my browser (see picture), but still the refresh is not happening.

While testing it on several cases, we found a second problem, which have to be fixed in the logic of the GUI. 

We will keep you posted about the status.

Sorry for the inconvenience.

We did not manage to resolve this as part of the current sprint which will be released tomorrow. This items will be continued on the next sprint with an expected beta release date on the 30th of June.

Hi @Erik Brink 
 

Do you have any update on this? I didn't see anything in the release-notes of the Universal GUI 2023.2.10 beta, or did i miss something?

The fix missed the end of previous sprint and became larger then we initially expected.

Now, we've resolved it and will be released as part of the 2023.2.11 release which will be available on the 31th of July as a beta release and a week later as the official release.