xAPPnow LOW CODE PLATFORM - User Manual 

Still no account yet?

×

BPMN Advanced Training: Message Start, Intermediate, End Events

 
This low-code tutorial provides a tutorial for Process Comunication by Message to demonstrate the usage of a BPMN Message Intermediate Event: Throwing, Message Intermediate Event: Catching, Message Start Event and Message End Event.
 
Prerequisites:
A Message Definition Object must be created first. This element is available on Definition Object Model. Check this topic for more details: Base Definition Elements - Message Definition Object.
 
In this sample, a User Registration process starts a Registration Moderation process by a message and waits for the moderation results. Once the moderation is done, the user will receive the status of the registration requested and will be notified with the results to the User Registration process. It consists of 2-collaboration models, called "UserRegistration" and "RegistrationModeration", which execute the following process steps:
 
  • UserRegistration:
  • This process begins with a User Task Request Registration, which is saved in a Registration Business Object named registration.
  • An exclusive gateway asks if the request was canceled. If yes the process ends and if not it continues to send the message object to the second collaboration model.
  • Then the process uses a Message Intermediate Event: Throwing "Start Moderation" to send the message object, in this case is a “registration”.
  • The process waits at the Message Intermediate Event: Catching for the message from the "RegistrationModeration" process.
  • After receiving the message, the attributes of the related Message Object are displayed in the User Task "View Registration Result".
  • In the User Task "View Registration Result" is possible to select if the process finish or begin again when the button Retry is selected and a gateway is configured to handle this.
     
  • RegistrationModeration:
  • The Message Start Event with the message object "registration" starts this process.
  • The attributes of the Registration Object, which was sent as a payload of this message, are displayed in a User Task "Moderate Registration" and the status of the registration can be updated.
  • After the User Task "Moderate Registration" a gateway asks if the registration status was updated.
  • The process ends with Message End Event, which send the message object registration to the "UserRegistration" collaboration model.
 
The following screenshot displays the Message Intermediate Event: Throwing configuration of the "UserRegistration" Collaboration. This configuration tab is the same for Message End Event.
  • At first, the “Receiver Process Name” has to be specified in the Configuration Tab. In this case, "Registration Moderation".
  • Based on the "Receiver Process" specification the available messages, to communicate with this process are selectable. This will display the message object mapped on Message Start Event.
 
 
The following screenshot displays the Message Intermediate Event: Catching configuration of the "UserRegistration" Collaboration. This configuration tab is the same as the Message Start Event.
  • A Message Definition object should be mapped from Definition Object subtab.