The Document Packages User Group privilege is required to generate Document Packages.
Document Packaging can be created from within the Unity Client. Package generation must be initiated from a document that belongs to a Document Type that has been configured for use with Document Packaging. The document must also belong to a supported File Type. For information on supported File Types, see Supported File Types.
Users can only create packages that contain documents the user has rights to access. If a user attempts to create a package that is configured to include documents that the user does not have rights to access, the package will not be created and an error message will be displayed. The Document Types that correspond to those documents will be logged in the Diagnostics Console.
Package generation can be initiated using:
-
A document included in a document search results list. Depending on your configuration, you may also be able to initiate Package generation from a selection of documents included in a document search results list.
-
An already existing Document Package included in a document search results list
-
An open document
-
The Generate Document Package Workflow action
-
The Application Enabler Generate Document Package context
The Application Enabler license is needed in order to generate Document Packages from an application.
To generate a Document Package from a Document Search Results list, right-click the desired document and select Generate Package.
To generate a Document Package from an open document, click Generate Package in the ribbon menu of the opened document:
Depending on your system's configuration, you may be prompted to select the following:
-
A package template
-
A date range to limit the documents added to the package to documents that fall within the specified range
-
Both a package template and a date range
After package generation has been initiated, the packet may be automatically compiled according to your configuration, or may require manual steps.
Some configurations may completely automate the package generation process and further configuration is not available. In this scenario, packages are indexed and uploaded into OnBase without user intervention. These documents can be viewed by performing regular document retrieval processes.
If your Document Packafe generation is not automated and requires manual intervention, see the following sections on building a Document Packafe: