screen_local [ErgoTech Systems, Inc. TechWiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
When you are simply reporting values from an industrial controller or similar data source, all the web-displays for all users should show the same values.  However, when a request is made from the UI it's possible that the values should be sent only to that display.  A common example of this is the display of data from a database.  Each user can select their own lookback period and display data unique to them.

In this case, you simply mark the whole chain of logic, from the component on the screen that triggered the search to the display component as "ScreenLocal".  The "ScreenLocal" property is in the "Expert" tab of all the non-graphical components.  For example, here's a BroadcastServer with the property set to true:

{{:pasted:20210404-140458.png?400}}

Another example is using an on-screen component to cause a popup window to appear, for example asking for additional information.  An example of this is in our SECS/GEM data collection solution where, once the user enters a lot-id, they are automatically prompted for an operator Id.

{{:pasted:20210404-130719.png?400}}

In this case, we want only the application into which the lot-id was entered to prompt for the operator, but all application to be updated with both the lotid and the operator.

{{:pasted:20210404-130633.png?600}}

In this case, the components between the BarCodeInputField and the PopuInitializer are marked "ScreenLocal" (ScreenLocalLotId and SetValue).  That's all that's required to ensure that the popup only appears on the page where the user scanned the lotid.