The “delivery” transaction is where the process server executes the Intermediate Message Event, i.e., receives the message, output maps its payload to the process data context, and proceeds on the respective control flow branch. Thus, we can say that this message is a perfect fit for the Process. Delivery: If a message passed a correlation condition, it is set to be the delivery state.concat(message/name, string(message/id))=substring(context,0,3).Thus, correlation ID acts as a filter for the BPM Process. For example: if a start event has a correlation condition based on the value of an XML tag is equal to a string or not. A correlation ID is nothing but a Boolean condition to validate if the message which has reached the BPM component matches a Process and can be delivered for initiation of the Event Trigger. This is one of the important functions of Event-Based Trigger. Matching: When a message reaches BPM, it is matched to the process based on some correlation ID.Intermediate Message Event follows a mechanism called Matching and Delivery.conversations between the process and another component.As such, they cater for a variety of use-cases, including
The Document upload interface has the payload of size in MBs whereas the Order Details interface has payload of size in KBs.
Both interfaces were triggered almost at the same time. We were having two interfaces named Document Upload and Order Details. In our project, the requirement was to send the data from CRM to RabbitMQ. Here in this blog, I would like to consolidate all my learnings and try to make it simple and easy for you using one scenario explained below Problem Definition I read so many blogs and white papers to understand the BPM concept, how it is different from ccBPM? and also what are the guidelines to be followed. A few months back, I had a requirement in which I needed to explore BPM for one of our Business requirements.