Supplemental query tables

http://www-01.ibm.com/support/knowledgecenter/SSTLXK_8.5.0/com.ibm.wbpm.bpc.doc/topics/c6bpel_querytables_supplem.html?cp=SSTLXK_8.5.0&lang=en

Supplemental query tables in Business Process Choreographer expose to the query table API business data that is not managed by Business Process Choreographer. With supplemental query tables, this external data can be used with data from the predefined query tables when retrieving BPEL process instance information or human task information.

Supplemental query tables relate to database tables or database views in the Business Process Choreographer database. They are query tables that contain business data that is maintained by customer applications. Supplemental query tables provide information in a composite query table in addition to information that is contained in a predefined query table.

Supplemental query tables have the following properties:

Table 1. Properties of supplemental query tables

Property	Description
Name	The query table name must be unique in a Business Process Choreographer installation. When the query is run, this name is used to identify the query table that is queried. A query table is uniquely identified using its name, which is defined as prefix.name. The maximum length ofprefix.name is 28 characters. The prefix must be different to the reserved prefix 'IBM', for example,'COMPANY.BUS_DATA'. Do not use a digit at the end of the table name. If a table is used multiple times within a query, the name of the table is extended with a number ranging from 0 to 9. For example, CUSTOM_VIEW0, CUSTOM_VIEW1 and so on. If there is already a digit at the end of your table name, Business Process Choreographer will remove this digit, which causes an QueryUnknownTableException.
Database name	The name of the related table or view in the database. Only uppercase letters may be used.
Database schema	The schema of the related table or view in the database. Only uppercase letters can be used. The database schema must be different to the database schema of the Business Process Choreographer database. Nevertheless, the table or view must be accessible with the same JDBC data source that is used to access the Business Process Choreographer database.
Attributes	Attributes of supplemental query tables define the pieces of information that are available for queries. These attributes must match the related name of the columns in the related database table or view. The attributes are defined with a name and a type. The name is defined in uppercase. The type is one of the following types: Boolean: A boolean value Decimal: A floating point number ID: An object ID of 16 bytes in length, such as TKIID of the TASK query table Number: An integer, short, or long String: A string Timestamp: A timestamp
Join	Joins must be defined on supplemental query tables if they are attached in composite query tables. A join defines which attributes are used to correlate information in the supplemental query table with the information in the primary query table. When a join is defined, the source attribute and the target attribute must be of the same type.
Authorization	No authorization is specified for supplemental query tables, therefore, all authenticated users can see the contents.

Parent topic: Query tables in Business Process Choreographer

TechMahendraQuestion

inline human task
supplementary query tables
complemetary query tables
business rules
hibernet
jdbc out bound adapter
api
rest service

Human Task Inline and stand-alone human tasks

Inline and stand-alone human tasks

You can implement a human task as part of the logic of a BPEL process, or independently of other processes.

If the task is implemented within a BPEL process, it is called an inline task. Otherwise, it is referred to as a stand-alone task.

• Stand-alone tasks
  Stand-alone tasks follow the service-oriented architecture (SOA) pattern and they are loosely coupled with the components that invoke them (to-do tasks), or the components that are invoked by them (invocation tasks). They can be wired to another component using the Service Component Architecture (SCA) infrastructure.
• Inline tasks
  Inline tasks are an integral part of the BPEL process. Inline tasks can be to-do tasks, invocation tasks, or administration tasks. Because collaboration tasks rely on the interaction between people and do not directly interact with processes, they cannot be inline tasks. Inline tasks are neither visible as SCA components (cannot be wired), nor are they reusable in other processes or activities.

Human Task

http://www-01.ibm.com/support/knowledgecenter/SSTLXK_8.5.5/com.ibm.wbpm.wid.bpel.doc/topics/chttype.html?cp=SSTLXK_8.5.5&lang=en

Types of human task

There are four types of human tasks that you can define.

To-do task

This is where a service component (such as a business process) assigns a task to a human as something for that person to do.

A to-do task can be implemented either stand-alone or inline.

To see an example of a to-do task that you can build and run yourself, go to http://publib.boulder.ibm.com/bpcsamp/index.html, and clickHuman Task features > To-do task.

Note: You will need a connection to the internet to view this example.

Invocation task

This is where a human can "assign" a task to a service component. In such a case, a human is invoking an automated service such as a business process.

An invocation task can be implemented either stand-alone or inline. When it is inline, an invocation task allows humans to invoke the operations that a business process exposes through activities such as receive, pick or event handlers. Through this, a user can start a process and define authorization for its inbound activities.

To see an example of an invocation task that you can build and run yourself, go to http://publib.boulder.ibm.com/bpcsamp/index.html, and click Human Task features > Invocation task.

Note: You will need a connection to the internet to view this example.

Collaboration task

This is where a human assigns a task to another human.

A collaboration task is stand-alone, in that there is no interaction between it and any other component. It is self-contained and implements a stand-alone human interaction without any reference or interface to another service.

To see an example of a collaboration task that you can build and run yourself, go to http://publib.boulder.ibm.com/bpcsamp/index.html, and click Human Task features > Collaboration task.

Note: You will need a connection to the internet to view this example.

Administration task

This type of task grants a human administrative powers such as the ability to suspend, terminate, restart, force-retry, or force-complete a business process. Administration tasks can be set up on either an invoke activity, or the process as a whole.

This type of task is only available within a business process (inline task).

Parent topic: Human tasks

Related concepts:

Inline and stand-alone human tasks

Task templates

Task instances

Human task clients

Human task user interfaces

Versioning of human tasks

To-do tasks and collaboration tasks with parallel ownership

Lifecycle of a human task

Related tasks:

Setting human task preferences

Improving performance when using human task list widgets