• XPDL 2.1 Proposals

User Task Scripts

|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 addition of a new UserTaskScripts element to TaskUser is proposed. This allows the specification of scripts that are to be executed in the user task client application environment. \\ \\ This fulfills a need not normally supported via BPMN (which only allows the specification of Script Tasks, which nominally will be executed in the process engine environment).\\ \\ See attached document "XPDL Proposal User Task Scripts and Activity Audit.doc" for more details.

Notes from Oct 11 Meeting (WfMC Paris)

While there have been many calls for script element in the past, there are serious problems. When one tool defines the script, no other tool will be able to use it. If the nature of the data being carried is such that no other tool will be able to use it, then an Extended Attribute is sufficient.

We discussed the possibility that the user might use one tool, write a script to do something, and even though it can not execute in another tool, the process designer at least can see that there is a script, and can manually transform that script from one form to another. If the script is in an extended attribute, then it is completely invisible to the other tools. There is some value in being visible.

Decided to pull this out of 2.1 release, and consider in future.