Transform
Add XML column is a step in the Transform Plugin for Process Studio Workflows. The Add XML column step encodes the content of a number of fields in a row in XML. This XML is added to the row in the form of a String field.
Add XML Column:
No.
Field Name
Description
1
Step name
Specify the name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow.
Content Tab:
No.
Field Name
Description
1
Encoding
Specify the encoding to use. This encoding is specified in the header of the XML file
2
Output Value
Specify the name of the new field that contains the XML
3
Root XML element
Specify the name of the root element in the generated element.
4
Omit XML header
Enable to not include the XML header in the output.
5
Omit null values from the XML result
Do not add or eliminate elements or attributes with null values. This is often used to limit the size of the target XML.
Fields Tab:
The Fields tab is where you configure the output fields and their formats. The table below describes each of the available properties for a field:
No.
Field Name
Description
1
Fieldname
Specify the name of the field
2
Element name
Specify the name of the element in the XML file to use
3
Type
Specify the Type of the field can be either String, Date, or Number
4
Format
Specify the Format mask with which to convert data; see Number Formats for a complete description of format specifiers
5
Length
Output string is padded to this length if it is specified
6
Precision
Specify the precision.
7
Currency
Specify the Symbol used to represent currencies like $10,000.00 or E5.000,00
8
Decimal
Specify the decimal separator. The Decimal point separator can be a "." (10,000.00) or "," (5.000,00)
9
Grouping
Specify a thousand’s group separator. A group separator can be a "," (10,000.00) or "." (5.000,00)
10
Null
Specify the string to use in case the field value is null.
11
Attribute
Choose Y/N from the dropdown list. Choose Y to make this an attribute (N means: element)
12
Attribute parent name
You can specify the name of the parent element to add the attribute to if previous parameter attribute is set to Y.
If no parent name is specified, the attribute is set in the parent element.
Add Constants is a step in the Transform Plugin for Process Studio Workflows. The Add constant values step is a simple and high performance way to add constant values to the stream.
No.
Field Name
Description
1
Step name
Specify the name of the step.
Note: This name has to be unique in a single workflow.2
Fields
Specify the name, type, and value in the form of a string. Specify the formats to convert the value into the chosen data type.
Add sequence is a step in the Transform Plugin for Process Studio Workflows. The Add sequence step adds a sequence to the stream. A sequence is an ever-changing integer value with a specific start, increment and maximum value. You may use a database to generate the sequence or use a workflow counter in Process Studio to generate the sequence.
No.
Field Name
Description
1
Step name
Specify the name of this step as it appears in the workflow workspace. This name must be unique within a single workflow.
2
Name of value
Specify the name of the new sequence value that is added to the stream.
3
Use DB to generate the sequence
Enable if you want the sequence to be driven by a database sequence, then set these parameters: Connection name, Schema name (optional), Sequence name.
4
Connection name
Specify the name of the connection on which the database sequence resides.
5
Schema name (optional)
Specify the table's schema name.
6
Sequence name
Specify the name of the database sequence.
7
Use a workflow counter to generate the sequence
Enable if you want the sequence to be generated by Process Studio, and then set these parameters: Counter name (optional), Start at, Increment by, Maximum value.
8
Counter name (optional)
If multiple steps in a workflow generate the same value name, this option enables you to specify the name of the counter to associate with. Avoids forcing unique sequencing across multiple steps.
9
Start at
Specify the value to begin the sequence with.
10
Increment by
Specify the amount/number by which the sequence increases or decreases.
11
Maximum value
Specify the value after which the sequence returns to the Start At value.
Calculator is a step in the Transform Plugin for Process Studio Workflows. The calculator step provides predefined calculation expressions that can be executed on input field values. It can take up to three input arguments (Field A, Field B and Field C) and a return type must be specified. You may perform multiple such calculations within the step that are independent of each other or depend on fields generated in previous calculations. There is an option to remove fields from the output after all values are calculated. This is useful for removing temporary values.
No.
Field Name
Description
1
New field
This field is populated by the value of the calculation. This field can be temporary or permanent.
2
Calculation*
This field contains the expression of the calculation.
3
Field A
An input for the calculation
4
Field B
An input for the calculation
5
Field C
An input for the calculation
6
Value type
It is the data type of the new field
7
Length
It is the length of the data type
8
Precision
It is the precision of the data type
9
Remove
If remove is selected then the value in the new field is deleted after completion of the step. It can be used for interim calculations.
10
Conversion mask
Date or Number format
11
Decimal symbol
The decimal digits and precision separator
12
Grouping symbol
The thousand separator
13
Currency symbol
Currency symbol
*Calculations Available
The table below contains the available calculations and associated descriptions:
No
Calculation
Explanation
Mandatory fields
1
Set field to constant A
Create a field with a constant value.
A
2
Create a copy of field A
Create a copy of a field with the given field value.
A
3
A + B
A plus B.
A and B
4
A - B
A minus B.
A and B
5
A * B
A multiplied by B.
A and B
6
A / B
A divided by B.
A and B
7
A * A
The square of A.
A
8
SQRT( A )
The square root of A.
A
9
100 * A / B
Percentage of A in B.
A and B
10
A - ( A * B / 100 )
Subtract B% of A.
A and B
11
A + ( A * B / 100 )
Add B% to A.
A and B
12
A + B *C
Add A and B times C.
A, B and C
13
SQRT( A*A + B*B )
Calculate ?(A2+B2).
A and B
14
ROUND( A )
Returns the closest Integer to the argument. The result is rounded to an Integer by adding 1/2, taking the floor of the result, and casting the result to type int. In other words, the result is equal to the value of the expression: floor (a + 0.5).
In case you need the rounding method "Round half to even", use the following method ROUND( A, B ) with no decimals (B=0).A
15
ROUND( A, B )
Round A to the nearest even number with B decimals. The used rounding method is "Round half to even", it is also called unbiased rounding, convergent rounding, statistician's rounding, Dutch rounding, Gaussian rounding, odd-even rounding, bankers' rounding or broken rounding, and is widely used in bookkeeping. This is the default rounding mode used in IEEE 754 computing functions and operators. In Germany it is often called "Mathematisches Runden".
A and B
16
STDROUND( A )
Round A to the nearest integer. The used rounding method is "Round half away from zero", it is also called standard or common rounding. In Germany it is known as "kaufmännische Rundung" (and defined in DIN 1333).
A
17
STDROUND( A, B )
Same rounding method used as in STDROUND (A) but with B decimals.
A and B
18
CEIL( A )
The ceiling function maps a number to the smallest following integer.
A
19
FLOOR( A )
The floor function maps a number to the largest previous integer.
A
20
NVL( A, B )
If A is not NULL, return A, else B. Note that sometimes your variable won't be null but an empty string.
A and B
21
Date A + B days
Add B days to Date field A.
Note: Only integer values for B are supported. If you need non-integer calculations, please add a second calculation with hours.A and B
22
Year of date A
Calculate the year of date A.
A
23
Month of date A
Calculate number the month of date A.
A
24
Day of year of date
A Calculate the day of year (1-365).
A
25
Day of month of date A
Calculate the day of month (1-31).
A
26
Day of week of date A
Calculate the day of week (1-7).
A
27
Week of year of date A
Calculate the week of year (1-54).
A
28
ISO8601 Week of year of date A
Calculate the week of the year ISO8601 style (1-53).
A
29
ISO8601 Year of date A
Calculate the year ISO8601 style.
A
30
Byte to hex encode of string A
Encode bytes in a string to a hexadecimal representation.
A
31
Hex encode of string A
Encode a string in its own hexadecimal representation.
A
32
Char to hex encode of string A
Encode characters in a string to a hexadecimal representation.
A
33
Hex decode of string A
Decode a string from its hexadecimal representation (add a leading 0 when A is of odd length).
A
34
Checksum of a file A using CRC-32
Calculate the checksum of a file using CRC-32.
A
35
Checksum of a file A using Adler-32
Calculate the checksum of a file using Adler-32.
A
36
Checksum of a file A using MD5
Calculate the checksum of a file using MD5.
A
37
Checksum of a file A using SHA-1
Calculate the checksum of a file using SHA-1.
A
38
Levenshtein Distance (Source A and Target B)
Calculates the Levenshtein Distance
A and B
39
Metaphone of A (Phonetics)
Calculates the metaphone of A
A
40
Double metaphone of A
Calculates the double metaphone of A
A
41
Absolute value ABS(A)
Calculates the Absolute value of A.
A
42
Remove time from a date A
Removes time value of A.
Note: Daylight Savings Time (DST) changes in Sao Paulo and some other parts of Brazil at midnight 0:00. This makes it impossible to set the time to 0:00 at the specific date, when the DST changes from 0:00 to 1:00 am. So, there is one date in one year in these regions where this function will fail with an "IllegalArgumentException: HOUR_OF_DAY: 0 -> 1". It is not an issue for Europe, the US and other regions where the time changes at 1:00 or 2:00 or 3:00 am.
A
43
Date A - Date B (in days)
Calculates difference, in days, between A date field and B date field.
A and B
44
A + B + C
A plus B plus C.
A, B, and C
45
First letter of each word of a string A in capital
Transforms the first letter of each word within a string.
A
46
UpperCase of a string A
Transforms a string to uppercase.
A
47
LowerCase of a string A
Transforms a string to lowercase.
A
48
Mask XML content from string A
Escape XML content; replace characters with &values.
A
49
Protect (CDATA) XML content from string A
Indicates an XML string is general character data, rather than non-character data or character data with a more specific, limited structure. The given string will be enclosed into <![CDATA[String]]>.
A
50
Remove CR from a string A
Removes carriage returns from a string.
A
51
Remove LF from a string A
Removes linefeeds from a string.
A
52
Remove CRLF from a string A
Removes carriage returns/linefeeds from a string.
A
53
Remove TAB from a string A
Removes tab characters from a string.
A
54
Return only digits from string A
Outputs only Outputs only digits (0-9) from a string from a string.
A
55
Remove digits from string A
Removes all digits (0-9) from a string.
A
56
Return the length of a string A
Returns the length of the string.
A
57
Load file content in binary
Loads the content of the given file (in field A) to a binary data type (e.g. pictures).
A
58
Add time B to date A
Add the time to a date, returns date and time as one value.
A and B
59
Quarter of date A
Returns the quarter (1 to 4) of the date.
A
60
variable substitution in string A
Substitute variables within a string.
A
61
Unescape XML content
Unescape XML content from the string.
A
62
Escape HTML content
Escape HTML within the string.
A
63
Unescape HTML content
Unescape HTML within the string.
A
64
Escape SQL content
Escapes the characters in a String to be suitable to pass to an SQL query.
A
65
Date A - Date B (working days)
Calculates the difference between Date field A and Date field B (only working days Mon-Fri).
A and B
66
Date A + B Months
Add B months to Date field A.
Note: Only integer values for B are supported. If you need non-integer calculations, please add a second calculation with days.A
67
Check if an XML file A is well formed
Validates XML file input.
A
68
Check if an XML string A is well formed
Validates XML string input.
A
69
Get encoding of file A
Guess the best encoding (UTF-8) for the given file.
A
70
Dameraulevenshtein distance between String A and String B
Calculates Dameraulevenshtein distance between strings: http://en.wikipedia.org/wiki/Damerau%E2%80%93Levenshtein_distance
A and B
71
NeedlemanWunsch distance between String A and String B
Calculates NeedlemanWunsch distance between strings: http://en.wikipedia.org/wiki/Needleman%E2%80%93Wunsch_algorithm
A and B
72
Jaro similitude between String A and String B
Returns the Jaro similarity coefficient between two strings.
A and B
73
JaroWinkler similitude between String A and String B
Returns the Jaro similarity coefficient between two string: http://en.wikipedia.org/wiki/Jaro%E2%80%93Winkler_distance
A and B
74
SoundEx of String A
Encodes a string into a Soundex value.
A
75
RefinedSoundEx of String A
Retrieves the Refined Soundex code for a given string object
A
76
Date A + B Hours
Add B hours to Date field.
Note: Only integer values for B are supported. If you need non-integer calculations, please add a second calculation with minutes.A and B
77
Date A + B Minutes
Add B minutes to Date field.
Note: Only integer values for B are supported. If you need non-integer calculations, please add a second calculation with seconds.A and B
78
Date A - Date B (milliseconds)
Subtract B milliseconds from Date field A
A and B
79
Date A - Date B (seconds)
Subtract B seconds from Date field A.
Note: Only integer values for B are supported. If you need non-integer calculations, please add a second calculation with milliseconds.A and B
80
Date A - Date B (minutes)
Subtract B minutes from Date field A.
Note: Only integer values for B are supported. If you need non-integer calculations, please add a second calculation with seconds.A and B
81
Date A - Date B (hours)
Subtract B hours from Date field A.
Note: Only integer values for B are supported. If you need non-integer calculations, please add a second calculation with minutes.A and B
82
Hour of Day of Date A
Extract the hour part of the given date
A
83
Minute of Hour of Date A
Extract the minute part of the given date
A
84
Second of Hour of Date A
Extract the second part of a given date
A
85
Second of Minute of Date A
86
ROUND_CUSTOM(A,B)
87
ROUND_CUSTOM(A,B,C)
88
Date A + B Seconds
89
Remainder of A / B
Add value fields changing sequence is a step in the Transformation Plugin for Process Studio Workflows. This step generates a sequence based on Start at and Increment by values. The sequence resets each time a value changes in any of the specified fields in the list. The input data should typically arrive in an ordered fashion although as long as identical values are grouped together in the data stream the step works as desired.
No.
Field Name
Description
1
Step name
Specify the name of the step, needs to be unique in a workflow
2
Result field
Specify the name of the output field, the sequence
3
Start at value
Specify the number to start at each time
4
Increment by
Specify the value to increase at each row in the same group
5
Init sequence if value of following fields change
Specify a list of fields here. If a value in one or more of these field’s changes compared to the previous rows, the sequence will be reset to the start value.
Concat fields, is a step in the Transformation Plugin for Process Studio Workflows. The Concat Fields step concatenates multiple fields (The fields can be separated by a separator and an enclosure) and outputs into a target field.
No.
Field Name
Description
1
Step name
Specify the name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow.
2
Target Field Name
Specify the name of the target field (String type)
3
Length of Target Field
Specify the length of the string type (setting the meta-data of the String type, this is also used by the Fast Data Dump option for performance optimization)
4
Separator
Specify the character that separates the fields in a single line of text. Typically this is ; or a tab.
5
Enclosure
A pair of strings can enclose some fields. This allows separator characters in fields. The enclosure string is optional.
Fields Tab: This is identical to the fields tab option of the Text File Output step.
No.
Field Name
Description
1
Name
Specify the name of the field.
2
Type
Specify the Type of the field can be either String, Date or Number.
3
Format
Specify the format mask to convert with. See Number Formats for a complete description of format symbols.
4
Length
Specify the length option depends on the field type follows:
Number - Total number of significant figures in a number
String - total length of string
Date - length of printed output of the string (e.g. 4 only gives back year)
5
Precision
Specify the precision option depends on the field type as follows:
- Number - Number of floating point digits
- String - unused
- Date - unused
6
Currency
Specify the symbol used to represent currencies like $10,000.00 or E5.000,00
7
Decimal
A decimal point can be a "." (10,000.00) or "," (5.000,00)
8
Group
A grouping can be a "," (10,000.00) or "." (5.000,00)
9
Trim type
Specify the trimming method to apply on the string. Trimming only works when there is no field length given.
10
Null
If the value of the field is null, insert this string into the text file
11
Get
Click to retrieve the list of fields from the input fields stream(s)
12
Button: Minimal width
Alter the options in the fields tab in such a way that the resulting width of lines in the text file is minimal. So instead of save 0000001, we write 1, etc. String fields will no longer be padded to their specified length.
Advanced Tab
No.
Field Name
Description
1
Remove selected fields
Enable this checkbox to remove all selected fields from the output stream.
2
Force the enclosure around fields?
Enable this checkbox to force all field names to be enclosed with the character specified in the Enclosure property above.
3
Disable the enclosure fix?
This is for backward compatibility reasons (since version 4.1) related to enclosures and separators. The logic since version 4.1 is: When a string field contains an enclosure it gets enclosed and the enclose itself gets escaped. When a string field contains a separator, it gets enclosed.
Check this option, if this logic is not wanted. It has also an extra performance burden since the strings are scanned for enclosures and separators. So when you are sure there is no such logic needed since your strings don't have these characters in there and you want to improve performance, un-check this option.
4
Header
Enable this option if you want a header row. (First line in the stream). Note: All other output stream fields are set to Null when this line is produced.
5
Footer
Enable this option if you want a footer row. (Last line in the stream). Note: All other output stream fields are set to Null when this line is produced.
6
Encoding
Specify the String encoding to use from the dropdown list. Leave blank to use the default encoding on your system. To use Unicode specify UTF-8 or UTF-16. On first use, Process Studio will search your system for available encodings. Note: This is needed especially when you concatenate different encoded fields into the target field with a unique encoding. This applies also on Binary stored string fields due to Lazy conversion.
7
Right pad fields
Add spaces to the end of the fields (or remove characters at the end) until they have the specified length.
8
Fast data dump (no formatting)
Improves the performance when concatenating large amounts of data by not including any formatting information. Please consider setting the "Length of Target Field" option to an approximately maximum of the target field length. This improves performance since the internal buffer will be allocated and needs no reallocation when it is not sufficient.
Note: When then "Length of Target Field" option is "0", the internal buffer size is calculated as 50 times the number of concatenated fields, for instance an internal buffer of 250 is used by default for 5 fields.9
Split every ... rows
If this number N is larger than zero, split the resulting stream into multiple parts of N rows. Note: This is only needed when a Header/Footer is used to be compatible with the result of the Text File Output step.
10
Add Ending line of file
Allows you to specify an alternate ending row to the output stream. Note: All other output stream fields are set to Null when this line is produced.
Number range is a step in the Transformation Plugin for Process Studio Workflows. Number range step identifies the range for a numeric field based on defined ranges.
No.
Field Name
Description
1
Step name
Specify the name of this step as it appears in the workflow workspace.
2
Input field
Specify the field that gets checked for the lower and upper boundaries so that a range.
3
Output field
Specify the output field name that gets filled with the range value (ranges are defined in the table below) depending of the input field.
4
Default value
Value to return if there are no matches within the ranges specified.
Ranges(min<=x<=max):
Specify ranges.
5
Lower Bound
Specify a field name for the minimum value of a range.
6
Upper Bound
Specify a field name for the upper value of a range.
7
Value
Specify a field name for the value.
Rename Fields (Select / Rename values) is a step in the Transformation Plugin for Process Studio Workflows. The Rename fields step is useful for selecting, renaming, removing, changing data types and configuring the length and precision of the fields on the stream.
Select and Alter Tab:
Specify the exact order and name in which the fields have to be placed in the output rows
No.
Field Name
Description
1
Fieldname
The name of the field from the input stream
2
Rename to
The new name of the field. Leave blank if you do not wish to rename the field
3
Length
Specify this value if you want to implicitly select all other fields from the input stream(s) that are not explicitly selected in the Fields section.
4
Precision
The precision option depends on the field type, but only Number is supported; it returns the number of floating point digits
6
Include unspecified fields, ordered by name
Enable if you want to implicitly select all other fields from the input stream(s) that are not explicitly selected in the Fields section
Button: Edit Mapping
The Edit Mapping dialog allows you to easily define multiple mappings between source and target fields. Note: Edit Mapping will only work if there is only one target output step.
No.
Field Name
Description
1
Source fields
A list of input fields available to map. Select a field to begin mapping
2
Target fields
A list of fields that source fields can be mapped to. Once you have selected a source field, select a target field to create a mapping
3
Add
Adds a source and target field mapping pair to the Mappings section
4
Delete
Removes a selected Mappings entry
Remove Tab:
Specify the fields that have to be removed from the output rows.
Click Get fields to remove button to import fields from previous steps.
Note: Field removals can slow down the process since the field order gets internally changed.
Meta-data Tab: Change the name, type, length and precision (the metadata) of one or more fields. Click Get fields to change to import fields from previous steps.
No.
Field Name
Description
1
Fieldname
The name of the imported field. Note: If you renamed a field in the Select & Alter tab, the name here must match the renamed value.
2
Rename to
If you want to rename this field, this is where you put the new name
3
Type
The data type for this field
4
Length
The field length
5
Precision
The precision option depends on the field type, but only Number is supported; it returns the number of floating point digits
6
Binary to Normal?
Converts a string to a numeric data type, when appropriate
7
Format
The format mask (number type or date format)
8
Date Format Lenient?
Determines whether the date parser is strict or lenient. Leniency means that invalid date values are processed. If set to N, only strictly valid date values will be accepted; if set to Y, the parser will attempt to determine the intention of an incorrect date, if possible, and correct it.
9
Date Locale
Specifies the date locale to use for date conversions and calculations. Leave blank to use the default encoding on your system or chose from the populated this list accordingly.
10
Date Time Zone
Specifies the date time zone to use for date conversions and calculations. Leave blank to use the default encoding on your system or chose from the populated list accordingly.
11
Lenient number conversion
When this option is set to Y, numbers get parsed until it finds a non-numeric value (e.g. a dash or slash) and stops parsing without reporting an error. When set to N, numbers get parsed strictly throwing an error in case invalid numbers are in the input. The default behavior is set to N.
12
Encoding
Specifies the text file encoding to use. Leave blank to use the default encoding on your system. To use Unicode, specify UTF-8 or UTF-16. On first use, Process Studio searches your system for available encodings and populates this list accordingly.
13
Decimal
A decimal point; this is either a dot or a comma
14
Grouping
A method of separating units of thousands in numbers of four digits or larger. This is either a dot or a comma.
15
Currency
Symbol used to represent currencies
Replace in string is a step in the Transformation Plugin for Process Studio Workflows. Replace in string is a simple search and replace all occurrences of a word in a string with another word. It also supports regular expressions and group references. Group references are picked up in the replace with field as $n where n is the number of the group.
No.
Field Name
Description
1
Step name
Name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow.
2
In Stream field
Select the in stream field where search and replace is to be done.
3
Out Stream field
Select the out stream field where the new string value is put.
4
Use RegEx
Is your search string a regular expression. Select Y/N
5
Search
Enter the search string.
6
Replace with
Replace the search string with the replace string.
7
Set empty string?
Set the string to null(Y/N).
8
Replace with field
Select a field use to replace the Out Stream field.
9
Whole Word
Is the search and replace field a whole word. .Select Y/N
10
Case sensitive
Is the search and replace field case sensitive. Select Y/N
Row Normaliser is a step in the Transformation Plugin for Process Studio Workflows. Row Normaliser step outputs normalized data from De-normalized information
Following is an example where Row Normaliser step normalizes data back from pivoted tables as demonstrated below.
Below is a sample table of product sales data:
Month
Product A
Product B
Product C
2003/01
10
5
17
2003/02
12
7
19
...
...
...
...
The Row Normaliser step converts the data into the format below
so that it is easier to update your fact table:
Month
Product
sales
2003/01
A
10
2003/01
B
5
2003/01
C
17
2003/02
A
12
2003/02
B
7
2003/02
C
19
...
...
...
No.
Field Name
Description
1
Step name
Name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow.
2
Typefield
The name of the type field (product in the example above)
3
Fields table
A list of the fields you want to normalize; you must set the following properties for each selected field:
- Fieldname: Name of the fields to normalize (Product A ? C in the example).
- Type: Give a string to classify the field (A, B or C in our example).
- New field: You can give one or more fields where the new value should transfer to (sales in our example).
4
Get Fields
Click to retrieve a list of all fields coming in on the stream(s).
Row denormaliser is a step in the Transformation Plugin for Process Studio Workflows. The Row De-normalizer step de-normalizes data by looking up key-value pairs in the normalized data and assigning them to new fields in the output rows ad de-normalized data. It also allows you to immediately convert data types. This method may use aggregates and needs the input rows to be sorted on the grouping fields.
No.
Field Name
Description
1
Step name
Name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow.
2
Key field
The field that defined the key of the output row.
3
Group fields
Specify the fields that make up the grouping here.
4
Target fields
Select the fields to de-normalize by specifying the String value for the key field (see above).
Options are provided to convert data types. Strings are most common as key-value pairs so you must often convert to Integer, Number or Date. If you get key-value pair collisions (key is not unique for the group specified) specify the aggregation method to use.
Row flattener is a step in the Transformation Plugin for Process Studio Workflows. The Row flattener step flattens consecutive rows in the input stream to columns as specified in the step Target Fields configuration.
No.
Field Name
Description
1
Step name
Name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow.
2
The field to flatten
The field that must be flattened into different target fields.
3
Target fields
The name of the target field to which the field is flattened.
Set field value is a step in the Transformation Plugin for Process Studio Workflows. It replaces the value of a field with the value of another field.
No.
Field Name
Description
1
Step name
Name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow.
2
Field name
Displays the fields with values that can be replaced.
3
Replace by value from field
Specify the field value to replace the values in the Field name column.
Set field value to a constant is a step in the Transformation Plugin for Process Studio Workflows. Set field value to a constant step replaces the value of a field with a constant value and there could be a variable replacement within the constant.
No.
Field Name
Description
1
Step name
Name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow.
2
Use variable in constant
Selecting this option allows you to use variable replacement within a constant.
3
Field
Displays the fields with values that can be replaced.
4
Replace by value
The value that will replace existing values within the specified field.
5
Conversion mask (Date)
Choose a date format
6
Set empty string?
Assign a null value to the field
Sort rows, is a step in the Transformation Plugin for Process Studio Workflows. The Sort rows step sorts rows on the fields specified and on whether they should be sorted in ascending or descending order.
Process studio sorts rows using temporary files when the number of rows exceeds the default limit of 1 million rows. In case you get an out of memory exception (OOME), you need to lower this limit threshold or change your available memory.
No.
Field Name
Description
1
Step name
Name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow.
2
Sort directory
The directory in which the temporary files are stored in case when needed; the default is the standard temporary directory for the system
3
TMP-file prefix
Choose an easily recognized prefix so you can identify the files when they show up in the temp directory.
4
Sort size
The more rows you store in memory, the faster the sorting process because fewer temporary files must be used and less I/O is generated.
5
Free memory threshold (in %)
If the sort algorithm finds that it has less available free memory than the indicated number, it will start to page data to disk.
Note: This is not exact science, because:
- This is checked every 1000 rows. Depending on the row size and other steps within complex workflows this could still lead to an OutOfMemoryError.
- In a Java Virtual Machine it's not possible to know the exact amount of free memory. As such it is not recommended to use this step for very complex workflows with other steps and processes that use up a lot of memory.
6
Compress TMP Files
Compresses temporary files when they are needed to complete the sort.
7
Only pass unique rows?
Enable if you want to pass unique rows only to the output stream(s).
8
Fields table
Specify the fields and direction (ascending/descending) to sort. You can specify whether to perform a case sensitive sort (optional)
9
Get Fields
Click to retrieve a list of all fields coming in on the stream(s).
Split fields, is a step in the Transformation Plugin for Process Studio Workflows. The Split Fields step splits a field based on delimiter and enclosure information.
No.
Field Name
Description
1
Step name
Name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow.
2
Field to split
The name of the field you want to split
3
Delimiter
Delimiter that determines the field. Special characters (e.g. CHAR ASCII HEX01) can be set with the format $[value], e.g. $[01] or $[6F,FF,00,1F].
4
Enclosure
Specify the field enclosure.
5
Fields table
This table is where you define the properties for each new field created by the split. For each new field, you must define the field name, data type, and other properties.
Split fields to rows, is a step in the Transformation Plugin for Process Studio Workflows. This step allows you to split a row containing a delimited field into multiple new rows, one per split value.
The original field must be a string field. A new field name must be specified. If the value type/format of the new row is not specified, the new field will use the same type/format as the original field.
No.
Field Name
Description
1
Step name
Name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow.
2
Field to split
The field you want to split
3
Delimiter
The delimiter or separator used. Special characters (e.g. CHAR ASCII HEX01) can be set with the format $[value], e.g. $[01] or $[6F,FF,00,1F].
4
New name field
The name of the new field
String operations, is a step in the Transformation Plugin for Process Studio Workflows. String operations step performs operations, such as trimming, padding, InitCap and others to the string value.
No.
Field Name
Description
1
Step name
Name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow.
2
In stream field
Designate the field to transform.
3
Out stream field
Designate the name of the field to be created.
4
Trim type
Designate the trim type: none, left, right, or both.
5
Lower/Upper
Designate upper or lowercase.
6
Padding
Designate left or right padding.
7
Pad char
Designate the padding character.
8
Pad Length
Designate how long the padding will be.
9
InitCap
Transform to initial capitalization.
10
Escape
Define to Escape or Unescape XML, HTML, use CDATA or Escape SQL.
11
Digits
Designate whether to return remove, or do nothing to digits.
12
Remove Special character
Designate a special character to remove.
Strings cut, is a step in the Transformation Plugin for Process Studio Workflows. Strings cut step can cut a portion of a string based on a range of positions. If the range is invalid, it returns blank.
No.
Field Name
Description
1
Step name
Name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow.
2
In stream field
Name of the field whose substring to cut.
3
Out stream field
When a field name is given here, the step creates a new field with the substring. Otherwise the original field gets replaced by the substring.
4
Cut from
Designate where to begin cutting the substring. This value is 0-based, thus the first character in a string is 0.
5
Cut to
Designate where to end cutting the substring. This value is exclusive (1-based), so using a 1 includes the first character. The maximum length of the new string is Cut to minus Cut from.
Unique rows, is a step in the Transformation Plugin for Process Studio Workflows. The Unique rows step passes unique rows by removing duplicate rows from the input stream(s). It is a prerequisite that input stream is sorted; otherwise, only consecutive double rows are evaluated correctly. Unique rows (HashSet) step does not need the rows to be sorted.
No.
Field Name
Description
1
Step name
Name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow.
2
Add counter to output?
Check this option to add a counter field to the stream.
3
Counter field
Define the counter field name.
4
Redirect duplicate row
Processes duplicate rows as an error and redirect rows to the error stream of the step. Requires you to set error handling for this step.
5
Error Description
Sets the error handling description to display when duplicate rows are detected. Only available when Redirect duplicate row is checked.
6
Fields to compare table
Specify the field names on which you want to force uniqueness or click Get to insert all fields from the input stream(s) You can choose to ignore case by setting the Ignore case flag to Y. For example: Tea, TEA, tea are the same if the compare is performed as case-insensitive. In this instance, the first occurrence (Tea) is passed to the next step(s).
Unique Rows (HashSet) is a step in the Transformation Plugin for Process Studio Workflows. The Unique Rows (HashSet) step removes duplicate rows and leaves only unique row occurrences. The Unique Rows (HashSet) step tracks duplicates in memory and does not require a sorted input to process duplicate rows,
No.
Field Name
Description
1
Step name
Name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow.
2
Compare using stored row values
Stores values for the selected fields in memory for every record. Storing row values requires more memory, but it prevents possible false positives if there are hash collisions.
3
Redirect duplicate row
Processes duplicate rows as an error and redirect rows to the error stream of the step. Requires you to set error handling for this step.
4
Error description
Sets the error handling description to display when duplicate rows are detected. Only available when Redirect duplicate row is checked.
5
Fields to compare table
Lists the fields to compare---no entries means the step compares an entire row
Value Mapper is a step in the Transformation Plugin for Process Studio Workflows. Mapping is usually achieved by storing the conversion table in a database. The Value Mapper provides you with a simple alternative. The Value Mapper maps and replaces string values from one value to another.
No.
Field Name
Description
1
Step name
Name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow.
2
Fieldname to use
Field to use as the mapping source
3
Target field name
Field to use as the mapping Target
4
Default upon non-matching
Defines a default value for situations where the source value is not empty, but there is no match
5
Field values table
Contains the mapping of source value to converted target value