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

Receive Port Message Activity

The Receive Message Workflow Activity waits for receipt of a Blue Integrator Message.  Each Receive Port Message Activity is bound to a Receive Port in the Blue Integrator Explorer when configuring a Workflow.  This activity is towards the top of the Activity Palette in the Blue Integrator Workflow Designer.

To use this activity in a Workflow, you must set the Message parameter, by selecting from the drop-down list of configured Blue Integrator Messages.  On execution, this is the name of the Message variable that will contain the received Message.  The Activity will block until a Message is received, and supports asynchronous operation, so it can be contained within an EventDriven Activity.  The exception is that the first Receive Port Message Workflow Activity in a Workflow will not block, and will exit with an error if there is not a Message waiting – this is because Workflow Instances are triggered on receipt of a message bound to the first Receive Port Message Workflow Activity, and so necessarily there should be a Message waiting.

Optionally you can configure the CorrelationFilter property, to determine which future messages will be directed../Workflow Correlation.htm to this Workflow Instance.  See the Correlation topic for further details.