KE00175731: Incorrect request closure category separator when category is set by workflow

[will.good]

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.

 

[Estie]

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?

 

[Guest Paul Davis]

@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.

[will.good]

Please can I have a response on whether any reconciliation can be done to correct the incorrect coding caused by this defect?

[Michelle]

@will.good I will raise a request with our services team to understand if it is possible to address the incorrect coding caused by the defect for the cases impacted.