Skip to main content

FileNet Workflows

Creating Workflows

Claim Filing & Processing

The following workflow was demonstrated and then subsequently recreated and tested in Traveler's environment. It is a sample workflow for processing a claim application. We expanded on this by triggering it via a document upload using a subscription created in the acce console, which we will also mark as an initiating attachment to automatically include it in the triggered workflow (see below).

Workflow preview:

Workflow download:

ClaimApplication.pep.zip

Using Web Services

  • In order to enable pasting wsdl partner links, navigate to View -> Configuration:

  • Right click on the connection point and click Properties...:

  • Under Web Services, check Enable Process Designer to enter WSDL links without browsing for Web services:

  • Now you can paste links in Workflow Properties under Web Services in the Partner Links section:

  • Next, open up the Palette Menu and check Web Services Palette:

  • Now you can drag in Invoke and select the created Partner Link as well as the desired Operation:

note

For web services that require SSL (ex. https://...), you must add a secret containing the certificate to the trusted_certificate_list in the CR.

Initiating Attachments

Initiating attachments are attachments to Workflows that automatically get incorporated into them on upload, via a Subscription that triggers a workflow on Document Creation.

Creating a Subclass (optional)

If desired, you can create a subclass of an exisitng one to use as a more specific type. This can provide finer granularity when, for example, triggering workflows.

  • Within the acce console, navigte to your choice of object store, go to Classes under Data Design and double click on a class you would like to form a subclass for. Next, click on Actions and New Class:

  • Enter a name and description:

  • Click Finish:

Creating the Subscription

  • In the acce console under your choice of object store, navigate to Events, Actions, Processes and then to Subscriptions:

  • Click New and enter a name and description:

  • Specify the class (and optionally subclass) you would like to subscribe to:

  • Check Create a workflow subscription to allow this subscription to trigger a workflow:

  • Select the events you would like to trigger the workflow. Creation of a document signifies a document upload:

  • Specify which Workflow you would like this subscription to trigger:

  • Optionally map properties from the uploaded document (Property name) to the Workflow (Data field name):

  • Ensure the subscription is enabled and if you would like, include subclasses:

  • Review the details and click Finish:

Workflow Init Attachment

  • Under Workflow Properties in the Attachments tab, create an attachment by double clicking under the Name field, typing a name and pressing Enter:

  • On the right sidebar, mark this as the Initiating attachment by clicking the following icon, which should then appear left of the attachment name:

           

  • From the palette menu, drag in a component node:

  • Configure this component by selecting an operation to extract information from the uploaded attachment, such as its given title, for example, which corresponds to symbolicPropName:

This then populates the return value, which can be used elsewhere in the Workflow as desired.