web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Activating Processes owned by other users fails. Deactivation Succeeds?

(0) ShareShare
ReportReport
Posted on by

So something seems to be weird with our CRM Security. I can't really tell how long it has  been this way, because I think there are two processes which I do not own.  Today I tried to activate one of those two and Got an error saying I lacked the prvCreateProcess Role. I checked and I am a System Administrator, System Customizer and have the CEO-Business Manager Role. 

  • I had no issues deactivating a process owned by another user
  • I could not reactivate the process I was able to deactivate owned by another user.
  • I was able to assign the process owned by another user to me and was then able to activate it.
  • I tried to assign the workflow I reassigned to me back to the original owner and could not
  • I had another owner create a new workflow and was able to activate that one.

This is a little odd. Not hyper critical, but I am concerned there may be something else wrong that is somewhat hidden. Can this type of behavior be explained or is it indicative of some issue?

*This post is locked for comments

I have the same question (0)
  • Verified answer
    mscrmba Profile Picture
    on at

    It's how it is.  It is how it is supposed to be acting.  There is nothing wrong.

    Background / What you might expect:

    Create Process privilege is separate to the Assign and Write (includes deactivate) privileges.  You can check the privileges for the Security Roles under the Customization tab > Process.  OOTB Systems Customizer has full privileges on Process, Process Configuration but only User level Create/Write/Assign on Process Session.  Systems Admin should normally be able to do everything.

    HOWEVER:  

    For workflows (and as if it sounds it acts exactly the same for Processes) there are some restrictions about who can do what - that override this OOTB approach to privileges.

    Please refer to this excellent blog by Gonzalo Ruiz:  gonzaloruizcrm.blogspot.com.au/.../processesworkflow-ownership-faqs.html

    Some extracts that directly respond to your questions:

    Qn: Why can’t I activate/deactivate someone else’s workflow, even if I am the system administrator?

    Ans: You want the workflow owner to explicitly acknowledge that a workflow will be activated and will perform some actions on his behalf. You would not want to allow another user (even the system administrator) to decide that some process should be executed on another user’s behalf. If you want to activate/deactivate someone else’s process you must first assign it to yourself.

    If I assign an activated process to another user, why does the user have to re-activate it?

    Ans: Active processes cannot be modified so the system automatically deactivates them before assigning it to the new user. As per Q3 above, only the new owner will be able to re-activate the process.

  • Community Member Profile Picture
    on at

    Thanks for the link. I'll give it a read.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
Wayne Walton Profile Picture

Wayne Walton 2

#2
Good.Panos Profile Picture

Good.Panos 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans