Jump to content

MichelleReaney

Hornbill Users
  • Posts

    47
  • Joined

  • Last visited

Posts posted by MichelleReaney

  1. Thanks Steve, This would mean adding about 15 extra nodes in the BPM for each time it expires was hoping for a simpler option. 

    Haha, I don't think just closing them without out at least chasing would go down too well :) We are trying to automate the requests to take the work away from service desk but if no authorisation is received then currently they just sit there waiting. 

  2. Is there a way of sending automated chase emails to the approver (cc in requestor) if the request has not been approved after say, 1 week, a different email after 2 weeks, then final email after 3 weeks to say the call will be resolved as no authorisation received.

    I was thinking about setting an expiry on the authorisation then sending a chase email but we would need to do this for each week so this will add a large number of entities to some already crowded BPM's.  

    Has anyone come up with a better way of doing this?

     

  3. On 12/10/2021 at 11:34 AM, Alberto M said:

    Thanks for this explanation, @samwoo.

    As we have around 150 services and our change, problem and known error request types have no catalog items, we needed to turn this setting off.

    It would be nice to have this setting separated for each request time.

     

     

    On 12/10/2021 at 11:51 AM, lee mcdermott said:

    @Alberto M

     

    yes with 150+ services that would be a massive amount of time and effort to setup a catalog item for each one just to get them working again.

     

    On 12/10/2021 at 11:44 AM, lee mcdermott said:

    thanks all for the info.

     

    we dont have any catalog items defined for changes or problems either so explains why it has stopped working.

     

    so to clarify is the resolution to create a catalog item or can this setting just be disabled?

     

    and where about is this setting (whats it called)?

     

    thanks

    lee

    Hi Both, 

    To make you aware we changed this setting to off as PM and KE had no catalogue items defined and this fixed it for these.

    However we have now noticed that with this setting off if an agent is logging a ticket in the agent portal then they are not required to select a catalogue item anymore.  

    It will let the agent continue with out selecting a catalogue item for that service and then errors at the end so they are unable to log a ticket.

    Something to check 

     

     

     

     

  4. We have a routing rule set up to create a new incident when an email is received from a specific external sender.  This has been working fine until some time between 03/12/2021 and 05/01/2022.  

    We have not changed anything in our systems.  I have looked at the guidance in here and we do not have a contact/user set for this email address and app.email.routing.rules.unknownUsers.allow is set to off but this has always been the case so I don't understand why it has suddenly stopped working.  

     

     

  5. We have an issue where some of the answers to a specific progressive capture are not showing in the questions section of the SR once it has been logged. 

    Once the Progressive capture has been completed, the majority execute successfully but some show all the answers in the SR and some don't. 

    Others fail with an error of no matching gotoif found and need to be moved on manually by completing the answer manually

    image.png.c83ec2035c7921795fa1050c9316a946.png

     

     image.png.18bc0ca27069b1b0b02bedb6e6284e59.png

  6. Thanks Jeremy. Might be something we have to look into if we cannot find a fix but this should not be needed as it should just work.

    They do work for a time and then stop working? URL says DNS_PROBE_FINISHED_NXDOMAIN I have tested this externally and still cannot see the images so it is nothing internal to us causing it. 

     

×
×
  • Create New...