A WebView solution is a group of pages that can be opened and worked on together. All open WebView pages are held in memory to allow quick switching between them, and the solution provides a way to configure page management settings for all its pages simultaneously.

An empty solution is created by default when starting WebView with a default set of page management settings. Those settings can be changed, and pages can be added to the solution from the Solution Properties tab.
To add pages to a solution:
On an open WebView page, or from the Pages tab, right click on the page's title to open the page context menu, and select .

Go to the Solution tab.

You should see the page in the list.

You can check the button for the page to have it load automatically when you open the solution.
To save the solution, first expand the Identity properties in the Solution tab and enter a unique name.

Then from the menu choose . The file will saved with an
.xml file extension.

Once you have saved your solution, its file name will appear in the list whenever this dialog is reopened.
To open a saved solution, from the Pages tab,
choose the relevant
path/username/Pages
drop-down, and double-click on the arrow icon of the solution you need
to open.

The available properties in the Solution tab are as follows:

The name of the solution, as a text string.
The name of the XML file that contains the solution configuration data.
The WebView user that created the solution.
A text description of the solution.
The most recent user to have edited the solution.
The properties in this section are used to manage memory. Each active page consumes memory. Setting limits on the maximum number of active pages, number of controls, and memory usage threshold ensures that the application continues to perform well.

The number of minutes to keep pages in memory when they are active. A page that has been inactive for a longer time than this number of minutes will be silently unloaded. Revisiting the page tab will reload the page. A page that has changes will not be retired until after it is saved.
The maximum number of pages that can be loaded in memory at the same time. When the number of open pages exceeds this number, pages will start getting retired.
The maximum number of controls a page can have to be considered eligible for retirement. A page containing a large number of controls will consume more memory and it will be retired earlier than other pages containing fewer controls.
The number of kilobytes of memory allocated for use before pages start getting unloaded to free up memory resources.

A list of all pages in the solution. Checking the button for a page causes it to load automatically when the solution is opened. For example, when this solution is opened, two page tabs will be added: one for the Notifications page and one for the Tank Level page.