| Anchor | _GoBack | _GoBack
|---|
| Table of Contents |
| Anchor | ||||
|---|---|---|---|---|
|
This category contains workflow templates and is deployed at Flowster Studio- Designer Basic installation.
| Anchor | ||||
|---|---|---|---|---|
|
This workflow adds a specified user to an Active Directory group.
General knowledge:
- 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 is starting with a connection to the Active Directory server, by using the ConnectToAD activity:
...
The output of the activity will be reflected in the Connection (ADConn) variable and it will be used for the rest of the Active Directory activities as an input.
- After the connection is made, the GetEntry activity will be used in order to retrieve the entry path of the user that will be added to the group:
...
The activity outputs the user entry path and is stored in the variable UserEntryPath <String>.
- The next step of the task 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 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 will finalize with a DisconnectfromAD activity:
| Anchor | ||||
|---|---|---|---|---|
|
This workflow lists all users members of a group in Active Directory.
General knowledge:
- 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 is starting with a connection to the Active Directory server, by using the ConnectToAD activity:
...
The output of the activity will be reflected in the Connection (ADConn) variable and it will be used for the rest of the Active Directory activities as an input.
- After the connection is made, the GetUsersInGroup activity will be used in order to retrieve a list of users members of a group:
...
The activity outputs the list of users and their selected attributes in Output parameter and stored in variable MembersCollection <Collection<Collection<String>>>. The number of results are returned by Output Rows Count parameter and stored in variable MembersCount<Int32>.
- Write activity is used to display at the end of the workflow execution the value stored in MembersCount
...
- InputValue is the value that will be displayed in Tracking Data.
- The next step of the task 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 will finalize with a DisconnectfromAD activity:
| Anchor | ||||
|---|---|---|---|---|
|
This workflow creates a virtual machine from a template. At the end of the workflow the new virtual machine is powered on.
General knowledge:
- 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 is starting with a connection to the Citrix XenServer server, by using the ConnectToXenServer activity:
...
The output of the activity will be reflected in the Connection (XenConn) variable and it will be used for the rest of the Citrix Xen Server activities as an input.
- After the connection is made, the VMCreateFromTemplate activity will be used to deploy a new virtual machine with a specified name from an existing template:
...
The activity outputs the UUID of the new virtual machine in variable NewVm_UUID<String>.
- 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 will finalize with a DisconnectfromXenServer activity:
| Anchor | ||||
|---|---|---|---|---|
|
This workflow creates a virtual machine from a template. At the end of the workflow the new virtual machine is powered on.
General knowledge:
- 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 is starting with a connection to the VMware vCenter, by using the
...
The output of the activity will be reflected in the Connection (VMConn) variable and it will be used for the rest of the VMware Server activities as an input.
- After the connection is made, the VMGet activity will be used to obtain the Template ID:
...
The activity outputs the id of the input template stored in variable Template_ID <String> .
- Template_ID value will be used in the next step, DeployVMfromTemplate:
...
The activity outputs the id of the new created virtual machine stored in variable
NewVM_ID <String>:
- The final step in the workflow flow is to power on the new created virtual machine using VM Power On activity:
...
- 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 will finalize with a VMwareDisconnect activity:
| Anchor | ||||
|---|---|---|---|---|
|
This workflow creates a virtual machine from a template. At the end of the workflow the new virtual machine is powered on.
General knowledge:
- 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 is starting with a connection to the HyperV server, by using the
...
The output of the activity will be reflected in the Connection (HyperV_Conn) variable and it will be used for the rest of the HyperV Server activities as an input.
- After the connection is made, the CreateVMfromTemplate activity will be used to create a new virtual machine from a source template:
...
- 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>.
The activity outputs the status of the activity.
- The next step is to power on the new created virtual machine using HyperVPowerOn activity:
...
- VM Name represents the name of the new created virtual machine.
- The task will finalize with a HyperVDisconnect activity:
| Anchor | ||||
|---|---|---|---|---|
|
This workflow uses powershell scripts to output the result of the Get-Process powershell command.
General knowledge:
- 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 is starting with a powershell script code using PSscript activity:
...
The output of the activity is stored in ListProcesses<Collection<PSObjects>>.
- The next step is to iterate through the collection of PSObjects in order to display the results of the powershell command using ForEach 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 is to get CPU property for the process with the name equal to the value stored in PSobj variable, using PSscript activity:
...