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 :
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 ?
Have you got Server Side WRE turned on? We see this issue with that.
AECOM Roads UK&I Digital Engineering, Design & Solutions Lead | Sector Information Management Lead
Principal Engineer – Digital
OpenRoads Designer 10.10 | MicroStation CE 10.16 | ProjectWise CE 3.4 | ContextCapture | ProjectWise PowerShell 2.0 | Generative Components | OpenBridge Designer 10.10
Revit 2022 | Civil 3D 2022 | Recap 2022 | Infraworks 2022 | Dynamo | Navisworks Manage
PowerShell | Visual Studio | Office 365 | Power Automate | Teams | SharePoint | Visio
Speckle | BIMVision | Revizto | Solibri
Yes, we have server side WRE turned on in our PW. Is there a way to trigger it from powershell ?
Not that I have found.
I have found the same. I was under the impression that the Set-PWDocumentState command doesn't trigger the WRE and so you would need to use other cmdlets alongside this to replicate the actions that are configured in WRE within your script.
See the thread below as well. Possible workaround to invoke the WRE commands via Web Services Gateway (WSG) and PWPS_WSG PowerShell module.Set-PWDocumentState enhancement