locked
workflow scope RRS feed

  • Question

  • Hello - I had a question about workflow Scope in CRM. I read the following article online as a primer:

    http://info.profad.com/bid/71873/Defining-Scope-using-Workflows-in-Microsoft-Dynamics-CRM-2011

    It looks like "Organization" is the broadest scope.  Is this the scope you set most often - ex - make sure the workflow always runs for all users across the organization?

    What are some scenarios in which you require a more limited scope and how often do you find yourself needing to enforce a more limited scope for workflows?

    Thursday, January 24, 2013 6:31 PM

Answers

  • I use a more limited scope when I only want the workflow to run on records owned by a particular group of users. For example, Business Units A and B have different sales processes, so they each have workflows which are 'Business Unit' in scope. I use 'User' scope to test my workflows.

    Neil Benson, CRM Addict and MVP at Slalom Consulting. Find me on Twitter. Join over 20,000 other CRM professionals on the Microsoft Dynamics CRM group on LinkedIn.

    Thursday, January 24, 2013 8:33 PM
    Moderator
  • Remember that the scope of the workflow is set by the owner of the workflow and not by the executer of the workflow.

    So if the request is to send an email to the assignee no matter WHO that person is, and no matter who executed the workflow, then you need to set the scope to Organisation.

    But if its only a single person that can be allowed to send out these emails.. then the workflow should be set with that person as owner and the scope set to user.


    Rune Daub Senior Consultant - Dynateam CRM http://www.xrmmanagement.com

    Thursday, January 24, 2013 9:48 PM

All replies

  • I use a more limited scope when I only want the workflow to run on records owned by a particular group of users. For example, Business Units A and B have different sales processes, so they each have workflows which are 'Business Unit' in scope. I use 'User' scope to test my workflows.

    Neil Benson, CRM Addict and MVP at Slalom Consulting. Find me on Twitter. Join over 20,000 other CRM professionals on the Microsoft Dynamics CRM group on LinkedIn.

    Thursday, January 24, 2013 8:33 PM
    Moderator
  • It does happen quite often that my customers use the user scope.

    Especially for manual run workflows that should only be runned by individual users.

    It really does come down to.. how extensive is the implemented security model.


    Rune Daub Senior Consultant - Dynateam CRM http://www.xrmmanagement.com

    Thursday, January 24, 2013 8:49 PM
  • Please consider the following scenario:  "When a Request is assigned send an email to the assignee."

    In a scenario like this doesn't it make sense to set the workflow Scope to Organization?  It seems like this type of workflow should happen for every instance of the scenario with no conditions/restrictions on scope.  Do you agree or is there another perspective I'm not considering here?

    Thursday, January 24, 2013 9:15 PM
  • Remember that the scope of the workflow is set by the owner of the workflow and not by the executer of the workflow.

    So if the request is to send an email to the assignee no matter WHO that person is, and no matter who executed the workflow, then you need to set the scope to Organisation.

    But if its only a single person that can be allowed to send out these emails.. then the workflow should be set with that person as owner and the scope set to user.


    Rune Daub Senior Consultant - Dynateam CRM http://www.xrmmanagement.com

    Thursday, January 24, 2013 9:48 PM