Browse Prior Art Database

Dynamic Notification

IP.com Disclosure Number: IPCOM000130023D
Original Publication Date: 2005-Oct-11
Included in the Prior Art Database: 2005-Oct-11
Document File: 2 page(s) / 6K

Publishing Venue

IBM

Abstract

Flow languages, such as Business Process Execution Language for Web Services (BPEL4WS), provide for the definition of business processes. They typically support the notion of notification: An activity or scope is assigned a time interval that when exceeded causes a specified person to be notified. The disadvantage of the current state-of-the-art expiration support is its inflexibility; notification is always the same whether it is a high value process or a low value process, whether it is an urgent process or a non-urgent process; that means expiration is context independent. Furthermore the appropriate notification condition and notification destination can not be changed. Two new mechanisms are provided for these new capabilities.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 2

Dynamic Notification Dynamic NotificationDynamic Notification Dynamic Notification

    Flow languages, such as Business Process Execution Language for Web Services (BPEL4WS), provide for the definition of business processes . They typically support the notion of notification: An activity or scope is assigned a time interval that when exceeded causes a notification to be send to a designated person. For example, if an activity has not been completed within 12 days, the manager of the employee to whom the task was assigned is notified . This could, for example, be expressed as follows:

<invoke name="approve"...>

<after 12 days sendNotification to managers/>

</invoke>

    When the activity "approve" has not been completed within 12 days, a notification work item is created for the managers of the individuals to which the activity has been assigned. This allows the notified person(s) to take appropriate actins. This notification mechanism has also been proposed for a scope; that means the notification is specified for a complete scope .

    The disadvantage of the current state-of-the-art notification support is its inflexibility; notification is always the same whether it is a high value or low value process, whether it is an urgent or non-urgent process; that means notification is context independent. Furthermore neither the notification condition nor the notification destination can be changed.

Two new mechanisms are needed to provide the desired capabilities .

    First, it is suggested to address the context issue by...