Nintex Community Menu Bar

NTX PowerShell Action - Stable Release

Features

Robust security features based on Windows Remote Management.
Ability to execute PowerShell scripts from any machine allowing Remote Management from your SharePoint servers.
PowerShell exceptions are handled so workflows are unaffected.
OpenSource
Actively Developed
Automated Installation Routine

Planned Features

Async PowerShell script execution
Script Repository
Run worker as a centralized SharePoint service instead of in Workflow Infrastructure
Pass SPServer object to PowerShell session for determining executing server.

Current roadmap/planned features can be found here.

Downloads

Disclaimer: As stated in our Terms of Use, Nintex is not responsible for any third-party content made available for download on Nintex Connect, whether or not this content has been reviewed and/or moderated by Nintex and regardless of who originated that content (including, but not limited to, Nintex employees, partners, affiliates, or moderators). Users shall assume all risks associated with applications and other content provided on Nintex Connect. Nintex does not provide support for any content and plugins provided for download at communities.nintex.com.

NTX - Home

Source Code

Source Code (Archive)

Source Code on Github

Screen Shots

Page 2 / 3

I am not sure, but it would certainly appear so. Does everything else function correctly in the legacy sites?

Cheers!

Aaron

Actually, no. I just tried to query for some other native Nintex action and I am getting the same thing I see with the Powershell action. What does it mean to "Contact your administrator to enable"? If I know how to do this, I think I can get the Powershell custom action working, too. I cannot find instructions on how to resolve this.

Thank you for your attention!

In Central Administration there should be a section where you can manage Nintex Actions. I suspect that you need to click the checkboxes for the actions that you wish to enable for the farm.

Note: You should be able to break permission inheritance for this at various stages of the hierarchy if you need more granular control later on.

Try replacing localhost with the machine name.

Cheers!

Aaron

We have the same Problem We cant call SharePoint Objects:

Cannot access the local farm. Verify that the local farm is properly configured, currently available, and that you have the appropriate permissions to access the database before trying again.
+ CategoryInfo : InvalidData: (Microsoft.Share....SPCmdletGetWeb:SPCmdletGetWeb) dGet-SPWeb], SPCmdletException
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletGetWeb

Did you find any solution

Does this solution require PSRemoting?

Hi Richard,

This solution requires Microsoft WinRM framework to function.

Any plans to move this project elsewhere when codeplex shuts down? or should I save my copy in my virtual safebox?

Hi ‌

any chance to get this working with nintex 2016 ?

But what do I insert in the "PowerShell Script" richt text box, when my PS script is laying on the server?

already tried:

C:FolderSubfolderScript.ps1 -Param1 "NintexWFVar" -Param2 "NintexWFItemProp"

...but nothing happens.

I hope u understand what I mean.

Can somebody give me a hint please?

Greets Martin

I my powershell script I have....

Function myFunc

{

....do something....

}

Export-ModuleMember -function myFunc

Then in the workflow action i do:

Import-Module -name c:fullpathfile.name myFunc -param1 "value" -param2 "value"

/Martin

Thanks for the fast reply.

Unfortunately this does not work in my case and I am not getting any errors.

When I simply open the shell on the server and paste C:FolderSubfolderScript.ps1 -Param1 "NintexWFVar" -Param2 "NintexWFItemProp", the script will execute as expected.

Could it be any reason my script is designed?

This is my script::

param(
   �string]$DestWebURL,
   �string]$PCGroup,
   estring]$ProductName
)
if(!(Get-PSSnapin Microsoft.SharePoint.PowerShell -ea 0))
{
Write-Progress -Activity "Loading Modules" -Status "Loading Microsoft.SharePoint.PowerShell"
Add-PSSnapin Microsoft.SharePoint.PowerShell
}
function AddFileShareLink{
   #Get Web
   $w = Get-SPWeb $DestWebURL
   #Get Placeholder
   $node = $w.Navigation.Quicklaunch | where {$_.Title -eq "FS2Link Placeholder"}

   #Check Placeholder Existence
   if($node){
       #Build FS-Link
       $fsLink = "file://fs2srv/_SP_Product_Center/" + $PCGroup + "/" + $ProductName
       $fsLinkName = "FS2SRV " + $ProductName;
       $fsNode = New-Object Microsoft.SharePoint.Navigation.SPNavigationNode($fsLinkName, $fsLink)

       #Add to Quicklaunch
       $w.Navigation.Quicklaunch.AddAsLast($fsNode)
       #Move New Node Position
       $fsNode.Move($w.Navigation.QuickLaunch, $node)
       $node.Delete()
   }
}
AddFileShareLink

Don't know if you got it working in the meantime, but I realize I forgot to mention my script is in a .psm file, powershell script module, and please pay notice to the -ExportModuleMember after the main function.

Hi Martin,

Thanks for your reply. I tested a simple Script which accesses the SP PS CMD-Lets and should just return me the list count of the website.

I tried it with a normal *.ps1 and your variation as ps module, but both weren´t working.

Here is the module code:

Param(
�string]$Url
)

function TestMe{
Add-PSSnapin Microsoft.SharePoint.PowerShell

$w = Get-SPWeb($Url)
$count = $w.Lists.Count

return $count
}
Export-ModuleMember -function TestMe

Here the line i wrote in the ntx wf action:

Import-Module -Name C:BatchTestMe.psm TestMe -Url "http://intranet"

The funny thing at this point is, when i only let the action return the SPWeb-Object, it works:

But trying to access the properties of the SPWeb object is never working. Can anyone explain this?

Hi Aaron Labiosa‌,

I am getting an error message when I publish my workflow where I have added a PowerShell Action. Do you know how to solve this problem?

soap:ServerServer was unable to process request. --> Failed to

publish workflow: <Error> <CompilerError Line="0" Column="10"