will.good Posted March 20 Share Posted March 20 Hi, Is there any reconciliation going to happen to recode the cases that report incorrectly because of this defect? We have around 2500 cases that are incorrectly coded because of this, and don't really think we should have to code these again from our end (+ would not have the time to ). Affects our reporting more than anything, so would be good to see this rectified. Link to comment Share on other sites More sharing options...
Estie Posted March 21 Share Posted March 21 Is there any further information about this defect? I cannot see it in the published defects list. Not sure what the closure category separator is? Link to comment Share on other sites More sharing options...
Paul Davis Posted April 11 Share Posted April 11 @Stefania Tarantino This defect was resolved in the Service Manager build that was released on 6th March. We only had Will who had indicated that he was particularly affected by this issue, and so could only directly notify him directly of its resolution. Details were, of course, included though in the release notes in the admin area and on the forum for the benefit of everyone else. Hope that helps. 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