Event-Triggered Crystal Reports

Run the Report When the Business Is Ready.

Wait for the right business condition, then produce the report and carry out the surrounding tasks with CRD. All CRD functionality is 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.

Combine conditions and configure tasks around report production.

Deliver the finished output and define the next action.

The Business Dependency

A Time on the Clock Does Not Mean the Data Is Ready.

Your team should not have to keep checking whether payroll finished, a file arrived or an order became ready. CRD connects the reporting job to the condition it depends on.

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

A file may need to be moved, a database updated or another process started.

Why Choose CRD

Run Reporting When the Business Condition Is Met

Choose CRD to configure the condition, reporting job and surrounding actions in one maintained workflow.

SAP Crystal Server

File Events and Schedule Dependencies

SAP Crystal Server provides file events, schedule dependencies and custom events.

File events and schedule dependencies can coordinate report execution.

CRD

Business Conditions and Configured Tasks

Database checks: respond to the supported record and data conditions.

File, email and program checks: connect reporting to an incoming file, approved mail account or program result.

Combined conditions: use ANY or ALL logic for the required dependency.

Surrounding tasks: configure actions before or after report production and delivery.

Report or package: start the applicable reporting job when its conditions are met.

Event, package and data-driven workflow functionality is included in your CRD licence at no additional feature cost.

From a Ready Record to a Delivered Report

For example, an approved ready-to-process record causes CRD to run the required report. A configured follow-up action records processing so the selection can exclude work already handled.

Check

Monitor the relevant ready-to-process condition at the configured interval.

Produce

Run the report or package with the data the business job requires.

Deliver

Send the finished output to the approved destination.

Follow Through

Perform the configured action and verify how repeated or failed conditions are handled.

Configure the Dependency and the Next Step

Use a condition your business process can establish, then define what should happen around the report. All CRD event and workflow features are included in the licence.

✓

Watch the Business Condition

Monitor supported database, file, email, FTP, process and program-result conditions rather than relying only on a calendar time.

✓

Combine the Required Checks

Use ANY when one condition is enough or ALL when the workflow must wait for every required condition.

✓

Run Tasks Around the Report

Configure task timing before or after reporting and delivery, including the applicable report-level and package-level actions.

START FREE TRIAL BOOK A DEMO

A business condition starts report production, delivery and a configured follow-up task.

Carry the Work Through to Its Required Result

Choose the tasks the process needs and make their order, execution account and failure response explicit.

Prepare and Move Files

Copy, move or organize files and folders, assemble protected archives, merge PDFs or Excel outputs and apply the required file controls.

Connect to Business Data

Run configured SQL, stored procedures, scripts or record actions. Add a follow-up update when the process needs to record completed work.

Call the Next Process

Launch a program, chain a schedule, print output or perform supported web, email, FTP and SharePoint actions.

Automate Without an RPT

Automation and Data-Driven Automation schedules can perform configured workflows without a report. These schedule types are included in the CRD licence at no additional feature cost.

Supported event families include database records, files, FTP, processes, program results, windows, unread email and ports. Use the exact condition settings available in your installed build. Email conditions require a currently supported account and authentication setup. Detecting a new or changed record does not itself require a schema change; optional write-back is a separate choice.

Yes. ANY or ALL logic can combine conditions, and event workflows can use applicable reports or packages. Event and package functionality is included in your CRD licence at no additional feature cost.

CRD polls conditions at configured intervals; it does not promise instant or exactly-once processing. Define how repeated conditions and completed work are handled. Test the same condition twice and verify the intended result with your actual configuration.

Yes. Configure the applicable default or schedule task lists, report-level and package-level timing, execution account, waiting behavior and timeout. Test a failed task as well as the successful sequence.

Task options include copying, moving and deleting files; creating, renaming and moving folders; local and FTP housekeeping; writing or appending text; ZIP encryption and extraction; PDF merging, stamping, metadata and security; and Excel merging, metadata and read-only controls.

Options include program execution, printing, schedule chaining, web and FTP operations, SharePoint upload and metadata, backup tasks, SQL and scripts, stored procedures, records and BLOB operations, and SQL table or column changes. Registry actions include setting a value and creating or deleting a key. SMS and Exchange appointment requests depend on configured messaging and current authentication.

Applicable email workflows can parse values and use attachments in configured actions. Evaluate the sender, authentication, selection rules and how already-processed messages are handled before relying on unattended production.

Yes. Automation and Data-Driven Automation schedules do not require an RPT file and are included in the CRD licence at no additional feature cost. Evaluate the configured task sequence, execution account and response to a failed step.