Developing a custom Process application involves customizing the way that the application interfaces with user, data, and workflow services.
A custom Process application can be created as any of the following applications:
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:
|
---|---|
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.
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: |
There are two types of work performers:
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.