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

Database Activity

The Database Activity allows you to directly interact with a SQLServer or Access database from a Workflow. You simply set the connection string, and the query (which can contain tokens).  The tokens can be Workflow variables, Workflow messages, Workflow message properties (in the syntax MessageName.PropertyName) or XPath, the XPath relating to the optional ParameterMessage property.

Data can optionally be returned as an Xml message, and on specifying the root and record tag names BlueIntegrator will automatically generate the schema for you.  The message will be returned in the message specified by the ReturnMessage property.

For further details please see the Database Send Transport, which uses a similar model.