Can Workflow be Accessed/Enforced on the Project Pro 2010 Client? RRS feed

  • Question

  • In reviewing Project Server 2010 workflows as a means to govern the use of templates and approvals for starting projects, the following questions arose as our current Project Manager base are heavy users of the MS Project Professional 2010 client for creating/maintaining project schedules...

    • Can workflows only be started from PWA or can they also be accessed from the MS Project Pro 2010 client?
    • Do workflows only govern projects initiated on PWA verses the client?
    • Can client users be limited to using defined workflows?
    • Is there any way to control what template get used to create/upload a project to Project Server 2010 from the MS Project 2010 client?

    We are looking to enforce the use of templates and an approval process for creating projects in Project Server 2010, but the majority of Project Managers use MS Project Professional only to create/upload schedules and PWA primarily for approving task updates from resources. I'm not seeing anything that defines how the client fits into the governance process when using workflows or whether client users can even access workflows. Looking for any input from others who may have dealt with this already.


    Rick Frisby

    • Edited by Rick VF Wednesday, September 12, 2012 4:05 PM
    Wednesday, September 12, 2012 4:01 PM

All replies

  • Some answers:

    - you can set a default Enterprise Project Type (EPT) that will be inherited by projects published from the client. That EPT can use a specific workflow

    - the workflow will govern Enterprise Custom Fields (ECFs) that are workflow controlled, but not necessarily the schedule. Some custom event handlers can be created for additional validation

    - workflows that are not defined cannot be used. There's no on-the-fly interface for creating workflows

    Hope this helps. |

    Wednesday, September 12, 2012 5:58 PM
  • Appreciate the response Catalin. Setting the default EPT with a workflow could be a viable option if all programs use the same template. However, may be an issue for some programs. Does only the default EPT get inherited by client projects or would the client recognize and use an EPT based on its affiliation to a department?

    Good to know about the workflow controlled ECFs. I'll have to experiment with that to see what happens in the client. Got it on the creation of workflows. We wouldn't want them to create any, just adhere to them, so that's actually a good thing.

    Good input that gives me someplace to start start experimenting. Thanks again for your response :) 

    Rick Frisby

    Wednesday, September 12, 2012 7:15 PM