In the Runtime

Now we want to test the behavior in the Runtime.

Start the Runtime or – if it is already running – switch to the Runtime and reload the changes.
Change the value of any variable in a dynamic element.

The set value is not sent to the hardware. Instead, a message box opens telling you that you do not have the authorization for this project.

Fetch the authorization with the according button.
Change the value of any variable in a dynamic element.

This time the value is really sent to the hardware, because now you own the authorization for this project.

Go to another computer, where this project runs.
Start the Runtime, if it is not already running.
Change the value of any variable in a dynamic element.

Again the value is not sent to the hardware and the message box opens.

Go to the first computer.

In the meantime, a dialogbox has opened up here. You are asked, if you want to hand over the authorization to the other computer. Now there are three ways to react:

Yes

The authorization is handed over to the other computer.

No

The authorization stays on this computer.

Do nothing

In the dialogbox you can see a time running towards 00:00. As soon as this time is over, the authorization is automatically released and the other computer gets it.

This guarantees that the project stays operable, even if no person is on the computer with the authorization at the moment.

This time interval is set to one minute by default. In the project properties under Network, you will find the property Authorization/Timeout for request [s] . You can change the timeout there.