Configuring Watched Folder for PDF Generator

Posted on December 1, 2011 by jefyoung | Comments (0)

To configure a watched folder in the Admin Console for PDF Generator:

  1. Create a folder to be your watched folder on your filesystem
  2. Login to the ADEP Admin Console (http://[servername]:[portnumber]/adminui/)
  3. Navigate to Services > PDF Generator
  4. Click On Sources
  5. Category=PDF Generator, Click Filter
  6. Click on ‘GeneratePDFService: 1.0 ‘ [Documentation on GeneratePDFService]
  7. In the ‘End Points’ tab, choose ‘WatchedFolder’ from the dropdownlist
  8. Click ‘Add’ (Resource: Description of Watched Folder End Point properties)
  9. For ‘Description’, type something to the effect of “Watched Folder Endpoint PDFG”
  10. In ‘Enter path for the watched folder’, type in the fully qualified path to the folder you created in Step 1
  11. In the Operation Field, select CreatePDF2 from dropdown
  12. In the ‘Input Parameter Mappings’ section, for the ‘inputDocument’ field, select variable, type *.* (this will allow all supported input type files)
  13. In the ‘Output Parameter Mappings’ section, for the ‘Output PDF Document’ field, type %F%E.pdf (this will inherit the input filename and extension and append the .pdf extension.
  14. Click the Add button to save the changes.
  15. Navigate to the Watched Folder you created in Step 1, you should now see new directories: /input, /result, /staged, /failed, /preserve
  16. Test by copying a Word document to the /input folder. It should disappear a few seconds later
  17. If successful, the generated PDF will appear in /result directory. If it failed, the document and reason for failure appear in the /failed directory

Making LiveCycle Workspace Tasks Only Visible to Specific Users/Groups

Posted on December 1, 2011 by jefyoung | Comments (0)

If you want to make a Workspace task only visible to specific groups, you have to specify who can Invoke the task through the AdminUI.

Prior to setting this up, be sure that you have already set up the groups you will need in order to lock down tasks to specific users and groups. Also be sure that all the users that need to invoke processes through workspace are given the Workspace User Role.

  1. Login into Admin Console http[s]://[server]:[port]/adminui
  2. Services>Applications and Services>Service Management
  3. Click the category dropdown, choose the category your process belongs to, and click filter.
  4. Locate the Process you wish to lock down and click the name of theProcess
  5. Click security tab
  6. Click Add Principal
  7. Choose User/Group in the “In” dropdown and click filter
  8. Click on User or Group you wish to add
  9. Check INVOKE_PERM
  10. Click Add
  11. Test by logging into Workspace as a user that should be able to invoke a task, task card should be visible.
  12. Then log into Workspace as a user that should not be able to invoke a task, the task card should not be visible.

Repeat steps 6-10 for each user/group
Repeat steps 4-10 for each process

Note: If a user has the Contentspace User or an Administrator role, they may be able invoke most tasks