BPMN 2.0 FTF Avatar
  1. OMG Issue

BPMN2 — Allow referencing scripts instead of enfocing inline specification

  • Key: BPMN2-274
  • Legacy Issue Number: 15103
  • Status: closed  
  • Source: University of Stuttgart - ISW ( Frank Leymann)
  • Summary:

    Use Case: When using BPMN 2.0 in systems management environments many tasks will be implemented as scripts. Especially, a huge amount of scripts already exist in these environments and BPMN 2.0 should support an easy and straightforward way to allow making use of them as script activity implementations.

    Issue: Scripts to be performed must be copied to the already defined @script attribute to make it inline to the script task. In practice, this is not only redundant but also introduces a lot of potential consistency problems because the proper script might be subject to change; in that case, all copies in all script tasks must be found and adapted accordingly.

    Prososed resolution: Add a new attribute @scriptRef (of type URI or QName) to the scriptTask element. This allows to point to the script to be executed.

    Minor comments: There is no need to introduce the script separately as an operation of some (artificial) interface. This should be clarified.

    The script task refers to a NONE task which has been renamed into Abstract Task: needs to be fixed.

    An associated document (BPMN Script Invocation.DOCX) with more background has been sent to Tammo van Lessen

  • Reported: BPMN 2.0b1 — Tue, 2 Mar 2010 05:00 GMT
  • Disposition: Resolved — BPMN 2.0
  • Disposition Summary:

    The functionality proposed is provided by other means.
    Disposition: Closed, No Change

  • Updated: Fri, 6 Mar 2015 20:57 GMT