Running a weekly background-job report in IFS Cloud when a custom event has no natural trigger

Confirmed approach (accepted answer, adopted by the poster):

1. A custom event, and a workflow started from one, always needs a trigger point; it cannot fire on a schedule by itself, so a condition inside the SQL does not replace the trigger.
2. Because the requirement is essentially a SQL query, the recommended route is a Scheduled Quick Report: create a Quick Report from the background-job query, then schedule it to run at the required interval and email the generated list to the recipients.
3. A heavier alternative is a modification: write a utility function, register it as a Database Task and schedule that task. This gives full control but is a customization.

Community workaround (suggested by other members, not the accepted answer):

• To get a scheduled trigger for an event action or workflow, create a small custom entity and a migration job that inserts a new record into it, then schedule that migration job as often as needed. An event action on the custom entity's new-record event then fires on that schedule. One member reported using this pattern in IFS Cloud for about three years and found it stable.

Prerequisites and limitations Release not stated in the thread (IFS Cloud). The Scheduled Quick Report route needs the query to be built as a Quick Report and outbound email to be configured. The Database Task route is a modification (custom utility function). The custom entity plus migration job pattern is a community workaround, not the accepted answer, and adds a small custom object that must be maintained.