A developer incorporates the following steps into a build process: (1) the most recent source code is checked out from a source-code tool, (2) a new build is developed and run using in-house build scripts, (3) a unit test is executed to check the code, and (4) a notification is sent out to announce that the build has been completed. You will now generate a sample Workflow that mirrors this build process. The instructions in Table DW-1 will get you started.
Table DW-1 Naming a Workflow
|
Steps |
Actions |
|
1 |
Open the Workflow Explorer |
|
2 |
Right Mouse Click on "Private Workflow" and Select "New" |
|
3 |
Enter the name Sample Workflow in the New Workflow pop-up window. |
|
4 |
Click the Finish button. |
Your new Workflow will appear on the Workflow Explorer screen under Private Workflows. When you select your sample Workflow from the Workflow Explorer screen, four fields appear to the right of the screen: General Information, Data, Execute Settings, and Global Environment Configuration. These fields display the current attributes of your new Workflow. (Note that the Overview and Activities tabs appear on the lower left side of the Overview screen. You will access these two tabs later in this demonstration.)