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 ?
Ok, thanks everyone !
I will try again with the PWPS_WSG even though it dint work earlier but honestly I think we will just reimplement the workflow rules inside the script.
If PWPS_WSG ends up working, ill reply with the solution to help contribute
Just to confirm that it ended up working with Invoke-WSGWorkflowCommand
Our script boiled down to the below :
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
Answer Verified By: AEC_PW_Interface
Pwps_dab was updated recently to include a hidden -Force command on Set-PWDocumentState
This now works with Server Side WRE set.
AECOM Roads UK&I Digital Engineering, Design & Solutions Lead | Sector Information Management Lead
Associate Director – Digital
OpenRoads Designer 10.12 | MicroStation 2023 | ProjectWise CE 10.3.4 | ContextCapture | ProjectWise PowerShell 2023 | ProjectWise WSG API | Generative Components | OpenBridge Designer 10.12
Civil 3D 2023 | Dynamo | Navisworks Manage
PowerShell | Visual Studio | Office 365 | Power Platform | Teams | SharePoint | Visio
Speckle | BIMVision | Revizto | Solibri