resultVariableNameZipFile

Fieldname in the datamap where the builded zipFile is written to.

resultVariableNameZipName

-

Fieldname in the datamap where the name of the zipFile is written to.

zipfileName

Example value:

• ${Person_LastName}_${Person_FirstName}_Binaries.zip

How the zipFile shall be named. fileExtension like '.zip' is needed.

coreObjectDescriptorList

coreObjectDescriptor which contains a list of CoreObjects with binaryData

<name of the zipFile-Entry>

 (minimum 1)

<name of binaryField to save into zipFIle>

Example value:

• ${Person_LastName}_${Person_FirstName}_Photo.jpg
  ← Person_Photo

• ${Person_LastName}_${Person_FirstName}_Softtoken.p12
  ← Person_Softtoken

• Additional parameter, added with "+"

• Combination zipEntryName ← BinaryFieldName

Image Removed

searchConfigName

-

Defines the search configuration that should be used to count objects.

During process execution the user must have the permission to execute the search configuration. It is possible to use a search configuration that searches over multiple levels.

Note: The binary data fields will not be loaded into the process map unless the search configuration has at least one binary data field in the result columns.

maxCount

The maximum number of objects that should be found.

resultVariableName

-

• CoreObjectDescriptorList

Specifies the name of a variable of the data map, where the CoreObjectDescriptorList of the found objects is stored.

copyValuesOfFirstResult

-

Valid values:

• true

• false (default)

This parameter decides whether the first found object is put completely to the map (true) or if the CoreObjectDescriptorList is put to the map (false). If set to true, resultVariableName will be ignored. maxCount will be ignored too and set to 1.

fullResultListField

-

<variableName>

Variable in which the full search result will be stored inside the process map. Will be ignored if it is empty.

TargetPrefix

-

<Prefix>

Example: Manager_

If the found objects fields should be added to the process map with a special prefix. It replaces the <Datapool_>, which is otherwise at this position. With this function, conflicting entries can be avoided.

Example: Instead of "Person_Email" the data map will get an additional entry: "Manager_Email".

sortColumn

-

<ColumnName> Example: FirstName

This parameter is the column name of the dataset, which is taken to order the search result.

sortOrder

-

Valid values:

• ASC (default)

• DESC

Combo box to select if the search result is ordered ascending or descending. Default is ascending.

<Datapool_Field>

-

<CONDITION>:<value>

Examples:

• EQUALS:true

• STARTS_WITH:${processVariable}

Valid CONDITIONS:

• EQUALS

• NOT_EQUALS

• GREATER_THAN

• GREATER_EQUALS

• LESS_THAN

• LESS_EQUALS

• STARTS_WITH

• ENDS_WITH

• CONTAINS

• SOUNDEX

• EMPTY

• NOT_EMPTY

• The datapool field adds and overwrites filters to the existing filters in the searchConfiguration.

• Allowed multiple times, for each search field of the search config. You can add several datapool_fields with the same name, for example, birth date fields to create a date range. 

• Filter condition and value shall be separated by a colon symbol, like this, <CONDITION>:<value>.

  • Drag and drop a datapool-field into the Service Task definition, to create a filter, for example, OrderNumber, see (1) in the screenshot.

  • Add the datapool field name as a prefix, for example, SclmDpOrder_OrderNumber, see (2) in the screenshot. Every filter that is added as <Datapool_Field> MUST exist in the used SearchConfig, otherwise it will not be added when the search task is executed. When adding the new parameter and its name, make sure to use the correct prefix for your configuration. 

  • For the value, a condition is needed, in the screenshot for example "EQUALS".Image Removed

You can also use the conjunctions AND and OR. For example:
EQUALS:Active _OR_ temporary.inactive

searchUniqueId

-

<value>

Example: ${<Datapool>_Id}

It is the Unique ID (<Datapool>_Id) used to store records in the underlying database. The value can be a literal or a JUEL expression. This filter always uses equals to identify the record. In case of a related search, this is used to identify the Source Object.

resultUniqueId

-

<value>

Example: ${<Datapool>_Id}

It is the Unique ID (<Datapool>_Id) used to store records in the underlying database. The value can be a literal or a JUEL expression. This filter always uses equals to identify the record. In case of a related search, this is used to identify the Result Object.

targetFieldName

Name of systemProperty to load

Combination of target field and system property.

A system property is defined of <contextid>.<propertyName>.

Image Removed