Using webMethods Content Service Platform Documents in a Process

Designer supports the use of webMethods Content Service Platform (CSP) documents in processes. Both receive tasks that start processes and those that do not start processes can use CSP documents. Message start and signal start events can use CSP documents to start processes. Message and signal intermediate events -- boundary and top-level -- can also use CSP documents.

Important:

User tasks can also use CSP documents. CSP document support in a user task must be added in the task editor, even if the process is CSP driven. For more information about using CSP documents, see the PDF publication Implementing webMethods Content Service Platform for BPM.

Drag and drop an existing CSP sourced IS document from the Package Navigator view onto the process editor to create a message start event pre-configured to use a CSP document. The E-form (For E-form Triggered Processes) check box is automatically selected, and the E-form Template Name field is automatically populated. You must select the E-form Content Repository location. See Selecting a webMethods Content Service Repository.

Drag and drop an existing CSP sourced IS document from the Package Navigator view onto an existing receive task, message / signal start event, or message / signal intermediate event (including boundary events) to configure it to use a CSP document. The E-form (For E-form Triggered Processes) check box is automatically selected, and the E-form Template Name field is automatically populated. You must select the E-form Content Repository (webMethods Content Service Repository) location. See Selecting a webMethods Content Service Repository.

Manually configure an existing receive task, message/signal start event, or message/signal intermediate event (including boundary events) to configure it to use a CSP document. See Configuring CSP Documents in a Process. You must select the E-form (For E-form Triggered Processes) check box. The E-form Template Name field is automatically populated when you select a CSP-sourced IS document as the step's Receive Document. You must select the E-form Content Repository location. See Selecting a webMethods Content Service Repository.

For conceptual and overview information about webMethods Content Service Platform (CSP), as well as information about configuring content repository environments, content filters, and content listeners for your processes, see the PDF publication Implementing webMethods Content Service Platform for BPM.

For information about the features, functions, and operation of the webMethods Content Service Platform core components, including content creation and administration, refer to the CSP HTML help, which can be found in any of these locations:

In the product installation directory: Software AG_directory\CSP\doc

If you have installed the Documentation component with the Software AG Installer: Software AG_directory\_documentation\webMethods\Third-Party\Content_Service_Platform

In the documentation area of the Empower Product Support Web site: http://empower.softwareag.com (login required)

For additional information about working with webMethods Content Service Platform and related suite components, see the following webMethods documentation: