Controlled Print - tsgrp/HPI GitHub Wiki

This page overviews setting up controlled print in OCMS.

Repository Setup

Documentum

Types

Ensure that the latest dar is deployed to the target repository. The following types should exist:

  • ocms_autonumber
  • ocms_ctrl_print_audit

Folders

Two repository folders are required:

  • Temp folder - temporarily stores the combined PDF in the repository.
    • Example location: /hpi/Controlled Print/Temp
    • Anyone with access to execute a controlled print should have DELETE access.
  • Audit storage folder - folder where controlled print audit objects are stored
    • Example location: /hpi/Controlled Print/Audit
    • Anyone with access to execute a controlled print should have WRITE access

Autonumber

Create an autonumber object to hold the next controlled print number. This object can be called anything, but in the default configuration, it is called controlledPrintAutonumber. Set the current_number attribute to the next number. The interface will 0-pad this value. So, for example, if you set the attribute to 1, the next controlled print whill have a controlled_print_id of 000001.

Other Repositories

Note - as of the 3.2 release, other repositories are supported upon client request.

OCMS Configuration

  • OTC: Add the Controlled Print Audit object type
  • Form Config: Add a form to create a controlled print audit object. This is up to your project, but here are some example settings:
    • Controlled Print Reference Number (required) - typically a freeform textbox since this value is usually generated in another system
    • Controlled Print Requestor (required) - could be a picklist or freeform textbox
    • Print Comments (optional) - ask the user to comment on the print reason
  • Target Type's Search Config: Add the controlled print action to the group actions section of your target type to controlled print. Note, once #1912 is fixed, add a duplicate action to the search results action area for the target types as well.
    • Choose the audit form you configured in the prior step
    • Enter the appropriate folder paths based on the folders set up in the repository
  • Trac Config (optional) - add a new trac to give (certain?) users the ability to search and view controlled print audit events. See Release1 and Edge1 environments for an example.