[#PETALSSEFLOWABLE-48] Allow to use the message content of an IntermediateCatchEvent - Petals Link JIRA

Details

Type: Improvement Request
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 1.1.1
Fix Version/s: 1.1.2
Component/s: Service engine
Security Level: Public

Description:

Hide

In BPMN, intermediate catch event we provide has a message ref.

<intermediateCatchEvent id="attenteSolde" name="">
    <messageEventDefinition messageRef="process:subventionSoldeeMessage"/>
</intermediateCatchEvent>

The reception of the message does not allow to use then its contents in the BPMN process.

The class IntermediateMessageCatchEventOperation, method doExecute(line 150) makes it possible to signal the event to the flowable process but does not provide a variable.

the method messageEventReceived allows to provide variables (the payload of the event is present in doExecute method).

The configuration could be done in the description of the operation in the WSDL as for the start event:
Example

<wsdl:operation name="estInstruite">
	<soap:operation soapAction="http://ns" style="document"/>
	<flowable:operation processDefinitionId="processID" action="intermediateMessageCatch" message-event-name="eventMessageName"/>
	<flowable:processInstanceId>/*[local-name()='root']/*[local-name()='process-instance-id-callback']</flowable:processInstanceId>
	<flowable:variable name="v1">/*[local-name()='traiter']/*[local-name()='root']/*[local-name()='v1']</flowable:variable>
	<flowable:variable name="v2">/*[local-name()='traiter']/*[local-name()='root']/*[local-name()='v2']</flowable:variable>
	<flowable:variable name="v3">/*[local-name()='traiter']/*[local-name()='root']/*[local-name()='v3']</flowable:variable>
	<wsdl:input>
		<soap:body use="literal" />
	</wsdl:input>
</wsdl:operation>

In BPMN the variables ${v1}, ${v2} an ${v3} are usable after event are received.

Thank

Show

In BPMN, intermediate catch event we provide has a message ref.

<intermediateCatchEvent id="attenteSolde" name="">
    <messageEventDefinition messageRef="process:subventionSoldeeMessage"/>
</intermediateCatchEvent>

The reception of the message does not allow to use then its contents in the BPMN process. The class IntermediateMessageCatchEventOperation, method doExecute(line 150) makes it possible to signal the event to the flowable process but does not provide a variable. the method messageEventReceived allows to provide variables (the payload of the event is present in doExecute method). The configuration could be done in the description of the operation in the WSDL as for the start event: Example

<wsdl:operation name="estInstruite">
	<soap:operation soapAction="http://ns" style="document"/>
	<flowable:operation processDefinitionId="processID" action="intermediateMessageCatch" message-event-name="eventMessageName"/>
	<flowable:processInstanceId>/*[local-name()='root']/*[local-name()='process-instance-id-callback']</flowable:processInstanceId>
	<flowable:variable name="v1">/*[local-name()='traiter']/*[local-name()='root']/*[local-name()='v1']</flowable:variable>
	<flowable:variable name="v2">/*[local-name()='traiter']/*[local-name()='root']/*[local-name()='v2']</flowable:variable>
	<flowable:variable name="v3">/*[local-name()='traiter']/*[local-name()='root']/*[local-name()='v3']</flowable:variable>
	<wsdl:input>
		<soap:body use="literal" />
	</wsdl:input>
</wsdl:operation>

In BPMN the variables ${v1}, ${v2} an ${v3} are usable after event are received. Thank

Environment:

petals 5.2.0, se-flowable 1.1.1

Activity

Ascending order - Click to sort in descending order

No work has yet been logged on this issue.

People

Assignee:

Christophe DENEUX

Reporter:

Guillaume Laplace
Watchers:

0

Dates

Created:

Fri, 10 Aug 2018 - 10:07:55 +0200

Updated:

Wed, 12 Dec 2018 - 17:08:28 +0100

Resolved:

Wed, 12 Dec 2018 - 17:07:58 +0100

Petals SE Flowable

Allow to use the message content of an IntermediateCatchEvent

Details

Activity

People

Dates