• XPDL 2.1 Proposals

Activity Auditing

|Please note: this is a preliminary proposal for XPDL 2.1 which has not yet been adopted by the coalition. Please use this page for discussion of that proposed extension. This proposal may change substantially before adoption, or may possibly never be officially adopted in this form.

The 'Auditing' in this instance means the auditing of events that occur within the lifecycle of an task / event activity (probably not gateway?).

For instance, nominally a process engine will perform some basic activity trace-logging on a process instance as it works thru the process.

The new Activity/Audit element allows the user to specify audit-related expressions to be performed by the process engine when certain events occur.

Currently the proposed enumeration of Auditable event types are (being the main business-applicable events on a task)...

• Initiated
• Completed
• DeadlineExpired
• Cancelled

See attached document "XPDL Proposal User Task Scripts and Activity Audit.doc" for more details and schema definitions.

Discussion from October 11 (WfMC Paris)

We felt that XPDL should focus on persisting design time information. The audit information proposed relates to run time information and implies execution semantics in form of an activity state model. A more elegant solution for this is to update the audit event specification to contain a reference to an XPDL package element, this way a BAM system can perform the association between an audit event and the underlying process model.