Category: Data operations Ruleset Actions (same group as Move, LogInfoWithLabel, ForceTransformationError)
Input property: SourceNode
LogInfo records the value of a source node in the transformation log using the INFO logging level. This allows the value to be displayed as part of the transformation’s informational output, making it easier to monitor processing activity, verify intermediate results, and troubleshoot the behavior of the transformation. The value appears in the Details section when the data is transformed. It's a non-destructive diagnostic action: it doesn't change, move, or validate any data, nor does it stop the Ruleset. It only reports what a node contains at that point in processing.
Each entry is a standard log line with a timestamp, the INFO level, and the originating class (com.extol.ebi.reactor.lib.AbstractAction), followed by the node's value. For example, if the source node holds c, the log shows:
2023-10-30 10:22:45,519 INFO [com.extol.ebi.reactor.lib.AbstractAction] c
LogInfo does not accept a label. If you need to tell several logged values apart, use LogInfoWithLabel, which adds a Label string and produces output like LABEL: - c.
Possible use cases
- Troubleshooting mappings: Confirm what value a node holds before a Move, lookup, or conditional rule uses it.
- Validating conditional logic: Check that an
Ifcondition is evaluating the value you expect, especially with unexpected qualifiers or empty fields. - Tracing loops: Log a node inside a "For each" Composite Rule to see how values change per iteration.
- Auditing key identifiers: Record a PO number, invoice number, or partner ID in the transformation Details for support and QA review.
- Testing new Rulesets: Add temporary LogInfo rules while building or testing a map, then remove them before production to keep logs clean.
Example
Scenario: An inbound 850 Purchase Order is mapped to a flat-file format. Some orders are landing with a blank ship-to location, and you want to see what the source actually contains.
Ruleset:
| Step | Action | Property | Value |
|---|---|---|---|
| 1 | LogInfo | SourceNode | PO1/N1_ShipTo/N104 (the ship-to ID) |
| 2 | Move | SourceNode | PO1/N1_ShipTo/N104 |
| 2 | Move | TargetNode | ShipToLocation |
Result: When the transformation runs, the Details section shows the ship-to ID for each document just before it's moved. If a blank or unexpected value shows up, you know the issue is in the source data and not in your mapping logic. Once you've found the cause, delete the LogInfo rule.
Tips and best practices
- Use LogInfo for quick, single-value checks. Switch to LogInfoWithLabel when logging more than one node in a Ruleset.
- Avoid leaving LogInfo rules in production Rulesets that process high volumes, since they add log noise.
- Don't log sensitive data (PII, payment details) unless your logging and access policies allow it.
- To halt processing when a value is wrong, pair it with ForceTransformationError. LogInfo only reports.
Comments
0 comments
Please sign in to leave a comment.