In order to provide a more consistent experience with the System Center product family, we've moved the Orchestrator blog to another blog at http://blogs.technet.com/b/orchestrator. Be sure to go there for all the latest info!
Note: The workflow sample mentioned in this article can be downloaded from the Opalis project on CodePlex: http://opalis.codeplex.com
A collection of Workflows that demonstrate how the Opalis Workflow Engine handles sets of data.
Launch the Workflow named ‘0.Setup’ by using Start or by running it using the Testing Console.
The Workflow will create a sample input.txt file on your C drive. The sample input.txt file will be used by the other Workflows and has following content:
1 2 3 4
1 2 3 4
This Workflow uses the Read Lines Activity to read all lines from the sample text file ‘input.txt’:
The Send Platform Event Activity displays the line text from the Read Lines Activity by subscribing to its Published Data:
Launch the Workflow by using Start, or by running it using the Workflow Testing Console. Check the Opalis Designer Events tab or the Testing Console log to see the resulting output:
There will be four Events, one for each line that is read from the sample text file ‘input.txt’.
This Workflow is the same as the Workflow named ‘1. Multi-Value Data’, except that the ‘Run Behavior’ properties of the Read Lines Activity is configured to flatten the multi-value Published Data and return a delimited string instead that uses ‘;’ as the separation character:
There will be one Event that contains the delimited string that was created by ‘flattening’ the multi-value Published Data from the Read Lines Activity.
This Workflow is the same as the Workflow named ‘1. Multi-Value Data’, except that there is an extra Compare Values Activity that filters the Published Data from the Read Lines Activity:
For comparison of numeric values, the proper Type needs to be specified in the General Properties of the Compare Values Activity:
The result from the Compare Values Activity is evaluated so that the Send Platform Event Activity will only trigger for values greater than 2. This is accomplished by using a Link Condition that is configured in the Link properties:
There will be two Events, one for each line that is read from the sample text file ‘input.txt’ and has a value greater than 2.