Skip navigation FileNet logo
Glossary  |  Help Directory  
  Help for Process Engine Reference  
  Search  |  Index  
Concepts
  About attachments
  About the Component Integrator
  About launching a workflow
  About milestones
  About operations
About the RMI registry
About rosters
About routing
About rules
  About security
  About security queues
  About step processors
  About step states
  About system maps
  About transfer
  About workflow fields
  About workflow maps
  About workflow participants
  Component queue security issues
  Content Engine (CE) operations
  Coordinate information
  Custom web applications
  Eliminating port 32771 conflicts
  Java Runtime Environment (JRE)
  Maximum index key size
  Naming conventions
  System fields
  Troubleshooting
  Wildcards
  Workflow database field size limitations
  Workflow exceptions
Events & Statistics
Expressions
Procedures
  
   

Using Content Engine (CE) operations in a workflow definition (Workplace only)

NOTE CE operations are not available for use with FileNet Web Services Client or Open Client.

To facilitate manipulation of documents in an object store, FileNet uses the Component Integrator infrastructure to provide Content Engine (CE) operations that can be used in a workflow in component steps.

Operations are:

  • File a document in an object store folder
  • Unfile a document from an object store folder
  • Publish a document using a publishing template
  • Get property values of a document or folder (integer, double, date, Boolean, string)
  • Set property value of a document or folder (integer, double, date, Boolean, string)

To use CE operations, it is important to understand the properties of documents in an object store. Each document in an object store has a set of properties defined by the system, such as the display name (the name of the document), the creator, the date last modified, and so on. In addition, each document is associated with a particular document class that usually defines additional properties specific to that type of document. For example, an Expense Report document class might have the property DepartmentNumber that would be specified for expense report documents when they are filed in the object store.

The following examples outline the steps for using CE operations in a workflow definition.

Example 1: File a document based on a response in a previous step.

Example 2: File a document based on the value of a specified document property.

For information on making Content Engine operations available for workflow definitions, see Enable CE_Operations in the Process Configuration Console online help.