This feature has been implemented in version 2026.3.0
Implemented

Workflow documentation

2 votes

avatar

I've played with workflows some and have a decent grasp of $PSUItem and $Workflow. I haven't managed to get the "Deconstruct hashtable output" to anything that I can discern.

Any chance you can add some documentation to show what that setting does?

All Comments (3)

avatar
I've played with workflows some and have a decent grasp of $PSUItem and $Workflow. I haven't managed to get the "Deconstruct hashtable output" to anything that I can discern.

Any chance you can add some documentation to show what that setting does?


@mshepard70
I'm having the same experience and conclusions. I will come back to this thread with an update by tomorrow.

avatar

@mshepard70 - Kindly following up on this. The documentation has been updated here.

More

The setting applies to a Script that returns exactly one hashtable. Example:

@{
Server = 'web01'
Port = 443
}


Then map the Script parameters:

Server = $PSUItem.Server
Port = $Output.Port

The next script can then receive the mapped values normally:
param($Server, $Port)

"Server=$Server; Port=$Port"

I still have more to follow-up on this regarding mappings. I will have another update on this but hopefully this helps in the meantime.

dae22dfa-a6af-44e4-91c9-6653c1ea291a.png

avatar

Hello,

The fix has been implemented and is available in the latest version 2026.3.0.0 of PowerShell Universal.

Could you please confirm that this version works as expected now? We recommend testing this fix in a staging environment prior to deploying it on your production environment.

Thank you for your collaboration.

Best regards,

Maxim Robert

This feature has been implemented in version 2026.3.0