Active Contract State

UI Access

In the Utility UI, the entire state of active contracts is read only once for a given template or interface. By default, the initial query is made using WebSockets. The UI uses a regular HTTP call as a fallback if, for any reason, WebSockets fail to connect.

After the initial state is established, the Utility UI queries only for granular state updates and applies them on top of the initial state.

Both the initial state and all subsequent updates are stored in browser local storage.

This results in much faster response times when querying data from the UI, as well as a reduced network footprint.

Disabling WebSockets

By default, the initial state of active contracts is queried using WebSockets.

If, for any reason, you wish to disable this, follow the steps below.

1. Login to the Utility UI.

2. Enter user settings.

3. Toggle the “WebSockets” switch to disable it.

Now, all queries for active state contracts will be made via regular HTTP calls.

Troubleshooting

If you encounter any problems using the Utility UI with either displaying or querying for the data, try the solutions below.

Clearing Local Storage Cache

Clearing Local Storage cache may help when data is not rendering or not displaying properly. After doing this, the Utility UI will again query the server for the initial state of active contracts when entering affected views.

1. Login to the Utility UI.

2. Enter user settings.

3. Press the “Clear” button on the “Active Contract Storage” tile.

All the data associated with the Utility UI in your browser local storage should now be removed.