The idea for direct acces to reports is interesting.
Also the idea to have some contextual reports is interesting.
But the idea to propose it near buttons seems strange, and what reports to propose ?

Any further idea ?

Yes, you right, could be strange but see the following mockup, and imagine in the combo a list of report ? it could be nice ?

Hi,

For your question about which report to propose, i think the better way is to use standard report. And for making the link between one report to a class object, you can use a table named for sample : contextualReport. The process for me could be exactly the same as the one you have developpe for the today screen report.

We need a table named "contextualReport"

1. idReport : for identify the reports
2. RefType : to identify the Class concerned by
3. and perhaps other needed fields, i let you see

and another table for parameters; the table could named "contextualReportParameter"

1. idContextualReport : for identify the contextual reports
2. parameterName: were could be store a parameter name
3. parameterValue: for store the value of the parameter, exactly same as today

And at the end you change objectButtons.php or another generic view to verify if exiting an contextual report for the showing object. If for the 'Activity' object you have one or more report you show the combo box with the list of report, and if not you show nothing.

At the end, when the final user select a report in the list, you show the "dialogPrint" DIV, with inside the report !

All i write is just suggestion ! you know your application much better than me.

Thanks

Ticket #1177 recorded