Schedule Management UFL for Crystal Reports

Schedule Management UFL for Crystal Reports

Schedule Management UFL for Crystal Reports

Price: $80.00

Quantity in Cart: None


Summary

This User Function Library complements cViewMANAGER or cViewSERVER by enabling you to design reports that can update any schedule item properties or any parameter value; run reports immediately, and load events into the schedule log files.

Features

  • Works with cViewMANAGER and cViewSERVER schedulers for Crystal Reports.
  • Works with Crystal Reports 6.0 and later.
  • Easy installation.
  • Easy to use.

Why it's useful (and worth buying)

Of particular use is that you can control the generation of control files for the multirun processing of reports in the schedule.

If a report in the schedule is set to burst using the multirun destination, you can design a report that uses this UFL to dynamically set the values in the multirun. This means that the report bursting can be totally driven by the data in your database.

If you want reports processed because of values in the database or a file appearing in a folder, you can use this UFL to force a "RunNow" on one or more reports based on that event. Use a table in your database or the File System as your data source to identify if the trigger condition has been met.

You can also use cViewLOG as a data source for your report, and use formulas using this UFL to selectively modify schedule item properties as required.

Example

As more and more things become data-driven, the idea of data-driven report bursting becomes increasingly attractive. And now, you can have the ability to make that happen.

This can be a powerful business tool. Think about how you might apply it, and it just keeps making more sense.

Here's an example.

Like any other company, yours has limited resources. Management's job is basically to manage those resources for the greatest benefit of the company and its shareholders. Since revenue comes from customers, meeting customer needs is a core aspect of managing those resources.

Presently, you have a Product Defects report scheduled for delivery each week. It shows various aspects of product defects, such as which were caught in QA inspections and which were reported by the customer. The report uses formulas and subreports to assemble disparate data into a very useful report. The problem is the report is useful only once a week.

If there's a spike in defects, it won't get management's attention for perhaps an entire week. Or maybe two weeks, if managers decide to save time by not reading this week's report.

One solution to this problem to rely on Customer Service to see the pattern and then take action. How would this play out? Obviously, the various Customer Service reps would compare notes during their lunch and break times and then contact the production department or maybe engineering or perhaps the shipping department or, come to think of it one of the 17 different component suppliers and get that problem solved!

Another solution to this problem is to send out daily reports. This sounds good, however it guarantees that managers will do what anybody does with information overload--either barely glance at the reports or not read them in the first place.

A third solution to this problem will actually work. That is to trigger a report based on the data. Now this report becomes an "exception." And, as we all know, busy managers tend to manage by exception. This report, coming at an odd time, must be important! Action required, action taken, defect issue addressed.

Free Trial Download

Customer Reviews
Average Customer Review: Not yet rated
Write an online review and share your thoughts with others.

There are no reviews