filenet

You should not expect that the exported process will be ready to run in FileNet.

Data types are mapped as closely as possible, but a few data types in Modeler are not supported in FileNet, as shown in Table 1.

For the case of a human task, the roles and resources defined in Modeler are mapped into the equivalent constructs in FileNet.

A local process is transformed into a submap within the workflow process created for FileNet.

The BSM is integrated with a simple FileNet P8 workflow, which manages documents associated with the loan application.

The goal is to provide you with insight on how you can leverage different parts of IBM FileNet P8 to produce similar solutions.

The management of the lifecycle is embedded in the FileNet BPM process that automates processing the case from the New to the Closed state.

In this way, the FileNet process acts in the same manner as a while loop, even though loops are not supported.

Therefore, elements in the process model need to be transformed into the closest matching element in FileNet.

In the format list, two parsers can be selected: PDF and FileNet Select the PDF parser for PDF conversion.

An individual resource requirement in Modeler maps to a participant in FileNet.

Annotations are mapped to text annotations in FileNet, shown in Figure 11.

Each repository you create will correspond with a data field in FileNet.

For this reason, processes for export to FileNet cannot use business items on the connector between tasks.

FileNet processes begin with a single launch step activity.

In FileNet, routing information is part of a step.

The connection between tasks is mapped to a route in FileNet.

FileNet P8 provides support for document-centric business processes (workflows).

When the loan applicant submits the document to the FileNet server, a FileNet process is invoked.

Global repositories are not supported in FileNet Business Process Manager mode; you must always use local repositories.

In local processes or loops, stop nodes are ignored when exporting to FileNet.

After completing the form, the field specialist updates the document in FileNet P8 and completes the task.

The terminology and technical descriptions within this article assume you are familiar with IBM FileNet P8.

Figure 3 shows a loan application form template that you create in the FileNet P8 eForms Designer.

If a local human task is used, the primary owner for the task maps to a FileNet participant for the step.

As for the data itself, not every data type that is available in Modeler has an equivalent in FileNet.

So in order to model cases in IBM FileNet, the sample asset uses a CaseFolder class definition.

This entire sample was developed using only existing software components from the IBM FileNet P8 suite

The Work Data eForm widget displays a FileNet eForm user interface to enter data for a new work item. In order to use the widget