Reporting With Cloverleaf

[Jon Melin]

Hello,

I was curious how people are using Cloverleaf for reporting. I have been tasked with keeping a report that logs every time a coded value comes across without a code, i.e. the end users aren’t entering the coded value correct. I know of certain ways to do this such as setting up a route and filter what I want to a file in the output but I was thinking there has to be a more efficient way of doing this.

Does anyone have any suggestions?

Thank you in advance.

~Jon

Topic

[Russ Ross]

Archived SMAT files might be useable for generating a report.

Russ Ross
RussRoss318@gmail.com

[Peter Heggie]

For reporting that does not have to occur in real-time, parsing SMAT files is the way to go, from a performance and efficiency standpoint. We do this for ad-hoc reporting.

For real-time reporting, we embed the detection logic in the interface, usually in the filter, but sometimes in the translate. We prefer the filter just because we don’t want to add complexity to the translate.

We do have a small number of instances where the reporting logic is in the destination thread proc, just to avoid slowing down the sending thread, especially if it has a lot of routes/details.

Peter Heggie
PeterHeggie@crouse.org

[Author]

Replies