@@ -16,13 +16,12 @@ Provides a brief introduction to the PowerShell Workflow feature.
1616## Long description  
1717
1818PowerShell Workflow brings the benefits of the
19- [ Windows Workflow Foundation] ( /dotnet/framework/windows-workflow-foundation )  to
20- PowerShell and enables you to write and  run workflows.
19+ [ Windows Workflow Foundation] [ 05 ]  to PowerShell and enables you to write and 
20+ run workflows.
2121
2222PowerShell Workflow was introduced in PowerShell 3.0 and the module is
2323available up to PowerShell 5.1. For more information about PowerShell Workflow,
24- see the [ Workflows Guide] ( /previous-versions/powershell/scripting/components/workflows-guide ) 
25- and [ Writing a Windows PowerShell Workflow] ( /previous-versions/powershell/scripting/developer/workflow/writing-a-windows-powershell-workflow ) .
24+ see the [ Workflows Guide] [ 07 ]  and [ Writing a Windows PowerShell Workflow] [ 08 ] .
2625
2726## About workflows  
2827
@@ -34,7 +33,7 @@ environments.
3433Workflows can be written in XAML, the language used in Windows Workflow
3534Foundation, or in the PowerShell language. Workflows are typically packaged in
3635modules and include help topics. For more information, see
37- [ XAML Overview (WPF)] ( /dotnet/framework/wpf/advanced/xaml-overview-wpf ) .
36+ [ XAML Overview (WPF)] [ 06 ] .
3837
3938Workflows are critical in an IT environment because they can survive reboots
4039and recover automatically from common failures. You can disconnect and
@@ -65,7 +64,7 @@ A PowerShell Workflow configuration consists of the following elements:
6564The workflow session isn't required, but is recommended. ** PSSessions**  can
6665take advantage of the robust recovery and Disconnected Sessions features of
6766PowerShell to recover disconnected workflow sessions. For more information, see
68- [ about_Remote_Disconnected_Sessions] ( ../../Microsoft.PowerShell.Core/About/about_Remote_Disconnected_Sessions.md ) 
67+ [ about_Remote_Disconnected_Sessions] [ 03 ] 
6968
7069Because the client computer and the computer on which the workflow session runs
7170can be managed nodes, you can run a workflow on a single computer that fulfills
@@ -122,11 +121,9 @@ To run a workflow, use the following procedure.
122121   Enable-PSRemoting -Force 
123122    ``` 
124123
125-    You can enable remoting by using the ** Turn on Script Execution**  Group Policy
126-    setting. For more information, see
127-    [ about_Group_Policy_Settings] ( ../../Microsoft.PowerShell.Core/About/about_Group_Policy_Settings.md ) 
128-    and
129-    [ about_Execution_Policies] ( ../../Microsoft.PowerShell.Core/About/about_Execution_Policies.md ) .
124+    You can enable remoting by using the ** Turn on Script Execution**  Group
125+    Policy setting. For more information, see [ about_Group_Policy_Settings] [ 02 ] 
126+    and [ about_Execution_Policies] [ 01 ] .
130127
1311281 .  Use the ` New-PSWorkflowSession `  or ` New-PSSession `  cmdlets to create the
132129   workflow session.
@@ -136,8 +133,8 @@ To run a workflow, use the following procedure.
136133   computer. This session configuration includes scripts, type and formatting
137134   files, and options that are designed for workflows.
138135
139-    Or, use the ` New-PSSession `  cmdlet. Use the ** ConfigurationName**  parameter to 
140-    specify the ** Microsoft.PowerShell.Workflow**  session configuration. This
136+    Or, use the ` New-PSSession `  cmdlet. Use the ** ConfigurationName**  parameter
137+    to  specify the ** Microsoft.PowerShell.Workflow**  session configuration. This
141138   command is the same as using the ` New-PSWorkflowSession `  cmdlet.
142139
143140   An alternative is to use the ` New-PSSession `  cmdlet. Use the
@@ -160,10 +157,10 @@ To run a workflow, use the following procedure.
160157   $ws = New-PSWorkflowSession @newPSWorkflowSessionSplat 
161158    ``` 
162159
163-    If you are an Administrator on the workflow session computer, you can use the 
164-    ` New-PSWorkflowExecutionOption `  cmdlet to create custom option settings for the 
165-    workflow session configuration. And, use the  ` Set-PSSessionConfiguration ` 
166-    cmdlet to change the session configuration.
160+    If you are an Administrator on the workflow session computer, you can use
161+    the  ` New-PSWorkflowExecutionOption `  cmdlet to create custom option settings
162+    for the  workflow session configuration. And, use the
163+    ` Set-PSSessionConfiguration `   cmdlet to change the session configuration.
167164
168165   ``` powershell 
169166   $newPSWorkflowExecutionOptionSplat = @{ 
@@ -204,13 +201,13 @@ To run a workflow, use the following procedure.
204201    ``` 
205202
206203   The following example runs the ` Test-Workflow `  on hundreds of computers. The
207-    ` Get-Content `  cmdlet gets the computer names from a text file and saves them in 
208-    the ` $Servers `  variable on the local computer.
204+    ` Get-Content `  cmdlet gets the computer names from a text file and saves them
205+    in  the ` $Servers `  variable on the local computer.
209206
210207   ` Invoke-Command `  uses the ` Using: `  scope modifier to define the ` $Servers ` 
211208   variable in the local session. For more information about the ` Using: `  scope
212209   modifier, see
213-    [ about_Remote_Variables] ( ../../Microsoft.PowerShell.Core/About/about_Remote_Variables.md ) .
210+    [ about_Remote_Variables] [ 04 ] .
214211
215212   ``` powershell 
216213   $Servers = Get-Content Servers.txt 
@@ -291,12 +288,26 @@ Some workflow common parameters are unique to workflows, such as the
291288** PSParameterCollection**  parameter that lets you specify different workflow
292289common parameter values for different remote nodes. For a list and description
293290of the workflow common parameters, see
294- [ about_WorkflowCommonParameters] ( about_WorkflowCommonParameters.md ) .
291+ [ about_WorkflowCommonParameters] [ 09 ] .
295292
296293## See also  
297294
298- -  [ Invoke-AsWorkflow] ( xref:PSWorkflowUtility.Invoke-AsWorkflow ) 
299- -  [ New-PSSession] ( xref:Microsoft.PowerShell.Core.New-PSSession ) 
300- -  [ PSWorkflow] ( xref:PSWorkflow )  cmdlets
301- -  [ Workflows Guide] ( /previous-versions/powershell/scripting/components/workflows-guide ) 
302- -  [ Writing a Windows PowerShell Workflow] ( /previous-versions/powershell/scripting/developer/workflow/writing-a-windows-powershell-workflow ) 
295+ -  [ Invoke-AsWorkflow] [ 12 ] 
296+ -  [ New-PSSession] [ 10 ] 
297+ -  [ PSWorkflow] [ 11 ]  cmdlets
298+ -  [ Workflows Guide] [ 07 ] 
299+ -  [ Writing a Windows PowerShell Workflow] [ 08 ] 
300+ 
301+ <!--  link references --> 
302+ [ 01 ] : ../../Microsoft.PowerShell.Core/About/about_Execution_Policies.md 
303+ [ 02 ] : ../../Microsoft.PowerShell.Core/About/about_Group_Policy_Settings.md 
304+ [ 03 ] : ../../Microsoft.PowerShell.Core/About/about_Remote_Disconnected_Sessions.md 
305+ [ 04 ] : ../../Microsoft.PowerShell.Core/About/about_Remote_Variables.md 
306+ [ 05 ] : /dotnet/framework/windows-workflow-foundation 
307+ [ 06 ] : /dotnet/desktop/wpf/xaml 
308+ [ 07 ] : /previous-versions/powershell/scripting/components/workflows-guide 
309+ [ 08 ] : /previous-versions/powershell/scripting/developer/workflow/writing-a-windows-powershell-workflow 
310+ [ 09 ] : about_WorkflowCommonParameters.md 
311+ [ 10 ] : xref:Microsoft.PowerShell.Core.New-PSSession 
312+ [ 11 ] : xref:PSWorkflow 
313+ [ 12 ] : xref:PSWorkflowUtility.Invoke-AsWorkflow 
0 commit comments