webMethods Knowlegebase : JDBC casting of Oracle TIMESTAMP(6) to java.lang.String Ordered Adapter Notification (1807086)

Problem

User encounters an issue while handling TIMESTAMP fields formatting that arrives through Order Adapter Notifications.

In the definition of the field selection on this types of notifications, there is no possibility to use expressions to format the output data (in other adapter service operations, this is possible), so the format that is being presented in the resultset is linked to some internal/default format string, which returns a variable number of milliseconds on the fractional seconds part.

This is causing issues because in the end to end processing user needs to format/transform timestamps to users internal canonical format (ISO8601 UTC/Zulu with three milliseconds precision, "yyyy-MM-dd'T'HH:mm:ss.SSSXXX") but with the dynamic number of milliseconds from the incoming timestamp, user cannot define a clear input pattern.

How can a user enforces the resulting timestamp casting from TIMESTAMP(6) to java.lang.String to always be in a known format?