Manually Generating UnityPop Files

[Matt_Savigear]

One of the most useful things about DocPop is the ability to manually generate the format outside OnBase without having to somehow use the API to get the link. This allows third party systems to publish DocPop links to documents in OnBase simply by knowing the path to the server and a couple of keyword values - from these a "templated" approach can be taken to produce working URLs.

Unity Pop seems to have a limitation which prevents this - the <Signature> tag. If you empty or remove this tag, the upop file refuses to work, but this means that we need to hit OnBase for a upop file for every document we want to have access to. Fine for small volumes, but a problem for high volume applications where this would generate performance problems and require more complex two-way communication structures to be set up.

So, given the rest of the XML is easy to generate, is there a way of bypassing the requirement for this internally generated signature, or some straightforward method for generating it to remove the reliance on a Unity API connection?

[Tyler_Sorber]

Hi Kevin

I am not aware of any Config Change that can be made to remove the Signature from the creation of a UPop File.

I would recommend looking into the SDK for OnBase 16, as a large UPop overhaul was completed. this allows the creation of UPop Links and Files Dynamically for multiple cases such as Showing a Document, Workflows, and CustomQueries.

[Alex_French]

Kevin's post had some content thrown away, I'll see if I can clarify and get the content to stick-

In OnBase 15, when using Unity Pop links (not files), you can set this value in the section of your AppServer's web.config:

<add key="permitUpopLinksWithoutSignatures" value="true"/>

That last line gets lost when entering a new comment on Communities, but seems to be correctly handled when inserted when Editing the comment.

[Sriram_Seshadri]

The SDK does not have an example per se but in Home / Pop Integrations / UPop / UPop Usage:

Creating a UPop File

The API used to create the UPop file is Hyland.Unity.Utility.CreateUpopFile(<document id>). It returns a stream that can be saved to disk, along with the extension of the file.

At this moment, no. The Upop file created by the API will open the document but not in Workflow.

[Sriram_Seshadri]

As long as you know the document ID and don't have to query OnBase to get the document ID, the Unity API method to create an UPop file does not require an Integration Toolkit license. This license is only needed when you do an Application.Connect call. Since you can create UPop file without needing this if you have the document ID you don’t need the license.

And the call does not make any service request. Everything happens locally.