CustomObject Class

CustomObject Class:

A custom object is used to store and manage data that does not have content (and thus doesn’t support versioning) or a lifecycle. For example, a customer might be represented in the object store as a custom object because there is no requirement for content. Custom objects:

• Have system properties that the system manages automatically, such as Date Created.
• Can have custom properties for storing business-related metadata.
• Are secured.
• Can participate in business processes as workflow attachments.
• Can generate server events when they are created, modified, or deleted. These events are then used to customize behavior.

Folder Class

Folder Class

A folder is a container that is used to group other objects. Folders are the primary mechanism through which users access documents. Users typically think of folders as a place where documents are stored;, however, filing documents in multiple folders does not create extra copies of those documents, but rather creates a logical association between the folder and the document. Folders:

• Have system properties that the system manages automatically, such as Date Created.
• Can have custom properties for storing business-related metadata.
• Are secured.
• Are hierarchical, in the sense that a folder can have subfolders.
• Can contain documents and custom objects.
• Can generate server events when they are created, modified, or deleted. These events are then used to customize behavior.
• Can be annotated.

Document Class

Document Class

Most users think of a document as a file they create with an application such as Word. The user stores the document in the document management system so that a history of changes to the document is maintained and the document can be easily found and edited. Users who design enterprise content management applications and those who manage them will need to understand how documents can be leveraged to support a variety of application needs. A document might be used to maintain a traditional electronic file as well as other types of data, such as an XML document or content that is managed in an external repository. Documents:

• Have system properties that the system manages automatically, such as Date Created.
• Can have custom properties for storing business-related metadata about the document.
• Are secured.
• Can have content that can be indexed for searching.
• Can point to content that is outside of the object store (external content).
• Can have no content (metadata only).
• Can be versioned to maintain a history of the content over time.
• Can be filed in folders.
• Can have a lifecycle.
• Can participate in business processes as workflow attachments.
• Can generate server events when they are created, modified, or deleted. These events are then used to customize behavior.
• Can be rendered to different formats, such as PDF and HTML.
• Can be published to a Web site.
• Can be annotated.
• Can be audited.

Roster vs Queue in PE

Roster vs Queue:

Queue: by using queue we can search the work items which are presented in that specific Queue only
 
Roster: by using roster we can search the work item across all the queues. it means if we select the roster in our search criteria, the system will search for the work item in all the queues.

A roster is a database structure that holds all the active workflow elements (workflows and all work items, whatever their location), whereas a queue is a structure that only contains work items maintained there while they await processing.

The Roster is a file containing a reference to all work items in a workflow. A Queue is a file containing a reference to a subset of the work items in a workflow. Queues are typically used to assign security to control access. 

Milestones and Deadlines

Milestones : Milestones are defined as key notification points in a business process. These are points at which participants need to receive a message describing an important task or tasks that are pending or completed

Deadlines : Deadlines are time-based constraints that can be applied to steps in a business process. A step with a deadline implies that the participant must complete the step within a specified amount of time. The specified time (the deadline) is relative to the time that the step starts (when the participant receives the work packet).

Isolated regions,Queues, Roster and Event logs

Isolated region : An isolated region is a logical subdivision of the Process Engine database. An isolated region consists of queues, rosters, and event logs

Roster: A roster is a database structure that stores the current location and other information about a work item. Process rosters provide the Process Engine software with an efficient way to locate a specific work item

Event Logs : An event log is a database structure that contains information about system-level events related to work item processing.

Queues: A queue is a database structure that holds work items

4 different types of queues are available in PE

A user queue is a queue that holds work items waiting to be processed by a specific user.

A work queue is a queue holding work items that can be completed by one of a number of users, rather than by a specific participant, or work items that can be completed by an automated process.

System queues are queues holding work items that are undergoing or waiting for processing by the Process Engine server

Component queue holds work items to be processed by component step in workflow. The components steps are to process a work item using an external component.

Component Integrator

Component Integrator : The Component Integrator is used to integrate Java or Java Message Service (JMS) components for use in processes. Components are registered in the Process Configuration Console to make them available in Process Designer.

Maps, Routes and Steps in Work Flow

Maps, Routes and Steps in Work Flow

Maps:  A map represents the sequences of steps and routes required to complete a process.

Routes: Routes define the order of execution for a series of steps based on specific rules (using workflow data fields) and user responses (Approve and Deny as examples). You can specify to always take a route or to only take the route when a condition is met.

-- Single (linear) routing
-- Conditional routing
-- Parallel routing

Steps: Steps represent specific business or system activities. Activities can be performed by an individual user (the participant), by a group of users, or by an automated application

There are several types of steps:
       
Launch step: The first step in a process. Every process has this step.
       
General step: Represents a general activity to be processed by a participant (or a group of users), or an automated process. It can be categorized as follows:
       
Participant step: A step that has an associated participant or a group of users, all of whom must process the work item to complete the step. The identity of these users can be defined at runtime through the use of groups.
       
Work queue step: A step that is assigned to a work queue (see definition below) instead of a specific participant.
     
Unassigned step: A step that has no effect in the process and can be used for routing or documentation purposes.

System step: Represents one or more functions to be performed by the system. For example, a system step might include assigning data field values, creating a new process instance, or suspending a process for a specified period of time.

Submap step: Calls another map in the current process definition.
      
Component step: Performs operations in an external application or system.It is accomplished by IBM FileNet Business Process Manager’s Component Integrator.
      
Web services step: Invokes or implements Web services. IBM FileNet Business Process Manager uses Web services to integrate to external applications and services.

Process design and Process definition

Process design: Process design starts by identifying the activities and the order in which those activities must be performed to accomplish the business process.

Process definition: A process definition describes the activities and resources required to accomplish a business process. It consists of a directed graph, with a series of process activities or steps (nodes) connected together by a series of routes (arcs), which define the sequence in which the steps are executed. Steps and routes are organized into reusable maps

There can be multiple process definitions per business process to support multiple versions. Process definitions can also inherit from other process definitions. Inheritance allows organizations to specialize processes to create consistency across a set of related processes. The process definitions are stored in the IBM FileNet P8 Content Engine repository.

Workflow, Workflow Definitions and Work Item

Workflow: Workflow is a structured way of performing tasks by an individual or a team.
 
Examples of workflow include auto insurance claims that require the efforts of multiple people to process. The workflow process involves a policy holder filing a claim, a field agent processing the claim, an adjustor adjusting the claim amount, and finally the claimant either receiving the claim amount or the claim being rejected.

Workflow Definition : A workflow definition consists of workflow properties and workflow maps. A workflow map consists of two or more steps. To create a workflow map, you define the steps that are involved in a workflow process and the routes that specify the sequence of the steps.

Work Item : A work item is a single unit of work composed of a collection of fields. Work items transverse the process map, moving the data required by the process from step to step as indicted by the map.