How to link statements schedules to automatically email after successful preparation

Question

System design (I use 2024R2 and will be using 2025R2 soon):

Prepare statement process should be triggered for each cycle, and must be completed successfully before going to next steps.
Print statements process depends on the prepare process, and can’t be triggered unless the preparation is completed successfully.

Current state:

I use automatic schedules to run the process overnight because it lengthy process.
We run Prepare Statements schedule first, then check the next day whether it is successfully completed and that the statement cycles are available in the “Print Statements” screen.
Based in the previous successful schedule, we trigger other schedules to email the statements

The question/Desired situation:

Is it possible to configure the schedules to run in sequence based on the successful status of the predecessor schedule? i.e. I want the system to use schedule to run the prepare statements, and if this schedule is successfully run, then run the email statements schedule.

Steve Milner · Answer

@ziadsakr Schedules can't be chained. Automation Schedules (SM205020) has no predecessor or "run after" setting. Each schedule runs on its own timetable.

You can get the same result without chaining, because Print Statements (AR503500) already knows whether the prepare finished. A cycle's Last Statement Date only moves forward when Prepare Statements (AR503000) has processed every customer in that cycle. When the Statement Cycle is set on Print Statements, the Statement Date fills in from that Last Statement Date. With Email Statement selected and Show All cleared, the list holds only statements that haven't been emailed and aren't marked Do not Email.

So let the email schedule run every night after the prepare window. Use one schedule per cycle, and one per branch too if Prepare Statements is set to For Each Branch. If the prepare didn't finish, the date still points at last cycle's statements. Those were already emailed, so the run sends nothing. Once a prepare completes, the next run emails the new ones.

The catch is the schedule's Filter Values tab. A schedule created from the screen saves every filter value, including the Statement Date that was on screen that day. Clear Active on the Statement Date row so the date comes from the cycle.

This is from the 2025 R2 code, the version you're moving to. Try it on a test tenant first, since a wrong filter here emails real customers.

Sign up

Social Login

Login to the community

Social Login