A signature captured through a Mobile Work Order (Aurena Native) app, stored as a CLOB larger than roughly 32,767 bytes, converts to a BLOB without error but doesn't render in Crystal Reports — signatures under that size threshold work fine.

All FAQ questions / Mobile and service touch apps (MWO/MRO)

Answer

Rather than writing a custom CLOB-to-BLOB conversion routine for this, use the platform's own signature-conversion function (the one built for the equivalent Task Signature view, exposed as a Clob_Base64_Blob-style API) after stripping the data:image/png;base64, prefix from the stored value — this handles signatures of any size correctly in Crystal Reports, including ones well over 32,767 bytes, where a custom conversion routine can run into chunking issues at exactly that size threshold.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Mobile and service touch apps (MWO/MRO) questions