Architectural Considerations for Reporting

The complexity of the how you access data, how you prompt the user to print the
report, and the design of the report are all architectural considerations to take into
account.

The following table provides architectural considerations when you plan,
convert, and define your reports.

Question	Consideration
Is event handling in the input dialog required?	If yes, use a UIBuilder for the report. If no, decorate a report contract.
Do you need to pre-process input data? Do you need to manipulate or modify input data? Do you want to be able to open different reports from the same dialog? Do you want to run the report from a form?	If yes, create a custom Controller for the report. If no, use the default Controller.
Is the report a simple list of data?	If yes, use auto design to create the layout of the report. If no, use precision design to control the layout of the report.

Regards,
Hossein Karimi