• State Suggested Answer
  • +2 person also asked this people also asked this
  • Replies 21 replies
  • Answers 1 answer
  • Subscribers 67 subscribers
  • Views 6465 views
  • Users 0 members are here

Set-PWDocumentState enhancement

Peter Willmen
Offline

Would it be possible to add an 'Admin Override' option to the 'Set-PWDocumentState' command in PW PowerShell?. This option should only be useable by members of the Administrator group or by using a '-AdminOverride' option

When this function is used on an object managed under the Workflow Rules Engine (WRE) it returns a 58268 error ("Manual change state not allowed. Please use Workflow customization rules to change document state")

Access to this additional option is required for system Administrators to fix problems with WRE where on occasion the rule action times-out and the file is left in the wrong state. This can be caused by a number of things such as large/corrupt files or even a slow network connection.

I know this can be achieved by editing the database entries but I need a managed function that can be configured to achieve the result in a consistent and controlled manner.

Parents
  • 0 Offline

    Hi Peter/all.

    With COVID-19 and home working, we are seeing more occurrences of workflow failing/timing out, which leaves the file in the wrong workflow state, (versions are sometimes wrong, or initials missing as well).

    I don't see any change to the Set-PWDocumentState command in terms of an 'Admin over-ride'.  Is there any quicker way I am missing to get the State manually changed/reverted when using WRE or is it still a manual hand-cranked fix every time?

    As we dont have easy write access to the Datasource DB, we are having to edit the WRE spreadsheet every time, to allow the file to be fixed, and then put the WRE rules back again, which is time consuming and adds risk.

    Any advice appreciated.

    Thanks.

    Jim

Reply
  • 0 Offline

    Hi Peter/all.

    With COVID-19 and home working, we are seeing more occurrences of workflow failing/timing out, which leaves the file in the wrong workflow state, (versions are sometimes wrong, or initials missing as well).

    I don't see any change to the Set-PWDocumentState command in terms of an 'Admin over-ride'.  Is there any quicker way I am missing to get the State manually changed/reverted when using WRE or is it still a manual hand-cranked fix every time?

    As we dont have easy write access to the Datasource DB, we are having to edit the WRE spreadsheet every time, to allow the file to be fixed, and then put the WRE rules back again, which is time consuming and adds risk.

    Any advice appreciated.

    Thanks.

    Jim

Children

Communities
Support and Services
Training and Learning
Social Media