| Table of Contents |
|---|
| Anchor | ||||
|---|---|---|---|---|
|
...
- Annotations were used for each activity to explain the behavior of the activity
- The main sequence used for this workflow is Flowchart Sequence.
- The task workflow is starting with a connection to the Active Directory server, by using the ConnectToAD activity:
...
The activity outputs the user entry path and is stored in the variable UserEntryPath <String>.
- The next step of the task workflow is to obtain the group entry path using the same GetEntry activity.
...
The activity outputs the group entry path and is stored in the variable GroupEntryPath <String>.
- The next step of the task workflow is to add the user entry path to the group entry path using AddUserToGroup activity.
...
- Group is the entry path of the group stored in variable GroupEntryPath.
- User is the entry path of the user stored in variable UserEntryPath.
...
- The task workflow will finalize with a DisconnectfromAD activity:
...
- Annotations were used for each activity to explain the behavior of the activity
- The main sequence used for this workflow is Flowchart Sequence.
- The task workflow is starting with a connection to the Active Directory server, by using the ConnectToAD activity:
...
- InputValue is the value that will be displayed in Tracking Data.
...
- The next step of the task workflow is to iterate through the MembersCollection to display the members returned by GetUsersInGroup activity.
...
- MembersCollection is a variable of type <Collection<Collection<String>>>. In order to iterate each collection, two ForEach activities are required. The first ForEach activity will iterate through the main collection and it will be of type <Collection<String>>. The second ForEach activity will go through every subcollection of the main collection.
- The Member attributes are displayed on every cycle of the ForEach activity
...
- The task workflow will finalize with a DisconnectfromAD activity:
...
- Annotations were used for each activity to explain the behavior of the activity
- The main sequence used for this workflow is Flowchart Sequence.
- The task workflow is starting with a connection to the Citrix XenServer server, by using the ConnectToXenServer activity:
...
- Text is the value that will be displayed in Tracking Data.
...
- The task workflow will finalize with a DisconnectfromXenServer activity:
...
- Annotations were used for each activity to explain the behavior of the activity
- The main sequence used for this workflow is Flowchart Sequence
- The task workflow is starting with a connection to the VMware vCenter, by using the
...
- VirtualMachineID represents the id of the new created virtual machine.
- Write activity is used to display at the end of the workflow execution the value stored in variable NewVm_UUID:
...
- Text is the value that will be displayed in Tracking Data.
...
- The task workflow will finalize with a VMwareDisconnect activity:
...
- Annotations were used for each activity to explain the behavior of the activity
- The main sequence used for this workflow is Flowchart Sequence
- The task workflow is starting with a connection to the HyperV server, by using the
...
- Source Template Name represents the name of the template. The input value is provided via argument SourceTemplate <String>.
...
- VM Name is the name of the new virtual machine. The input value is provided via argument NewVMName <String>.
...
- VM Name represents the name of the new created virtual machine.
...
- The task workflow will finalize with a HyperVDisconnect activity:
...
- Annotations were used for each activity to explain the behavior of the activity
- The main sequence used for this workflow is Flowchart Sequence
- The task workflow is starting with a powershell script code using PSscript activity:
...
The Name property returned by the powershell command is evaluated with a Custom If activity:
In order to extract the Name property from the output returned and convert it to string, an Assign activity is used to store the Name property of the Process in ListProcesses collection:
- The next step of the task workflow is to get CPU property for the process with the name equal to the value stored in PSobj variable, using PSscript activity:
...