Location Prefixes

When configuring a value in a process or a business rule, you can direct Loftware Enterprise SP to look for the data in the job data, the process, system properties, or the current row if processing rows of data. You can direct Loftware Enterprise SP to check only one of these locations for the key (name), or to check more than one of these locations in a specified order.

Prefix	Effect
$ or $#	Look for the key in the job data and return the associated value. If the key is not found in the job data, look in the process.
# or #$	Look for the key in the process and return the associated value. If the key is not found in the process, look in the job data.
$$	Look for the key in the job data and return the associated value. If the key is not found, do not look for it in other locations.
##	Look for the key in the process and return the associated value. If the key is not found, do not look for it in other locations.
%	Look for the key in the system properties and return the associated value. If the key is not found and no other location is specified, do not look for it in other locations.
@	Look for the key in the row of data currently being processed and return the associated value. If the key is not found and no other location is specified, do not look for it in other locations.

Complex Lookup Examples

You can use several prefixes in combination so that you can look for a key in more than one location, specifying the order in which to check the locations. You can also use a value retrieved from one key as the key or part of the key for a second lookup.

Example	Result
@%$#{/Body/Category}	This prefix and key cause Loftware Enterprise SP to look for a key named /Body/Category in several locations, stopping when it is found, and to return the associated value. Loftware Enterprise SP first looks for the key in the row of data currently being processed. If the key is not found there, then Loftware Enterprise SP looks for it in the system properties, then the job data, and then the process. When the key is found, the value is returned and the lookup ends without checking any remaining locations.
${@{column1}}	This complex prefix and key cause Loftware Enterprise SP to look for a key named column1 in the row of data currently being processed. If found, the value of column1 is then used as a key for a lookup in the job data, and the associated value from the job data is returned.
$${Color@{column1}}	This complex prefix and key cause Loftware Enterprise SP to look for a key named column1 in the row of data currently being processed. If found, the value of column1 preceded by the text row is used as a key for a lookup in the job data, and the value associated with that key is returned. For example, if column1=Blue in a particular row, then Loftware Enterprise SP would look for a key named ColorBlue in the job and return the value associated with that key.

Example

Result

@%$#{/Body/Category}

This prefix and key cause Loftware Enterprise SP to look for a key named /Body/Category in several locations, stopping when it is found, and to return the associated value. Loftware Enterprise SP first looks for the key in the row of data currently being processed. If the key is not found there, then Loftware Enterprise SP looks for it in the system properties, then the job data, and then the process. When the key is found, the value is returned and the lookup ends without checking any remaining locations.

${@{column1}}

This complex prefix and key cause Loftware Enterprise SP to look for a key named column1 in the row of data currently being processed. If found, the value of column1 is then used as a key for a lookup in the job data, and the associated value from the job data is returned.

$${Color@{column1}}

This complex prefix and key cause Loftware Enterprise SP to look for a key named column1 in the row of data currently being processed. If found, the value of column1 preceded by the text row is used as a key for a lookup in the job data, and the value associated with that key is returned.

For example, if column1=Blue in a particular row, then Loftware Enterprise SP would look for a key named ColorBlue in the job and return the value associated with that key.