Monthly Archives: June 2014

One of the great things about work flows is that you can stop and start them. A workflow can be stopped, on a temporary basis, by using the Suspend-Workflow activity. workflow suspend1 {Get-Service Suspend-Workflow Get-Process }suspend1   This will run … Continue reading →

In my last post I questioned why commands from CDXML didn’t fail as thee weren’t any activities defined for them.  Turns out that functions and other commands that don’t explicitly have their own workflow activities are implicitly wrapped in the … Continue reading →

Last time we saw that you’re not really using cmdlets in PowerShell workflows – you’re using workflow activities. Some cmdlets haven’t been packaged into activities and for those you need to put them in an Inlinescript block.  You can also … Continue reading →

This is a simple function to return some data about a system: function get-serverdata { Get-CimInstance -ClassName Win32_OperatingSystem Get-Service Get-Process } get-serverdata   The function will return the CIM data about the operating system, then the service data and then … Continue reading →

I said in the first post in this series that you could force a workflow to perform tasks in parallel or in sequence. Starting with parallel you can force parallel execution by using the parallel keyword: workflow thursday1 {parallel {   … Continue reading →