Kelvin Posted August 4, 2021 Share Posted August 4, 2021 About 1 hour ago any self service ticket that comes through shows the site with the ID number and not the ID name. Is this as a result of an update or bug fix? Link to comment Share on other sites More sharing options...
David Hall Posted August 4, 2021 Share Posted August 4, 2021 Hi @Kelvin I'm not aware of any site specific changes in this latest update. I've had a look and tested locally and I don't appear to be able to replicate this issue for existing or newly logged tickets which all display the site name for me. As a first step I'd just like to confirm you have done the usual basics with a log out/clear cache/log back in and then see if the issue persists. After that perhaps confirm if any colleagues are seeing the same issue? Let me know if the issue persists. Kind Regards, Dave. Link to comment Share on other sites More sharing options...
Kelvin Posted August 4, 2021 Author Share Posted August 4, 2021 @David Hall I dont think this is the case as looking at the DB I can see Link to comment Share on other sites More sharing options...
David Hall Posted August 4, 2021 Share Posted August 4, 2021 Hi @Kelvin Thanks for that update.. indeed something is not correct there. So just to confirm those 2 incorrect entries that you have shown... were they logged via self service portal or via the Employee portal? Also just wanted to confirm whether the site in these cases is set via manual selection in the progressive capture or via a business process action? Regards, Dave Link to comment Share on other sites More sharing options...
Kelvin Posted August 4, 2021 Author Share Posted August 4, 2021 @David Hall These were logged via the self service portal and is captured during progressive capture This has been working since first live several months ago and has only stopped working today. Link to comment Share on other sites More sharing options...
David Hall Posted August 4, 2021 Share Posted August 4, 2021 Thanks @Kelvin Will take a further look now. Kind regards, Dave. Link to comment Share on other sites More sharing options...
David Hall Posted August 4, 2021 Share Posted August 4, 2021 Hi @Kelvin I've managed to replicate the issue and we now have a fix which is currently being reviewed/tested, we'll look to get it patched as soon as possible, most likely tomorrow morning. Kind Regards, Dave. Link to comment Share on other sites More sharing options...
Mike Hillman Posted August 5, 2021 Share Posted August 5, 2021 We've just noticed the same issue occurring, although we've only started to see it this morning - is there an update on the patch rollout? Link to comment Share on other sites More sharing options...
David Hall Posted August 5, 2021 Share Posted August 5, 2021 @Mike Hillman We're building the patch now so it should be rolled out this morning, I'll post back here once this has been done. Kind regards, Dave. 1 Link to comment Share on other sites More sharing options...
David Hall Posted August 5, 2021 Share Posted August 5, 2021 @Kelvin @Mike Hillman Just an update that the patch has just been deployed... sometimes it can take a few mins to be noticeable with caching etc but the issue should now be resolved... if you can keep and eye on it this afternoon and let me know how it goes. Kind Regards, Dave 1 1 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