The Message Start Event in Context

6-10 Modeling and Implementation Guide for Oracle Business Process Management Figure 6–11 shows the default notation for the error end event. Figure 6–11 The Error End Event The error end event is represented by two concentric circles with a lightning bolt in the middle. For information implementing the error end event, see the Oracle Fusion Middleware Modeling and Implementation Guide for Oracle Business Process Management.

6.2.8 Introduction to the Message End Event

The message end event is used to send a message to another process or service when the process is completed. The message end event is always used with either a message start event or message catch event. Figure 6–12 shows the default notation for the message end event. Figure 6–12 The Message End Event The message end event is represented by single circle with a yellow envelope in the middle. For information on how implement message throw events, see Communicating With Other BPMN Processes and Services Using Message Events in the Oracle Fusion Middleware Modeling and Implementation Guide for Oracle Business Process Management.

6.2.9 Introduction to the Terminate End Event

The terminate end event is used to immediately terminate a process. When a terminate end event is reached, the process ends immediately. There is no error handling or additional clean up performed.

6.3 Adding User Interaction to Your Process

Most business applications require interaction from process participants within your organization. This interaction can be as simple as entering information into a form or can involve multiple work flows and multiple users. This section describes the BPMN flow objects that are used to model how process participants interact with your business processes. Note: When creating a process that has multiple end events, you must ensure that any tokens that reach a message end event were created by a message start. For example, you cannot use a message end event to end a process instance initiated by a timer start. Modeling Business Processes with Oracle BPM 6-11

6.3.1 Introduction to Human Workflow

Many end-to-end business processes require human interactions with the process. For example, humans may be needed for approvals, exception management, or performing activities required to advance the business process. Oracle Human Workflow provides comprehensive support for human participation by providing the following features: ■ Human interactions with processes, including assignment and routing of tasks to the correct users or groups ■ Deadlines, escalations, notifications, and other features required for ensuring the timely performance of a task human activity ■ Organization, filtering, prioritization, and other features required for process participants to productively perform their tasks ■ Reports, reassignments, load balancing, and other features required by supervisors and business owners to manage the performance of tasks For more information see the Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.

6.3.1.1 Introduction to Human Tasks

Human Tasks are a component of Oracle Human Workflow. Human tasks enable you to interleave human interactions with connectivity to systems and services within an end-to-end process flow. Human tasks are responsible for handling all interactions with users or groups participating in the business process. They do this by creating and tracking tasks for the appropriate users in the organization. Users typically access tasks through a variety of clients, including the worklist application, E-mail, portals, or custom applications. Human tasks enable process developers to define how process participants interact with process-based applications created using the Oracle BPM and SOA suites. Using Human Tasks, process developers can define the interface and workflow for end-user interaction by creating the following: Human Tasks are reusable services that can be used within other processes that require the same UI. ■ Roles and assignments ■ Deadlines and escalations ■ Presentations Human tasks are created using Oracle BPM Studio.

6.3.2 Introduction to The User Task

The user task represents a part of your process where a process participant is required to perform work. This can be a simple interaction, such as entering a form, or part of a more complicated workflow that requires input from multiple process participants. Figure 6–13 shows the default notation for the user task. Note: In Business Process Composer, human tasks can be used in projects and project templates created in BPM Studio. You cannot create or edit Human Tasks in Business Process Composer.