Conflict between ISESCALATE and INV_TIME_TO_NEXT_ESCALATION in the status table
by dymitrruta - Tuesday, June 2, 2020, 19:39:42

Dear Organizers, I noticed that in the status table after a sequence records with ISESCALATE=true and the corresponding INV_TIME_TO_NEXT_ESCALATION=1 for the same refid there are many subsequent records with ISESCALATE=false but still INV_TIME_TO_NEXT_ESCALATION=1. I thought escalation state (ISESCALATE=true) always implies INV_TIME_TO_NEXT_ESCALATION=1 and vice versa. Example for REFERENCEID=101042. Could you please check and explain? Many thanks.

RE: Conflict between ISESCALATE and INV_TIME_TO_NEXT_ESCALATION in the status table
by andrzej - Wednesday, June 03, 2020, 10:41:53

Thanks for the notice!

Those values are indeed wrong. We corrected them (we changed the INV_TIME_TO_NEXT_ESCALATION values in cases when the escalation ended and there ware no further escalations related to the given case).

We also used this occasion to remove duplicated entries in the case status history table. The corrected version is available for download in the Data Files section.

Please let us know if you notice any other data-related issues!

Best,
Andrzej Janusz