We value your privacy

We use cookies to enhance your browsing experience, serve personalized ads or content, and analyze our traffic. By clicking "Accept All", you consent to our use of cookies.

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 Binding

Before a Workflow can be activated, it must first be bound.  This applies only to Workflows that contain Send and Receive activities – Workflows that are designed only to be called from other Workflows do not need to be bound.  A Binding associates real BlueIntegrator Ports with the ReceivePortActivity and SendPortActivity items in a Workflow.  A Binding can also provide initialization information for Workflow variables, allowing for easy parameterization.

To bind a Workflow, select it in the Blue Integrator Explorer tree, and select the Bindings tab.

A list of current Bindings is displayed here.  You can add, edit and delete Bindings as required.

On creating or editing a Binding, the Binding properties form is displayed:

On the Binding tab, you can specify a name for the Binding, and you can also specify the Port associations.

On the Parameters tab, you can specify initial values for all Workflow variables (as defined in the Workflow Editor on the Messages & Variables tab).

NOTE Note that you can specify Receive or Send Ports as associated with a Send Activity – if you specify a Receive Port this effectively resubmits the output back into the system.

On the Processing tab, you can specify whether or not this bound Workflow operates in Sequential mode. This is a mode designed for complicated correlation scenarios where Workflow Instances are initialized one at a time to ensure that every Workflow Instance has a chance to set up a Correlation Filter before any other Workflow Instances are initialized.  By default this option is disabled for optimal performance.

Finally, on the Tracking / Debugging tab you can specify Tracking and Debugging options, specifically :

– Should state transitions be logged for this bound Workflow

– Should Message and Variable contents be logged for this bound Workflow.  Only Messages and Variables flagged for tracking via the Messages & Variables tab (TrackContents property) will be logged

– Should Workflow Instances be Suspended on start (to allow easy debugging)

Våra medarbetare har arbetat med integration i över 20 år. Till vår samlade kunskap har vi sedan 2012 adderat Blue Integrator, integrationsmotorn som i dag används av över 200 företag i hela världen.

Facebook-f Linkedin Youtube Medium



    + 46 729 64 80 15
    support@blueintegrator.com
    Star street 1, SE-512 50 SVENLJUNGA
    microsoft-gold-partner