Jump to content

Josh Bridgens

Hornbill Users
  • Posts

    214
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Josh Bridgens

  1. @Dan Munns

     

    Any outgoing from us with these calls are being forwarded to a remedy instance and to an externally internal, not quite employee user/customer  (Genuine description I had)

     

    And they want to use the Remedy references, much to my dismay and fighting it they agreed they would.

     

    To avoid confusion for the users we have agreed to just have one reference and We would do the struggling of finding the calls etc. Thats why its in white in the body, as I thought it would pick it up.

  2. Hi @Steve Giller

     

    2 minutes ago, Steve Giller said:

    Firstly, the Rule checks for a match to see if the email needs processing; this can, using the correct variables, "see" the subject and the body amongst other things. This part may be failing because in your original post you are looking in "summary" rather than "subject"

    I realised that afterwards and changed it after re-looking at the original request updater we have, apologies.

     

    3 minutes ago, Steve Giller said:

    Secondly the Operation checks to see if there is a Hornbill Reference in the subject line - this is where your rule will always fail because your Hornbill Reference is in the body, and the Operation is not looking there.

    Is there any way to fix this?

     

    I'm at a loss here.

     

    Josh

  3. Morning All,

     

    We have a strange setup for one certain type of call while we are mid transition of a phone contract, unfortunately we are having to use the third parties call references for any outbound and inbound email.

    Obviously this is not what we wanted however they have stressed they are not prepared to work with us without this.

    I thought I could get round this by having our reference number for customer updated in the body of the email, but in white text so its not actually readable unless people go looking... this isnt working.

    The routing rule I have setup is as follows:

    image.png.d42b3a425bd3f324861a42503f82eae0.png

    The Template We are sending out is very barebones as we have had to strip off all branding for now for these calls, however I have highlighted where our reference shows in white:

    image.png.e5f6b25ee821f6aa22d98c9d8aa0092d.png

     

    Is there any reason this may not be working?

     

    Josh

     

  4. Hi Steve, 

    3 hours ago, Steven Boardman said:

    Could you go into the PFC, move any node, and then re-save the PCF process and try it again and let us know how you get on?

    Tried it, unfortunately getting the same problem :( 

     

    Not sure if my assets are incorrect or something, but theyre definitely tied to this user.....

     

    Thanks for the help.

     

    Josh

  5. Hi All,

     

    Am I losing my marbles, or am I missing a way to automatically link calls to a Problem, or change through the BPM??

    I know we can update linked calls, however I have a Catalogue that when used needs to automatically link the call to a Problem we have logged....

     

    Josh

  6. Hi @dwalby,

     

    A lot of this is me slowly losing my mind...

    3 hours ago, dwalby said:

    In terms of the below are you asking what 'Service' it would be logged against? 

    Questions like these are probably things the users will decide for themselves I imagine!

    I've recently put forward a proposal of the new Services with a more friendly look and a LOT more catalogues underneath, I'm hoping this will get the ball rolling and we can start working in a more customer oriented manner.

     

    Time will tell.

     

    Josh

    • Like 1
  7. Hi @Victor,

     

    Unfortunately I was driving home when I had the phone call saying nobody could connect and had to madly pullover to do an instance check, completely forgot to get a screenshot.

    I do remember the XMLMC Session bind was failing with over 5000+ ms ping, if that helps?

    Josh

×
×
  • Create New...