Event-Triggered Crystal Reports
Run the Report When the Business Is Ready.

Stop watching for a file or checking whether the data is ready. CRD can wait for a business condition, run the reports and carry out the next tasks. All features are included in your licence, with no paid feature add-ons.
Start reporting when the required database condition is met.
Respond to files, incoming email or program results.
Wait for one condition or several together.
Prepare the reports and carry the work forward.
The Business Dependency
A Time on the Clock Does Not Mean the Data Is Ready.
Payroll runs late. A supplier’s file arrives early. The order batch finishes at a different time each day. CRD lets reporting follow those conditions, so someone does not have to watch the clock.
The Data Arrives Later
A fixed reporting time can come before the upstream work is complete.
The Handoff Is Manual
Someone has to check the condition and start the next reporting step.
The Work Continues After Export
The report may be one step in a larger piece of work.
Why Choose CRD
Connect Reporting to More Business Conditions
CRD adds database, email and program-result checks alongside tasks that prepare files and continue the process.
SAP Crystal Server
File Events and Schedule Dependencies
SAP Crystal Server provides file events, schedule dependencies and custom events.
Named User licensing supports scheduled delivery; personalized Publications require Concurrent Sessions licensing.
CRD
From Business Condition to Next Step
Watch for the database condition your report depends on.
Respond to files, incoming email or program results.
Wait for any one condition or all required conditions.
Move files, run programs or update records around reporting.
Run the report or package that belongs at that point.
Events, packages and data-driven workflows are included in your CRD licence, with no paid feature add-ons or additional publishing feature licence.
The Payroll File Arrives. Reporting Can Follow.
For example, payroll finishes by placing a file in a folder. CRD checks for that file, runs the payroll reports and delivers the outputs. A follow-up task can move the file out of the watched folder.
Watch
Check the folder at the chosen interval.
Run
Produce the payroll reports.
Deliver
Send them to the reporting destinations.
Continue
Move the processed file with a follow-up task.
Wait for the Work Your Reports Depend On
Event automation is included in your CRD licence, without a paid feature add-on.
Watch the Business Condition
Use database, file, email, FTP, process or program-result conditions.
Combine the Required Checks
Start when one condition is enough, or wait until all are met.
Run Tasks Around the Report
Prepare files before reporting and carry out the next action afterwards.
Reporting Can Be One Step in the Process
Let CRD handle recurring tasks around the reports as well.
Get Files Ready
Copy or move files, combine outputs and prepare protected archives.
Work With Business Data
Run SQL, stored procedures or scripts, including a follow-up record update when needed.
Start the Next Step
Launch a program, chain another schedule or send output to its next destination.
Run Tasks Without a Report
Use Automation or Data-Driven Automation schedules for tasks that do not need an RPT file. Both are included in your licence.
Try the Handoff Someone Has to Watch Today
Start a free 30-day trial with an arriving file, ready database condition or other reporting trigger. See how CRD can connect it to the reports and next action your team needs.
Built by ChristianSteven Software
Reporting automation experience from organizations around the world.
Your Event Workflow Questions, Answered
Answers to common questions before you try CRD.
CRD can monitor database records, files, FTP, processes, program results, windows, unread email and ports. The available checks depend on your build and connection setup. Event functionality is included at no additional cost.
Yes. Use ANY when one condition is enough or ALL when every condition must be met.
CRD checks at configured intervals. It does not promise instant or exactly-once processing; the setup should account for repeated conditions and work already handled.
Yes. Event workflows can use reports or packages with tasks before or after reporting and delivery. These features are included at no additional cost.
Detection does not itself require a schema change. An optional task that writes back to the database is a separate choice.
Yes. Automation and Data-Driven Automation schedules can run tasks without an RPT file. Both are included in your CRD licence.
Show Us What Your Reporting Has to Wait For
Bring the condition, reports and follow-up action. We’ll show you how CRD can connect the steps.