Xpath of MessageStart/End Events

[Steve]

Version: Bizagi Xpress 9.1.2.1020

Situation:
There are two processes, SendPayment and ReceivePayment
The end of SendPayment needs to start ReceivePayment
SendPayment's MessageEnd event has the same name as ReceivePayment's MessageStart event
SendPayment's MessageEnd event is configured to sync with ReceivePayment's MessageStart event
SendPayment correctly instantiates a new ReceivePayment process

Problem:
Xpath button disabled on Configure message form.
The details created during the SendPayment process are not visible to the ReceivePament process.

How can I manually configure the xpath of a MessageEnd event (as per the Configure Message form) so that my receiving process/task knows which case it is receiving? The wiki example and youtube video are of no help as the Xpath button is disabled.

[BizAgi Xpress Support]

Dear Steve,
Thank you very much for your interest in BizAgi.

Unfortunately, the message start and message end shapes currently cannot send data (other than metadata that triggers the target process).
Concerning your implementation, you will need to replace in your processes the message end and message start, for the signal start and signal end shapes (http://wiki.bizagi.com/en/index.php?title=Start_And_End_Shapes#Signal_Start, http://wiki.bizagi.com/en/index.php?title=Start_And_End_Shapes#Signal_End).

In the actual BizAgi Xpress version, the signal shapes will override the message shapes functionality if you wish to share data within your processes SendPayment and ReceivePayment. For this to be done succesfully, you will need:

1. To have in you data model, an idSendPayment attribute in your ReceivePayment process entity.
2. To set this attribute in an "On Enter" action expression, which would assign ReceivePayment.idSendPayment = SendPayment by Xpath value.

Having done this, the ReceivePayment process will have visibility of which SendPayment instance launched its start, by navigating its Xpath as "ReceivePayment.idSendPayment.Data...".

About the Xpath button/field being disabled, it will be enabled if you have modeled that SendPayment can specify an idCase of an specific existing ReceivePayment instance. This idCase needs to be set while in SendPayment execution and will not create a new ReceivePayment instance but trigger its continuance (given ReceivePayment is in a "waiting" status).

Best regards,
BizAgi Xpress Support.

[Steve]

Thank you, using Signal Start and Signal End does indeed work. That part of my problem is now resolved.

The Xpath button is still not available during Message Start configuration, irrespective of which type of relationship is used in the database.

[BizAgi Xpress Support]

Dear Steve,

In order for the Xpath button to be enabled, please consider that this field is configured only so that the Message End can specify the idCase of an existing case in another process. Therefore, it is needed that the target "Process" you specify, has an available message "Element" different than a Message Start (a Message event with the "Is throw" property unmarked).
This is designed this way, because the Message Start will always create a new case, so no specification of idCase is needed whatsoever.

Best Regards,
BizAgi Xpress Support