Changes
== Features ==
* Supports multiple value types
* Multi-server configuration* Correctly formatted value in Attributes
== Prerequesites ==
To be able to successfully set up the system, the Ubik server/development machine needs access to the OSIPI instance. This can be easily checked in the web browser by navigating to the provided URL. [https://techsupport.osisoft.com/Documentation/PI-Web-API/help.html|OSIsoft's PiWebAPI] is a REST API, from which the plugin reads data.
== Configuration in Ubik ==
In the case of '''Basic authentication''', put the credentials in the respective fields <code>LOGINNAME</code> and <code>PASSWORD</code>. Be aware that domain backslashes might need to be doubled, thanks to their escaping nature: <code>DOMAIN\\USER</code>
If you leave the <code>LOGINNAME</code> field empty, the client tries to authenticate against the OSIPI server with <code>[https://docs.microsoft.com/en-us/dotnet/api/system.net.webclient.usedefaultcredentials| WebClient.UseDefaultCredentials]</code>. Should this be the authentication of your choice, be aware that the Ubik Studio/Enterprise Service/Web Service needs to be started as that user that has access to the PI system. == Attributes ==The OSIPI Plugin delivers the correctly formatted value in the Live Value Attributes collection, which can be [[Live_Values#Binding_to_Attributes|bound to directly from XAML]].The [https://docs.microsoft.com/en-us/dotnet/api/system.globalization.cultureinfo value formatting culture] can be set in the '''OSIPI_SERVER''' configuration with the <code>FORMATTING_CULTURE</code> field, which defaults to <code>EN_US</code>. There's also an option to trim leading zeroes (<code>TRIM_LEADING_ZEROES</code>, defaulting to <code>false</code>).
