Hornbill Users
  • Content count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About Awalker

  • Rank
    Advanced Member

Profile Information

  • Gender
  • Location
    Taunton, Somerset
  1. @Victor Thank you for all your help on this, greatly appreciated.
  2. Hi @Victor, Oddly i am unable to replicate the issue now, I have gone back to the original process and it seems to be working 100%.
  3. HI @Victor, This is odd, I have re-raised a CR using the original process, but pointed it to my test team instead of the Change management team and it worked absolutely fine. I have since removed that node ad added a stage checkpoint and re-raised a CR and again it worked fine.
  4. @Victor I will get onto this this afternoon, and feedback. Many thanks
  5. HI @James Ainsworth, Any update on this at all??
  6. @Victor Thank you for the help in updating the BP, the requested change now works as intended, however: - The process now fails once a change is updated to Implemented, Can you please help me identify why this is as i am unable to confirm this nor can i find further description of the error in the log files as the filter does not seem to work. Error Attached.
  7. @Victor i will run some tests now to see if this process has returned from the dark side
  8. @Victor, the force runs strong through your scenarios, these are correct.
  9. @Ehsan, yes this was on, i have now switched this off, as assume that will resolve my issue?
  10. Hello, I have a process for developers to follow when requesting elevated access, as part of this process it requires authorisation to which i have used the authorisation node, however today when a request was raised it was approved by an analyst (Graham) that was not in the authorises list within the process, can you confirm how this was possible and what i need to do to rectify this asap. Screenshot attached of users who can authorise this
  11. @Victor excellent really appreciate your help on this, would be good to get this nailed Hope all is well.
  12. HI @Victor, Apologies, its looks as though it has worked, but it is working the wrong way round. As part of my Process the first step once a change request has been raised is someone assigned to the change team needs to assign it to an analyst, the process then stops the assigned analyst from approving the change, whereas what i am trying to do is to stop the customer who raised the request from having that ability, as currently they still can. if that makes sense?
  13. Hi @Victor, Did you manage to take a look at the above?
  14. @Victor CH00000122
  15. Hi @Victor, A change request was raised by David Finn, he has has 60% approval assigned to him via the authorisation node, when the CR got to the point of approval, he still had an activity assigned to him for approval and he was able to progress the CR.