locked
workflows - start with a record attribute change. RRS feed

  • Question

  • I've noticed that a workflow configured to run as above, will start with every update to the workflow's entity - irrespective of whether the trigger attribute has changed or not.

    Surely this is a bug..?


    T Sadikali
    Tuesday, July 5, 2011 12:56 PM

Answers

  • Yes, you are right it should read 'start when record attribute is updated'. Although it technically does not change, it is updated so the workflow will trigger. The workflow will not compare if the old and new values are the same

    Gonzalo | gonzaloruizcrm.blogspot.com

    Tuesday, July 5, 2011 1:42 PM
    Moderator

All replies

  • The workflow will not start if the trigger attributes have not been updated. However, each time that the entity is updated, a new job is started which is called the "workflow expansion task" which verifies whether or not to start the workflow. If the attributes selected have not been updated, at this point the workflow will not be started.

    Are you seeing that the actual workflow is executed?? If so, it could be because other plugins are updating the attribute or maybe the system is updating the attribute when you issue an "update".

     


    Gonzalo | gonzaloruizcrm.blogspot.com

    Tuesday, July 5, 2011 1:16 PM
    Moderator
  • Hi Gonzalo -

    What I think is happening is that because the entity is being updated 'as a whole' - as opposed to the update only including those attributes that have genuinely changed - the wf starts.

    In other words, the description 'start when record attribute changes' is false, because the engine is not actually detecting 'change', but rather just an update.

    E.g. consider a wf's entity is contact + it is configured to start when Address1City changes. Then an update to a contact is made including Address1City = London, where it already = London for the given contact. This will result in the wf starting.

     


    T Sadikali
    Tuesday, July 5, 2011 1:36 PM
  • Yes, you are right it should read 'start when record attribute is updated'. Although it technically does not change, it is updated so the workflow will trigger. The workflow will not compare if the old and new values are the same

    Gonzalo | gonzaloruizcrm.blogspot.com

    Tuesday, July 5, 2011 1:42 PM
    Moderator
  • ...and therefore this is a definate 'gotcha', if not a bug. I hope one of the product team picks this up. Thanks for the conversation, Gonzalo.

    Tamim.


    T Sadikali
    Tuesday, July 5, 2011 1:47 PM