Skip to main content

Database lookup

Description

Database lookup is a step in the Lookup Plugin for Process Studio Workflows. The Database lookup step looks up values in a database table. Lookup values are added as new fields in the stream.

Configurations

No.Field NameDescription
1Step nameSpecify the name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow.
2ConnectionSpecify the Database connection for the lookup table.
3Lookup schemaSpecify the Database schema containing the lookup table.
4Lookup TableSpecify the name of the database table used for the lookup.
5Enable cache?Enables caching of database lookups. This means that once a key (or group of key) has been looked up, the looked up values are stored, and returned again the next time this key (or group of key) is being looked up (without incurring the cost of a database call).
6Cache size in rowsSpecify the size of the cache (number of rows), 0 means cache everything.
7Load all data from tablePre-loads the cache with all the data present in the lookup
table. This may improve performance by avoiding database calls. However, if you have a large table, you risk running out of memory.
8Keys to look up tableSpecify the keys and conditions to perform the database lookup.
9Values to return tableSpecify the fields from the lookup table to add to the output stream.

- "New name" allows you to use a different name if the database column name is inappropriate.

- "Default" is the value returned (instead of null) if the lookup fails.

- "Type" is the type of the output field.

Note: Enabling error handling on the Database Lookup step will redirect all failed lookup rows to the error handling step, instead of adding them to the main output stream with null/default values.

10Do not pass the row if the lookup failsEnable checkbox to avoid passing a row when lookup fails. Within the SQL syntax, enabling this would be an INNER JOIN, otherwise it would be an OUTER JOIN.
11Fail on multiple results?Enable checkbox to force the step to fail if the lookup returns multiple results.
12Order byIf the lookup query returns multiple results, the ORDER BY clause helps you to select the record to take. For example, ORDER BY would allow you to pick the customer with the highest sales volume in a specified state.
13Get FieldsClick to return a list of available fields from the input stream(s) of the step.
14Get lookup fieldsClick to return a list of available fields from the lookup table that can be added to the step's output stream.