PrimalSens not working for workflow

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
This topic is 7 years and 9 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
User avatar
arjanbroeke
Posts: 44
Last visit: Wed Apr 11, 2018 6:50 am

PrimalSens not working for workflow

Post by arjanbroeke »

Product, version and build: PS2016 5.2.123
32 or 64 bit version of product: 64-bit
Operating system: Windows 10
32 or 64 bit OS: 64-bit
PowerShell Version: 5

When defining a workflow with parameters, the parameters are not shown in PrimalSense, I've tried all three the options for the Cmdlet Primalsense setting.

I've for example defined:
  1. workflow Get-VMMDisk {
  2.     param (
  3.         [Parameter(Mandatory = $true)][string]$VMName
  4.     )
But when calling the workflow in the script, the workflow name is in the PrimalSense, but the parameters are not.


Cheers,
Arjan
User avatar
davidc
Posts: 5913
Last visit: Mon Jul 08, 2019 8:55 am
Been upvoted: 2 times

Re: PrimalSens not working for workflow

Post by davidc »

Thank you for reporting this. This issue will be resolved in the next service release.
David
SAPIEN Technologies, Inc.
This topic is 7 years and 9 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.