IBM FileNet P8, Version 5.2.1            

Introduction to Process Applications

Developing a custom Process application involves customizing the way that the application interfaces with user, data, and workflow services.

Specifically, the following aspects of the application might be customized:

A custom Process application can be created as any of the following applications:

Step Processors

A Step Processor is an application that performs the operations that are associated with a step in a workflow. There are two types of Step Processors:
Step Processor This applet or application processes the information and resources a workflow participant needs to complete a step in a workflow. When a workflow participant opens a work item, the Step Processor displays the following items:
  • The instructions
  • The attachments that are stored in object or file stores
  • Current field values
  • Response options
  • Other resources that are necessary to allow the participant to process the step
When you design or customize a Step Processor, you must account for all data and information that is to be provided for this step.
Launch Step Processor A Launch Step Processor is a more specialized type of Step Processor. Because a Launch Step Processor begins a workflow, a typical Launch Step Processor contains all of the information necessary to initialize a workflow. A typical Launch Step Processor is independent of the condition of workflow progress; therefore, you need to consider only what information the Launch Step Processor introduces into the workflow.

For information about Step Processors from the user and administrative perspective, see Use Java™ step processor.

There are two ways of developing a Step Processor or Launch Step Processor: as an HTML Step Processor or as a Java Step Processor application or applet.
HTML Step or Launch Step Processor Developing a custom HTML Step Processor involves using the Web Application Toolkit and/or developing your own JavaServer Pages (JSP) and associated components. For information about developing an HTML Step Processor or Launch Step Processor, see Developing Step Processors. For complete information about the Web Application Toolkit, see Web Application Toolkit.
Java Step Processor You can build a Java Step or Launch Step Processor for deployment as either a Java application or applet. For a discussion of whether to develop your custom Java Step Processor as an application or an applet, see Developing Custom Java Processors - Applications vs. Applets. For complete information on developing a Java Step Processor or Launch Step Processor, see Developing a Java Step Processor. To extend or customize the sample Java Step Processor supplied for the Process development environment, see also the following topics:

Work Performers

A work performer is an application with the following attributes:
  • It performs an operation or set of operations that are associated with a workflow step.
  • It does not require a user interface.
Here are some typical work performer operations:
  • Logging in to and establishing a workflow system session
  • Polling a work queue (to find operations that are related to a workflow step)
  • Locking the retrieved object
  • Processing the work (such as performing updates of data, and saving)
  • Cycling back to queue polling
For more information, see Developing Work Performers.

There are two types of work performers:

User Inbox

A User Inbox is typically an HTML page or Java applet that provides the user (workflow participant or Process Tracker) with notifications for work items. In Workplace, the page displays when you click the Tasks tab in a User Inbox. The notifications in the User Inbox include information and associated attachments that are provided from a user or work queue.

For overview information about developing a custom User Inbox as either an HTML page or a Java applet, see Developing User Inboxes: an Overview.



Last updated: March 2016
dev_custom_app_overview.htm

© Copyright IBM Corporation 2016.