Melissa Gurney Posted January 25, 2017 Share Posted January 25, 2017 Hello, I am receiving the following error when trying to log a call through self service. The call logs but then fails as it is not successfully assigned to the team. This is the business process: Are you able to help me work out what is wrong? The correct BPM and PC are assigned to the catalog item and the team is added as a supporting team to the service. Thanks, Mel Link to comment Share on other sites More sharing options...
Victor Posted January 25, 2017 Share Posted January 25, 2017 @Melissa Gurney did you try to attach any screenshots to this post? I think it did not work, would you mind posting them again? Thanks! Link to comment Share on other sites More sharing options...
Melissa Gurney Posted January 25, 2017 Author Share Posted January 25, 2017 Hi Victor, Sorry about that I thought they had uploaded. Link to comment Share on other sites More sharing options...
Victor Posted January 25, 2017 Share Posted January 25, 2017 @Melissa Gurney dev team is looking into this Link to comment Share on other sites More sharing options...
Melissa Gurney Posted January 25, 2017 Author Share Posted January 25, 2017 Thanks Victor Link to comment Share on other sites More sharing options...
Melissa Gurney Posted January 25, 2017 Author Share Posted January 25, 2017 I seem to have sorted this now! Thank you for taking a look. Link to comment Share on other sites More sharing options...
Victor Posted January 25, 2017 Share Posted January 25, 2017 @Melissa Gurney ermm.. how? Link to comment Share on other sites More sharing options...
Melissa Gurney Posted January 25, 2017 Author Share Posted January 25, 2017 It was an issue with the SLA/priority rather than the assigning node It turns out it wasn't even making it to that point. Link to comment Share on other sites More sharing options...
Victor Posted January 26, 2017 Share Posted January 26, 2017 @Melissa Gurney ah, ok, I see... I saw something else in the logs from your instance (nothing to worry) but most likely it was not related to this error (which confused me). But happy is sorted now Link to comment Share on other sites More sharing options...
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