Thanks To...
First I am happy to have the time to work on this stuff thanks to my employer:
Project Description
The FIM WF Activity for PowerShell makes is easy to use PowerShell inside FIM workflows.
The activity is also a good example of using diagnostic tracing inside FIM WF.
Who is this for?
The code sample in this project are interesting if you match the following:
- You have FIM 2010 deployed
- You want to take advantage of FIM 2010 workflow
- You prefer PowerShell Scripting to Windows Workflow Foundation development
The goal in this project was to use the minimum amount of .NET code in my FIM workflows, and the maximum amount of PowerShell.
FIM 2010 is a IT Pro product, so PowerShell made the most sense from an extensibility point of view.
Solution Components
FimCmExtensions.FimCmActivityLibrary.dll
A Workflow Activity that participates in FIM 2010 workflow by switching WorkflowData items for PowerShell variables
The name of the component has "CM" in it for two reasons:
- I am Craig Martin ;-)
- The project was originally started to simplify integration with FIM Certificate Management
Over the past few weeks I realized that this was an important component that was hidden in the other project, and that most people doing FIM WF might find this interesting, but would probably not naturally browse into the FIM CM Extensions project to find it.