Hi all,
I wanted to provide a clarification on the usage of the Query Metering license.
First, with answering Jason's questions:
1. Updating an existing document will not consume a query from the allotted queries per hour. The only action via the Unity API that will consume a query, is when you perform a document query.
2. Same as #1, it will not consume a query.
There are no functional limitation of creating new documents or updating existing documents via the Query Metering license, but that is not the main intent of this license. This license is intended to be used as a cheaper alternative for solutions with external end users that do not know or care about OnBase, and/or do not require full functionality of the OnBase software, and we believe that the document query would be the most important and prominent functionality that an external users would need from OnBase, so that's why this license only consumes when performing a document query.
One can argue that if the Query Metering license is only intended to be used for document queries, why is it able to do everything else that a Concurrent Client license can do, and that's something that I can't really answer since I was never involved in the initial inception of the Unity API, so I don't know the discussion that happened around this license and its usage in the Unity API, but my guess is that we wanted to leave that up to the developer to make that decision.
With all that being said, I don't see this as something that's black and white, as to say that if an external user is even doing one thing that's not a document query, the Query Metering license can't be used. I have seen many exception cases for using this license, from allowing non-document query actions to be taken, and even being used in a solution that are used by both internal and external users (internal users being the employees of the OnBase customer). It's mostly decided on the degree of how your solution deviates from the initial intention of this license, and that is something that should be discussed by folks at Hyland, but most of all, it should be discussed before the license is even offered as an option to the customer.
With what Alex mentioned about our material not reflecting this information, that is certainly true, so we will look into updating those materials, at the very least for the API Training class.
