The following Activity shapes are included in the IWS Toolbox:
| Table of Contents | ||
|---|---|---|
|
Task Translator
...
Property | Description |
|---|---|
Name | Default is task_translator. |
Description | Text displayed below the shape in the workflow diagram |
Source | Location of the .ejmtsk file containing the definition of the translator. The field is read-only. |
Stream | Instead of creating the translator from scratch in the IWS, it is possible to assign existing Message Center stream to the shape. This should be done after dropping the shape onto canvas, while it is sill just a shell. |
OutParams | List of output parameters, to be used by further shapes/steps. It is not enough to simply populate the variables inside of the translator. Special coding is required to make them visible outside of the translator. |
Send notifications | This is a dropdown field. |
DataTaskEmailDistribution | This is a checkbox field. |
ResponseNotificationEmail | This is a checkbox field. |
ASKNotificationEmail | This is a checkbox field. |
File/Execution Count | Limit to the number of additional files to be processed. (Only applicable if begin shape has "allow extra files per load" option turned on.) |
Condition to Execute | Condition which will define when to execute the step and when not to. The default value is 1 (Yes) |
TSR Name | This is a dropdown field. |
| Result File Pattern | Pattern for the result file. |
| TSR Name | Options for Task Status Response (TSR) file name. Possible values are
|
TSRNamePattern | Pattern for Task Status Response file. |
| Single Incoming File Only | Indicator to only process one file even if multiple data files match the provided file mask. |
| Custom Parameters | List of the parameters to be visible inside the translator. They can be expressions based on TSR values or variables returned by prior steps. |
TSR Transform Stream | (advanced) This field allows you to use custom stream, which transforms the content and format of Task Status Response (TSR) message before sending it out. |
TSR Name Prefix | String literal which will be added to the beginning of the TSR file. |
ACK Name Prefix | String literal which will be added to the beginning of the ACK file. |
Custom TSR Location | Folder where TSR messages for current workflow should be delivered |
Custom ACK Location | Folder where ACK messages for current workflow should be delivered |
Comment | Text displayed above the shape in the workflow diagram |
MEMO | Arbitrary custom text. It can be used for any descriptive purposes. It is not displayed anywhere on the diagram. |
Task Loader
This activity shape is associated with loading data.
The following table describes the shapes' properties.
...
This dialog box opens when you right click this shape and select Properties:
Generic Extract and Transform
...
This dialog box opens when you right click this shape and select Properties:
ExecuteCM
This activity shape allows you to execute the Control Message as an EJM Task.
The following table describes the shape's properties.
...
This object generates a Message Center stream that removes duplicate records from an incoming file based on a key field. In addition the user can set filter and order by expressions. UnDup task is a separate workflow step that can be used in the same way as a Task Translator:
Format Settings
Use double mouse click on object to create a task. Entered name will be used for Solution Explorer tree item and generated Message Center stream:
Task Format popup will be opened once task was created. Set sample data and format settings:
Header lines (except the column header) and footer lines are excluded from output message by default. Use 'Include header lines in output' and 'Include footer lines in output' options to add them.
...
UnDup settings form will be generated for task:
Use Source object to update task format and Key, Filter, and Order By objects to set grouping and filtering settings:
The following table describes the shape's properties:
...
| Expand | ||
|---|---|---|
| ||
Let's create and publish a sample bundle-based workflow:
The sample file for it looks like this:
The second column is considered to contain the key expression. Workflow has been successfully executed:
|
