Writing a value through a .wpf element to an internal variable is not possible when authorization in the network is enabled and the system does not have the authorization token.

• Related Articles

• FAQ: Initialization of Internal variables (Network) in Dominant redundancy mode.

  When (re-)starting the dominant Server 1, regardless of their 'Remanence' configuration, internal variables with calculation in 'Network' are initialized first in the dominant Server 1 and only after synchronized with the running Server 2. Modules ...

• It shall be possible in standalone projects to prevent interaction with the process like with the token for network authorization

  Summary It shall be possible in standalone projects to prevent operation in the same way that is possible through the access token for network authorization, using the value of a variable that can be configured. DescriptionIt shall be possible in ...

• No feedback to an operator on a runtime client when the network authorization token was requested but has already been reserved on another runtime client

  Summary When an operator requests the network authorization token on a system "C" while the token currently lies with the system "A" but a reservation has been made for the token on system "B", there is no feedback to the operator that the token ...

• The WPF element property window may display a different linkage value from the configuration dialog in the Editor.

  Summary The WPF element link “Authorization/Interlocking” type may display a different linkage value in the property window from the selected value in the configuration dialog in the Editor. DescriptionThe WPF element link ...

• Internal variables with calculation "Network" as index variable cause performance and consistency problems

  Summary Index variables cause long waiting times when replaced on the client. This problem was solved by a cash. Description For internal variables, the Calculation property is set to Network. These variables are used as index variables. During ...