As I start I'll acknowledge this is a weird question.
We've identified that the journal tables sometimes store the condition value as: -2147483648
We use the standard condition values that come out of the box and map to (1, 2, and 3).
The issue was highlighted by our data warehouse team because the above crazy big negative number was showing up in some of their operating metric reports.
I've been working with WF support. It sounds like engineering is concerned that fixing the erroneous value will create issues for other customers. Part of our compromise is that I'd ask in the WF community how others are using this error and/or what fixes you've put in place that support auditing and the purpose of journal tables?
