Breadcrumbs

Scope of delivery

The scope of delivery for signoSign/Universal consists of a ZIP archive containing the current components from the table. The individual components are described in more detail in the following sections.

Component

File

signoSign/Universal Viewer
signoSign/Universal Document Pool

signoSignUniversal.war



Migration tool

migration-tool-[version].jar


signoSign/Universal Viewer

The signoSign/Universal Viewer is the core of signoSign/Universal. It contains all the components that are technically necessary for displaying, editing and signing PDF documents. Signature capture is simple, secure and ISO compliant.

In addition to the supplied ‘Document Pool’ application, it is also possible to provide documents for signoSign/Universal that originate from an existing (web) application at the customer. These documents are accessed or transferred via the signoSign/Universal REST API.

signoSign/Universal Document Pool

The Document Pool is an optional web application that can manage documents and edit them with the Viewer. Document Pool makes documents available to the Viewer for editing.

Document Pool allows the user to upload, delete, download and, above all, display and edit user-specific documents in the signoSign/Universal Viewer. Documents can also be shared with external users (sharing cases).

Login ensures that all users are separated from one another, which means that each user can compile their own document collection. Users with the role "ssu-admin" see all documents and processes of all users after logging in.

If an existing (web) application is to be used with signoSign/Universal, a specific implementation via the REST API is required to access the corresponding documents.

Migration tool

The migration tool is used for minor updates (e.g. from version 3.1.0 to 3.2.0) of signoSign/Universal to prepare the existing database schema for the new version. It carries out all necessary structural adjustments, such as creating additional tables or adding new columns. This ensures that the application remains compatible with the updated schema after the update.

For more information on using the migration tool, see the section Migration.