Legacy Issue Number: 15040
Source: Intalio, Inc. ( Tammo van Lessen)
Currently, a Business Rule Task has only an "implementation" attribute that is used to identify the technology used to interact/communicate with a rule engine (e.g. Web Service or any other protocol).
However, there is no possibility to identify to which rule engine the data should be sent nor which rule set should be processed. I believe that this information is crucial from a vendor perspective.
My suggestion is to add an anyURI-attribute called "ruleSet" (perhaps there is more generic term). The attribute's value can be resolved at runtime/deployment time by BPMS to identify both, rule engine and ruleset or other rule engine specific settings.
Reported: BPMN 2.0b1 — Sat, 1 Aug 2009 04:00 GMT
Disposition: Closed; No Change — BPMN 2.0
Since the business rule task is underspecified, vendor specific extensions are needed anyway. So there is no real value in adding any additional attribute, since
interoperability will not be possible.
Disposition: Closed, No Change
Updated: Fri, 6 Mar 2015 20:57 GMT
BPMN2 — Add an attribute that can identify a rulebase/rule engine for Business Rule Task
- Key: BPMN2-248
- OMG Task Force: BPMN 2.0 FTF