Set-PWDocumentState : Workflow rules not being executed

Question

Hello, 
 Looking for some help to understand why our Set-PWDocumentState commands do not trigger the WRE when we do state changes. 
 Our scripts boils down to : 
 
 New-PWLogin -DatasourceName "name" -LoadWRE -UserName "user" -Password $Password 
 $doc = Get-PWDocumentsByGUIDs -DocumentGUIDs GUI 
 Set-PWDocumentState -InputDocuments $doc -State "Next state in the workflow" 
 
 We also see the same kind of issue with New-PWDocumentVersion, just like the Set-PWDocumentState, we notice that the workflow rules have not been executed after execution. 
 Looking on the forums, we also saw the suggestion to use Invoke-WSGWorkflowCommand but that command gives the following: 
 Error: Manual change state not allowed. Please use Workflow customization rules to change document state. 
 
 Anyone has any pointers on how to investigate why the workflow isnt being triggered ? 
 
 Thanks !

AEC_PW_Interface · Accepted Answer

Just to confirm that it ended up working with Invoke-WSGWorkflowCommand 
 Our script boiled down to the below : 
 
 New-PWLogin -DatasourceName $datasource -UserName $username -Password $SecurePassword 
 $docs = Get-PWDocumentsByGUIDs -DocumentGUIDs "doc id" //or find the document how ever 
 $context = New-WSGClientContext -DisplayLabel $datasource -UserName $username -Password $SecurePassword -WsgURL "https://xyz.bentley.com/ws/" 
 Invoke-WSGWorkflowCommand -DocumentGuid $doc[0].DocumentGUID -CommandLabel $command -WSGClientContext $context -ReturnDocument 
 
 You must have good knowledge of the commands in your workflows but other then that, this works perfectly when you have server side WRE enabled. 
 Thanks again for the help everyone

Chris Andrew · Answer

Pwps_dab was updated recently to include a hidden -Force command on Set-PWDocumentState 
 This now works with Server Side WRE set.

Set-PWDocumentState : Workflow rules not being executed

Top Replies