Sending a large report (like a Quick Report's full results) as an email attachment from a workflow hits a size limit, since the straightforward mail-sending function's parameter is too small to hold it and the large-object-capable overload isn't usable directly from a custom projection action.

All FAQ questions / Workflows and automation

Answer

A workable pattern for this: schedule the Quick Report's SQL as an IAL object, then create a custom event that reacts to that specific IAL object's replication/update status going to a completed state, and have that event trigger a PL/SQL block that builds the attachment and sends the mail directly — this sidesteps the small-parameter mail overload entirely, since the actual attachment-building and sending happens in your own PL/SQL rather than through a size-limited projection action. If a plain CSV attachment runs into character-encoding problems when opened in Excel, generating a genuine binary spreadsheet file instead of a CSV avoids that class of encoding issue, though building one from scratch is a substantial undertaking best reserved for cases where CSV really won't do.

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

← Browse Workflows and automation questions