Kevin Kennedy

@Mark (ESC) I agree with @Steve Giller's advice, but as we are complete newbies in the Hornbill world, and didn't know any better, I did write something similar for our instance. In our case we had a very limited population of tickets, and the report ran without error. I would advise you if you choose to proceed, to date limit your report to short intervals, to ensure that it runs without error and does not impact your performance.

@Ann K Forgive me for perhaps not understanding your need, but it sounds like you just need to either: 1. Want to hardcode in a date to limit the number of items the report returns, i.e. no entries that occurred before January 1, 2021. or 2. Want to prompt the user for either the earliest date to include, or the dates starting and ending, at the time of report execution. If this is accurate, I can walk you thru the process, as it has been a while since you posted, and no one else has stepped forward. Apologies in advance if I am over-simplifying you needs.

@RobW Pretty late to the party here, so perhaps the need has passed. I just wrote two similar reports to what it sounds like you are wanting to see. My purposes were a little different, the first version of the report shows all activity & communication, what and when it happened, against a single request. As we are in the US and a public company, and our Sarbenes-Oxley auditors often ask for this kind of detail. Like looking at ticket detail, but without access to Service Manager. The second version was to check the tone and frequency of communications from a single user across all requests they interacted with. I have not finished totally validating either report yet, but would be happy to walk you thru the process I used to create either/both of the reports, should you see value in such an activity.

@Victor@James Ainsworth Thanks to @Yodit for inspiring a solution to my problem regarding the inclusion of "between user specified dates" in report titles. Whilst she was writing a quick report to troubleshoot a problem, she offhandedly mentioned that she could instead of using the double sided "between", it could be written as a greater-than or equal to a user prompted date, and a less than or equal to a second user specified date. Brilliant! When done that way, and including the variables start & end for my user prompted values, I was able to produce this, which was exactly (or close enough) what I wanted.

I'm also assuming that the variable cannot be a user prompted date range. Here is how I set up the filter. Note the Variable Reference is usdr, for user specified date range. set up the report heading like I thought it should be: However, when I run the report, I get the following: Which, I will admit, is a very pretty chart, but has failed to translate the date range into the title. Any guidance as to how to do this properly?

@NeilWJ I can confirm that the report we noticed this problem on was a scheduled delivery type.

@NeilWJ, @Paul Alexander We are also experiencing the second issue Paul raised.

@Michael Sharp Thank you for posting your solution to this. We will be facing the same questions over the next few months, as we begin to incorporate Quality Dept. Gage Repair Requests & possibly Human Resources within our Hornbill Instance. I had not even considered that this might be an issue until I stumbled across your post. You were gracious enough to come back and post a response when you solved this, for which I am grateful.

@Anne K You definitely can, but depending on how your email is configured, it may not pass thru without setting your email server to trust images/attachments from the domain hornbill.com . Our corporate logo does not download until you approve downloading images for that email (O365 hosted Exchange with Outlook as an email Client)

Jeremy: In our instance, this is an indicator that your session has been idle too long and has expired. Simply refreshing the page relogs you in (assuming you are using Single Sign On, and returns you to the page you were on, without the CSRF token mismatch. Hope this helps!

Ann: We are relative newbies on the Hornbill app. We had multiple approvals that expired, and had similar problems. We had to edit the Executed BPM's and update the approval node to notify the request timeline that the approval was completed. Then we saved them and re-ran them from the point of failure. Hope this is helpful to you, sorry if not... Kevin K.

Victor - Thank you for the rapid response. We are just switching to Hornbill Service Management, and I have not yet had any training on reporting. I have managed to figure out the fundamentals on my own, but some of the details elude me. For my reports, I would like to have the run date added to the end of the Title to show on the report (see above)contents, so that if someone has a printed copy, they are able to tell how long ago the report was run. I have tried several methods to inject the date into this title, without success.

I see that this topic is several years old. As a Hornbill neophyte, this doesn't seem to be working for me. I have tried a number of different combinations to inject the current date into a report title, without success. Or suggest an area of the Wiki to read that will help?