osTicket Jasper Reports Plugin

buck_rogers

If anyone is interested, I have created a plugin for Jasper Reports. It is Alpha .1. It has one report, but it shows the way to create more. I will be adding to it as needed.https://github.com/meatballcoder/osticket-jasper-plugin

Grizly

Hi @[deleted]! Cheers for releasing mate, I've jotted down some random thoughts, might be of help: Does the firstRun stuff do anything? I've not seen that before. Nice. I was thinking about upgrades & database initialisation etc.. for plugins I mean, didn't know how it would handle it. Does your callbackDispatch function work properly? When I had mine inside the plugin, it kept instantiating the Plugin, so I had to extrude it.. was annoying. Maybe my version of osTicket wasn't running that code statically.. hmm. Ahh, just had a poke at the manual, class.signal.php uses call_user_func_array, so the $callable passed to Signal: in PHP 5.3+ should be "ClassName:", not array("Class","normalMethod"); Hmm. That could be where I went wrong. Probably won't work for Dispatcher methods.. hmm. Dispatcher:() is ugly! http://php.net/manual/en/function.call-user-func-array.phpIt appears the Jasper server has a compiled version of the report definition to work from, not the xml. So it might not be editable live. Which makes sense.. But to configure the Jaspersoft\Client\Client it is necessary. Next you'll be needing a field, I'm thinking a textfield to enter CSV for the RunnableReports list.. '/reports/osTicket/HelpTopics,/reports/osTicket/AgentStats,/reports/osTicket/Users,/reports/osTicket/Delays' or something.. At least then your call to reportService()->runReport could be administratively defined. Why is help-topics.php in it's own file? It seems like the controller you made could be part of the plugin itself, rather than a whole separate thing. Why do you need to change class.osticket.php? I don't understand the addition of that variable. What does it do? Is it purely for the Nav entries changes in navigation.tmpl.php?Doesn't your Plugin add it's own Menu entry? I believe you can modify $nav after calling require('staff.inc.php'); in the same scope.Woah, never seen an integrity attribute in a link before, that's cool! (Although, apparently not standard anywhere: http://stackoverflow.com/questions/32039568/what-are-the-integrity-and-crossorigin-attribute) I'm seeing $config, min & future in the reports.html file javascript, but I can't see how that gets set. Maybe you need a capture pattern in your searchAction line, like: $search_url = url('^/jasper-reports/', patterns('controller\jaspercontroller', url_get('^search/$', 'searchAction'), url_post('^jasper-stats/(?P<start_date>.+)/(?P<end_date>.+)/(?P<args>.+)?$', 'getTicketStats')); // based on /scp/ajax.php examples, likely wrong...

buck_rogers

Thanks. I will work on it. At the time I wanted to roll it out, and hadn't thought about that part. I'm too impatient, but I will try to make it better.I don't know if the actual Jasper XML can be simply imported, but at least it gives the SQL and some basic format. I figured folks could always use the SQL.I don't know on the runnable reports. Maybe a dropdown? I was trying to use the Jasper rest_v2 API to retrieve a list of reports, but I can only get the containing folder, no list. Still trying on that one.I will move things to the controller. I had initially created those pages in a test environment, outside of osTicket, just web pages in general. I forgot I did that for that reason.I will look at the url pattern and try and implement it.I don't do anything in firstRun. I kept it to remind me it was available to me.I had to change the navigation template in staff because in a plugin, from all I tried, has relative links, relative to the plugin URL. This means to get to the normal menu items they were all scp/dispatcher.php/jasper-reports/dashboard.php, instead of scp/dashboard.php.Changing the core to allow for the public function was the only way I could tailor the URLs. From what I saw in the Equipment Plugin, it looks like they import lots of the core into their plugin and have entirely new header includes, etc. Lots of extra stuff. I could have simply put a public variable in and tested for it being populate, but decided on the methods.I tried the template from the development branch is while it worked, it did not work everywhere. The menu came up okay, but there were links in some of the stock osTicket pages that I needed to supply isPlugin(), or their links would be wrong.

buck_rogers

I changed (thanks Grizly):logic moved to the controller.added a RenderView class that is called by the controller when needed.added static variables to the JasperReportPlugin for the plugin variables set by the Admin when the plugin is installed - username, password, url, port (not using port, just put it in the url), report_path for initial loading of reports and in case needed elsewhere;added logic in controller to populate dropdownlist (or anything else) with the list of reports on a given path (e.g. /reports/osTicket...) in the initial display page.tidied up some naming conventions like controller to controllers and fixed references to such.At the moment I just need to make more reports. This will change the UI eventually for the plugin because not everything will have a date range, I don't believe. It can stay for the moment. I believe I've updated GitHub accordingly.