PDF/A Compliance Module
for SharePoint and other platforms

Everything a compliance solution needs to do, ready-to-use.

Whether you need to archive everything in SharePoint or content stored in many different systems, the Hyper.Net Compliance Module provides you with a plug-and-play solution for what is otherwise a challenging problem. You get a comprehensive feature set that addresses every area of the content lifecycle:

 

  • Supports all input formats. Every document and image type—even PDF and PDFA files—is transformed into a valid PDFA (or PDF or TIF if preferred) file.
  • Automatic archive routing. All resulting archive files are automatically published into the designated repository or routed to an external archiving system. Metadata is available during the routing process and can be used not only to control the routing process but also included in the package to be archived.
  • Automated watermarking. Configurable watermarking templates allow you to vary watermarks by document type, division or any other criteria.
  • Metadata stamping. Stamp any desired metadata onto every page of the resulting archive file in any desired location. Stamped values may also be computed on the fly from metadata and/or any external values. 
  • Document compounding. Combine documents related by a common metadata value or compound entire folder hierarchies and publish them into a single, watermarked PDFA file with an internal table of contents and stamped metadata.
  • Load balancing and failover. In high-volume situations, the conversion and publication processes are distributed across CPUs, servers and server pools to ensure maximum speed and greatest efficiency. And if one server goes down, the workload is automatically re-distributed across the remaining servers without human interaction.
  • Extremely high processing speed. Multi-threaded processes ensure maximal parallelism and superior speed. Traditional PDFA conversion solutions can't even come close.

 

General Highlights   Extra highlights for organizations with SharePoint   How it works
  • Any document or content storage facility can initiate the PDFA archiving process using a simple XML call to the Hyper.Net Web Service—the call can be made at any desired point in the content lifecycle or business workflow
  • Any application containing data that is relevant to archive can use the same interface to archive its data—even if the data is not in document form, for example database tables, lists or text
  • Completed PDFA files are automatically transported to the archive along with all corresponding metadata into the target output database (SharePoint shadow libraries or page libraries, Lotus Notes NSF databases, file systems, SQL databases and any archiving system)
  • Document metadata can be used to control the conversion and routing processes
  • Routing of the resulting PDFA package can be synchronous or asynchronous with respect to the initiating process
  • Documents to be compounded into a single PDFA file may be of different types and page orientations
  • All documents found in a folder to be archived are compounded in the required sequence regardless of document type. The resulting compound PDFA file is structured internally to correspond with the archived folder hierarchy and is complete with a table of contents and page numbering. Ideal for records management and for assembling project or meeting materials!
  • The archiving process can be configured as desired with extra steps to accomplish any required transformation or routing
  • Can be configured to output PDF or TIF files instead of PDFA files
     
  
  • Automatic initiation via SharePoint document management events or programmatically from any desired point in the document workflow
  • PDFA files can be routed back into SharePoint shadow libraries, SharePoint page libraries or placed on SharePoint lists
  • SharePoint documents containing only metadata as well as SharePoint lists can also be archived
  • Works seamlessly and transparently with SharePoint review and approval processes— versions are converted to PDFA and routed to the archive upon approval
  • Configured document compounding takes place automatically when documents to be compounded are changed
  • An on-demand archiving function is included to support manually initiated requests
  
  • The archiving process is initiated automatically from a workflow action, event sync or both
  • Every document to be included in the final PDFA is converted into an staging PDF (when compounding, multiple documents will be converted)
  • All staging PDFs are combined in the required sequence into one compound PDF (when compounding)
  • Metadata is extracted and if desired calculated, then stamped onto every page in the staging PDF in the configured location
  • Watermarking is applied to the staging PDF
  • The staging PDF is now transformed into a valid PDFA
  • The final PDFA is sent synchronously or asynchronously to the target repository