Automation: Activity output object properties exposed to simplify graphical runbook authoring
16 March 2016
When you author graphical runbooks in Azure Automation, a common pattern is to use the output of one activity as the input to a later activity. Previously, the UX allowed selection only of the entire output object. Any properties of the object needed to be discovered independently and entered manually. Now the UX exposes the property hierarchy of the activity output objects so that you can choose to use a selected object property as input to an activity. This is a big time saver when you're authoring graphical runbooks. Currently, the properties are exposed for cmdlets that have the OutputType attribute set. To learn more about setting OutputType in your PowerShell cmdlets so that they can be used easily in graphical runbooks, refer to the about_Functions_OutputTypeAttribute article and the OutputType Attribute Declaration article.