Browse Prior Art Database

Enhanced Notification

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

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 notification item to be sent to a set of pre-selected persons. It is proposed that the current, rather inflexible, mechanism is extended through the notion of notification handlers, notification activity type, and notification faults.

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

Page 1 of 2

Enhanced Notification Enhanced NotificationEnhanced Notification Enhanced 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 item to be sent to a set of pre -selected persons. For example, if an activity has not been processed within 12 days, processing of the activity is no longer needed. This could, for example, be expressed as follows:

<invoke name="approve"...>

<after 12 days sendNotification to managers/>

</invoke>

    When the activity 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 actions. This notification mechanism has also been proposed for a sphere; that means the notification is specified for a complete sphere .

    It is suggested to introduce the notion of notification handlers similar to event handlers and fault handlers.

This would allow coding the previous example as follows:

<invoke name="approve">

<notification time="12D">

... some activity ...

</notification>

</invoke>

    If the expression in the time attribute evaluates to true, the notification handler gets control and can do whatever is needed to cope with the situation, including executing a <notify> activ...