Configure application-level settings
- Last UpdatedNov 22, 2022
- 3 minute read
- PI System
- PI Manual Logger 2017 R2
- Visualization
In the web.config file, you manage how users interact with PI Manual Logger Web.
-
Open %PIHOME%/Piml.Web/web.config in a text editor.
-
In the section, change the following settings as needed.
Setting
Default value
Description
AutoSaveLocally
Add this setting and set to to enable users to save automatically to local browser storage when they navigate to the next tag on the individual data entry page, or when they enter a value on the grid data entry list.
Note: Performance can be impacted when using this feature.
BypassAuth
This setting empowers PI Manual Logger Web to bypass authorization of all users for all tours. The consequence of this setting is that every PI Manual Logger Web user can create tour runs for every tour and perhaps override Full Access Group and Data Entry Group associations you might have previously set up for tours in the PI Manual Logger PC client application.
To utilize the settings you previously established in the PI Manual Logger PC client, set to False.
ConnectionTimeout
This setting determines how long in seconds the application waits to establish a connection to the IIS Web Server, when determining if the user is Online or Offline. If this timeout is reached before a successful connection is registered with the server, the user will be put into offline mode. This connection test occurs before the database connection test mentioned in the DBConnectionTimeout setting. If successful, the database connection test occurs. If both are successful, the user is determined to be Online. The user is determined to be Offline if either fail.
DBConnectionTimeout
This setting determines how long in seconds the application waits for a database connection to be made, when determining if the user is Online or Offline. If this timeout is reached before a successful connection is registered with the PIML database, the user is put into offline mode.
DefaultColumnsToDisplayInGrid
This setting contains a comma-separated list of column headings that are displayed by default when the grid is shown in PI Manual Logger Web. The following column headings are available: Index, Name, Group, Description, Value, PreviousValue, EngineeringUnits, Comment, Timestamp, Limits, Instructions, Violated, and Rejected.
If this setting is not provided, the default columns are used.
Note: Some read-only columns, such as EngineeringUnits and Limits, are only displayed if a tag in a tour contains a value for that column.
DefaultPageSize
This setting determines the default number of items to be displayed in grid data entry view for all users.
DefaultToGridView
You can configure the default view for the data collection to be the grid view.
Here is an example of what this looks like:
DigitalStateSortOrder
You can now set the display order for digital states through the DigitalStatSortOrderoption in the appSettings section of the web.config file. The following options are:
CodeDesc - Will be sorted by state code descending,
CodeAsc - Will be sorted by state code ascending,
NameDesc - Will be sorted by state name descending,
NameAsc - Will be sorted by state name ascending.
Here is an example of what this looks like:
GetHistoricalValuesFromPI
You can configure how your historical data is retrieved, either directly from PI Data Archive or from your PI Manual Logger SQL Server database cache. The default is to retrieve directly from PI Data Archive. This configuration will also affect how Limit Tag values are retrieved.
PromptForFilterListChangeWhenTourRunDataExists
This setting determines how PI Manual Logger Web behaves when users are online and tour run data already exists when they load a new filter list. When set to , PI Manual Logger Web automatically performs a refresh which sends all tour run data, removes tour run data from local storage, and updates the local tours and configuration. When set to , PI Manual Logger Web prompts the user to see if they want to perform a refresh, send the tour run data, and reload the tours and configuration.
UseGeoLocation
This setting enables devices that have location tracking enabled to log latitude and longitude geographic location coordinates for each tag during a tour run. The data is stored in the field in the .
Note: OSIsoft recommends that a secure context such as HTTPS be used with this setting, since some browsers require a secure origin to capture geolocation information.
Please see the pre-installation section of PI Manual Logger 2017 R2 Release Notes for more information.