hi Murof

I read your post twice and feel like i fundamentally don't understand screen navigation in the wincc unified. Can you please help?

1. In Unified you often have a Screen architecture with screen Windows and you will not change your main screen so often (or even once) -  Can you please explain from high level point of view where the difference comes from between wincc unified and wincc comfort ?
   
2. Do other wincc families (other than wincc unified ) have the same or similar screens navigation structure?
3. Why is triggering popup from the tag such a pain?

Murof

Hello DariusB

The suggestion from Siemens for the Area Pointer to change Screen is as you described is a script in the screen context of your Basic Screen:

https://support.industry.siemens.com/cs/ww/en/view/109794243

Since V18Upd1/2 you can also use the mainScreenwindow in the Screen management.

here you can dynamize the screen Property with a Tag or a Script. But I would not compare here WinCC comfort/advanced with Unified. In Unified you often have a Screen architecture with screen Windows and you will not change your main screen so often (or even once). So a Script in a dummy Object in the Main Screen context (with the Tag as trigger) is a suitable way to trigger what ever you want. This would also be a good way if you use Server/Client

Bye Murof

------------------------------------------------------------------------------------------
Split from Unified panel open Popup from PLC tag.

rdoliveira

my application does not have multiple simultaneous accesses

 Hi 

Basic stuff.

Is wincc unfied ready for the multi client operation. In other scada systems client tags will be used to store data for the individual sessions. Any idea how is it done in wincc unified if possible at all?

Regards

 hi Stefan 

You answered all questions thank you