Licensing Clarification: Using DocumentUltimate Alongside FileUltimate

We are currently in the process of integrating FileUltimate 8.x in our application under a valid Enterprise License. We’ve noticed that DocumentUltimate is being installed as a dependency, although we have not actively used it so far. Now we are planning to start using DocumentUltimate package for document view functionality.

If we begin using DocumentUltimate, is it sufficient to use our existing FileUltimate license key, or is a separate license for DocumentUltimate required? (DocumentUltimate Currently shows a water mark when deployed)

As we are nearing the final stages of development, we would greatly appreciate your response ASAP.

Thank You.

Cem Alacayir Replied

Yesterday at 3:36 AM

Employee Post Marked As Answer

FileUltimate uses the same DocumentViewer that comes with DocumentUltimate but there is a license difference in usage.

FileManager of FileUltimate has an integrated DocumentViewer which is opened when you double-click document files (or click Preview action in the context menu). But this DocumentViewer cannot be used standalone, it’s just part of the FileManager.

So FileUltimate has dependencies to our other products for enhancing the FileManager:

Can use the DocumentViewer when DocumentUltimate DLL is available.
Can create image thumbnails/viewers for much more image formats when ImageUltimate DLL is available.
Can create video thumbnails only when VideUltimate DLL is available.

So the usage here is internal and isolated.

But when you need a standalone DocumentViewer which you put in your own host page and pass the document file to display, you will need a DocumentUltimate license. DocumentUltimate also has a DocumentConverter API which you can use even in non-web apps (Console, Winforms etc.).

1 Reply

Reply to Thread

Related Knowledge Base Articles

1 Reply

Reply to Thread

Tags

Related Knowledge Base Articles