06-29-2017 02:46 PM
I have a custom app that is using the Unity API via a v10 instance of the web service running against OnBase v13. It retrieves document using Core.GetDocumentByID. We recently added some new document type groups/document types, and the API call is not returning documents in those types.
The API call is still working normally for the older document types. Also, the account being used does have access to the new types in the client. The web service supporting the app has been restarted since any changes were made.
Is there a permission we are overlooking that explains this behavior?
Thanks,
Ulrik
07-10-2017 11:00 AM
Hi Ulrik,
As Scott suggested, you need to restart your application server for the changes to be recognized. If it still doesn't solve your issue, I recommend you to contact your first line of support and they will be able to debug the issue for you.
06-30-2017 05:03 AM
Typically, this happens when the OnBase application server that the API application calls has not been restarted. When you say that you restarted the "web service," are you referring to the OnBase AppServer pool?
06-30-2017 07:31 AM
07-10-2017 11:00 AM
Hi Ulrik,
As Scott suggested, you need to restart your application server for the changes to be recognized. If it still doesn't solve your issue, I recommend you to contact your first line of support and they will be able to debug the issue for you.
07-20-2017 07:18 PM
If after restart web service your problem persist, check if you new document types are configured to be stored on another disk group so user that impersonate "web service" NEEDS to have access to that volumes.
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.