• Industries
  • Products
  • Buy
  • Services & Support
  • Communities
  • Discussion Groups

    Autodesk PLM 360

    Reply
    Product Support
    Posts: 258
    Registered: ‎03-27-2012

    Does a Workflow need approval from all users in the tenant?

    58 Views, 2 Replies
    06-21-2012 06:20 AM

    Can you create a Workflow that does not need approval from all users in the tenant?



    John Hill
    Support Specialist
    Product Support
    Autodesk, Inc.
    Please use plain text.
    Product Support
    Posts: 258
    Registered: ‎03-27-2012

    Re: Does a Workflow need approval from all users in the tenant?

    06-21-2012 06:21 AM in reply to: JohnCHill

    Yes, you can set the approval on the workflow from very granular to one or all users.



    John Hill
    Support Specialist
    Product Support
    Autodesk, Inc.
    Please use plain text.
    Employee
    broepke
    Posts: 103
    Registered: ‎01-24-2004

    Re: Does a Workflow need approval from all users in the tenant?

    06-21-2012 07:05 AM in reply to: JohnCHill

    Some additional tips. Two key ways to enable this are to leverage scripts that are already present in the default tenant.

     

    1. Set "GenIsOwner" as a condition script on any workflow that requires just a single sign off and then ensure that the record owner is set to the person you want to sign off on the record. This is also very useful in controlling what items show up on people's Outstanding Work List

     

    2. The second is the "Multi-Approval" board scripts that we included. This is a very reusable method for creating a workflow step that requires multiple people fully approve a state before moving on. Examples of how this is configured is in many workspaces today - Consider looking at the "Change Orders" workspace. 

     

    Extra Tip - This is very simple to recreate in any workflow.  Simply make sure that each of the "Transitions" that are coming out of your state are named exactly as the examples (Approve, Reject, Final Approaval, Cancel) to ensure the scripts work - then on each of those transitions, set the matching script.  The Cancel step is optional.  The State name itself can be named anything you like.

     

    Capture.PNG



    Brian Roepke
    Director of Product Lifecycle Management
    Autodesk, Inc.

    Please use plain text.