LOCAL SETTING:x

Continuing the discussion from Setting ISCURRENTWORKPERIODOPEN:

Hi @emre what was the reason you need to force a User to Log Out before this Setting is Refreshed?

This tile was set to refresh but it is pointless, right?

Can this not be a GLOBAL SETTING:x accessible variable. I have not set this to a V5 REQUEST as it seems too obvious and you must have a valid reason…

Welcome your comments.

I think you may be confused. It does update if Work Period is opened or closed regardless if user logs in or out. What he was referring too is if you clear transactions which also resets work period… That will not update that setting until you log out,.

The reason is because its in memory and not a SQL table.[quote=“pauln, post:1, topic:12047”]
This tile was set to refresh but it is pointless, right?
[/quote]

Nope it will work just fine.[quote=“pauln, post:1, topic:12047”]
Can this not be a GLOBAL SETTING:x accessible variable. I have not set this to a V5 REQUEST as it seems too obvious and you must have a valid reason…
[/quote]

If you want it Global you can make your own, in fact me and @QMcKay were using our own until Emre put in the local setting for us.

I do not understand your answer here @Jesse - if you check my settings above, AND if I CLOSE the WP from another terminal THEN this Tile does not change, it still shows the WP in its last state.

That’s what I was referring to as “pointless”…

Well you didnt say that. I would think message server might refresh that.

Thanks for your reply kendash. Will message Server refresh “Local” variables for a terminal? Typical local memory is just that “local” and not accessible.

What is your understanding of Emre’s Local references here?

Maybe you should just try it first because you would know that it works just fine with message server. Instead of trying to figure out Emre’s brain :P[quote=“pauln, post:5, topic:12047”]
Typical local memory is just that “local” and not accessible.
[/quote]

No that is not true. You can access local settings. In fact you can create your own local settings using Update Program Setting action. [quote=“pauln, post:5, topic:12047”]
What is your understanding of Emre’s Local references here?
[/quote]

My understanding is exactly how Emre explained it. It works like other settings but its local to that machine and not written in the database. This does not mean it cant be manipulated with message server. When you start or stop a work period message server sends a message to all terminals which updates local settings.

You will also notice that it automatically updates the navigation screen as well on all terminals.

Finally: you do not have to use LOCAL SETTING:X simply SETTING:X works fine.

[=('{SETTING:ISCURRENTWORKPERIODOPEN}'=='TRUE' ? 'Ready' : '<color Red><italic>NOT</italic></color> ready')]

PS: I am curious did you write all of this without testing it?

That is what I wanted to know.
The answer to your question yes I have not tried this as I do not use Message Server (at this point). Like your venue, my venues are very different in nature. I always search for related threads and come here for more clarification, (and directions for navigating the “said” brain!)