3 Replies Latest reply on Aug 7, 2015 8:50 AM by Jenny.Lardh

    Change Assignment Loop

    Dan Apprentice

      I'm using the OOTB 'Approvals' child object and associated 'Approve' action in my Change Management process.  The action has an associated window that allows you to specify a builder that the change will be assigned to (this is a link to the System\User Object), the next action in the process is an Assign/Reassign that uses 'Process/_Approvals/_Builder' runtime value for the action and this then assigns the Change to that analyst.  This works the first time to take the approve action.


      I have added a loop into my process that allows a Change to go back to the CAB for approval (we have people who make modifications to the specification of a change that I feel should mean the change is 're'approved by the CAB before the building of the change goes any further), the action is then taken to 'Approve', the window comes up and allows you to input a builder, but it uses the previous loops input in the next Assign/Reassign that happens.  Each time it goes round the loop the assignment goes to the previously selected user.  I'm not sure why or if i'm trying to make it do something it was not designed to do.  Any help would be appreciated.


        • 1. Re: Change Assignment Loop
          Jenny.Lardh SupportEmployee



          Is the Approver a collection action? Does the Approver Object contain a Date attribute with a persistence type of "Creation"?

          If you use runtime values from a collection object you will need to have a data time attribute with the create persistence type or the system will not know which order the collections where created in and will continuously pick the first one.


          Kind Regards,


          1 of 1 people found this helpful
          • 2. Re: Change Assignment Loop
            Dan Apprentice

            I added a "Create Date" attribute with a persistence type of "Creation" and it's solved the issue.  Easy when you know how I guess, many thanks for your help


            Just a note, I had to modify the records already in the and put dates into the new attribute as existing changes that went back through the loop error'd  when adding an approval.  Presumably something to do with the way the runtime values are derived using the date from that new attribute?

            • 3. Re: Change Assignment Loop
              Jenny.Lardh SupportEmployee

              Yes, the runtime value would look at this attribute, so if you had any records where this hadn't been filled in you would most likely get an error message.

              Modifying the already existing records though should solve it for you.