Gareth Watkins Posted January 31, 2020 Posted January 31, 2020 I have built a process to log an incident based on an email received from a monitoring system using routing rules and templates, but it isn’t working. I had successfully tested the process a few weeks back when using my own email address and forwarding messages onto hornbill. The workflow kicked in and call journey progressed. After trying to raise calls using the correct email address, and changing the routing rules etc, the calls raise, but are not in the correct workflow. I cannot identify the workflow they raise under, but it isn't the one I have set in the routing rules/templates. Even changing the email address back to my own and sending test alerts now doesn’t work. I’m totally stumped, and sure it will turn out to be something simple, but desperately need to get these calls working by Monday next week in order to support our out of hours monitoring solutions.
Foley Coker Posted January 31, 2020 Posted January 31, 2020 Hello Gareth, we are experiencing the same problem. It follows the routing rule, but bypasses the routing rule template aside from the designated team. For us this is raising an incident call with no workflow as default rather than the service request call that the routing rule template points to in the service portfolio. I am unsure as to why this has occurred, as this has been working as intended up until a day or two ago.
Victor Posted February 2, 2020 Posted February 2, 2020 @Gareth Watkins @Foley Coker the behaviour you describe has recently been identified as a defect. From my understanding there will be a Service Manager update on Monday which will address the issue.
Martyn Houghton Posted February 3, 2020 Posted February 3, 2020 @Victor Is there a Problem reference for this defect? Cheers Martyn
Victor Posted February 3, 2020 Posted February 3, 2020 @Martyn Houghton yes, this one PM00161040. It's mentioned in the release notes for the latest build:
HGrigsby Posted February 3, 2020 Posted February 3, 2020 I have also noticed a problem with our routing rules, they now log an incident instead of the service request that they have always done. Helen
Guest Ehsan Posted February 4, 2020 Posted February 4, 2020 @HGrigsby, This issue was addressed in Build 1838 of the Service Manager application. Please update application on your instance. https://community.hornbill.com/topic/17675-new-update-hornbill-service-manager-1838/
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now