Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Help

Workflow Correlation

Send and Receive Message activities have a CorrelationFilter property. This property is used to define messages arriving at a port bound to a workflow that will be directed to the current Workflow Instance.  In the absence of a CorrelationFilter, all incoming messages would be directed to new (rather than an existing) workflow instances.

A CorrelationFilter expression is like a regular Blue Integrator Filter except that it can relate to two messages: a reference message and the incoming message. The filter determines whether a new incoming message should be directed to a workflow instance by comparing it to the reference message. For example, a workflow may be used to process receipts, so on sending a message a CorrelationFilterproperty on the Send Message Activity can be configured to route incoming messages of type PurchaseOrder/Receipt where 
[Reference Message].PurchaseOrderId = [SecondaryMessage].ReceiptEntityId. A Receive Message Activity is still required to actually receive these receipts, but the CorrelationFilter will ensure that they are routed appropriately.

The Correlation Filter is bound at the time of the receive or send action, which means any subsequent changes to messages (or the value of properties) will not be reflected immediately.

The Correlation Filter is set in the Workflow Editor properties for a Send or Receive Port activity: