For PDF e-Invoicing flows in GIODE, all data routing relies heavily on JMS header values from customer. We use ROUTER flows in GIODE and none of this data goes through GIODE translation PODS. Hence, we don't have visibility to JMS header attributes or corresponding EMB command message fields. In other words, support person cannot verify what came in from customer when we look for this document in inflight. If something goes wrong in the data flow, it will be very difficult to debug issues without having access to JMS header details. We need these JMS header values and queue name to be shown at receive step > event details so that it helps support folks to isolate problem. Thank you!!!
- Venkat Potluri