{"id":575,"date":"2013-05-08T12:41:45","date_gmt":"2013-05-08T17:41:45","guid":{"rendered":"http:\/\/www.exchangedefender.com\/blog\/2013\/05\/shockey-monkey-reporting\/"},"modified":"2013-05-08T12:42:56","modified_gmt":"2013-05-08T17:42:56","slug":"shockey-monkey-reporting","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2013\/05\/shockey-monkey-reporting\/","title":{"rendered":"Shockey Monkey – Reporting"},"content":{"rendered":"

This week we have returned our development focus to Shockey Monkey<\/a> Reporting. You may remember from earlier last month we released our first revised report: <\/p>\n

\n

Employee \u2013 Billable Ticket Summary<\/u><\/b> <\/p>\n

This is a report that will generated the billable time across service tickets for an employee based on time entry against those tickets.<\/i><\/b> <\/p>\n

\"clip_image002\"<\/a><\/b> <\/p>\n

Since then we have added several new reports to this engine and are very pleased with the results. We have also made sure that every single report is printable; we know this has always been a huge feature request. <\/p>\n

  <\/p>\n

Employee \u2013 Billable Time<\/u><\/b> <\/p>\n

This report gives you a calculated total of billable ticket hours for a given employee.<\/i> <\/p>\n

  <\/p>\n

Clients \u2013 Active Summary<\/u><\/b> <\/p>\n

This report gives you an overview of your clients and the last time a touch or invoice was created for them.<\/b><\/i> <\/p>\n

  <\/p>\n

Clients \u2013 Billable Time<\/u><\/b> <\/p>\n

This report gives you an overview of your clients and billable time entered against their tickets.<\/b><\/i> <\/p>\n

  <\/p>\n

Internal \u2013 Inventory<\/u><\/b> <\/p>\n

This report gives you an overview of the inventory currently listed within your portal.<\/b><\/i> <\/p>\n

Since this re-write of our report engine began several months back, we talked about a dynamic report engine<\/b><\/i>.<\/b> This engine would allow you to customize and build a report of the current information inside of your portal. We have finished the first section: Tickets<\/b> and have added it into the reporting engine<\/u>.<\/p>\n

<\/u><\/b> <\/p>\n

*BETA*<\/em> \u2013 Report Templates<\/u><\/b> <\/p>\n

This section allows you to manage your report templates. You can add\/edit a template or select the desired template and generated a new report, which will be saved for viewing at a later time. Clicking on the Last Generated <\/u>date, will open the currently generated report. <\/p>\n

\"clip_image004\"<\/a> <\/p>\n

  <\/p>\n

*BETA*<\/em> \u2013 New Report<\/u><\/b> <\/p>\n

This section is where you will create a new report template or edit and existing one. You will notice at the top of the page, you can enter information about the report template. Then below that section you assign filters and decide which columns should be visible in the generated report. <\/p>\n

\"clip_image006\"<\/a> <\/p>\n

  <\/p>\n

*BETA*<\/em> \u2013 Generated Report<\/u><\/b> <\/p>\n

Upon viewing a generated report you will see something like this, depending on the columns you marked as visible and the report filters that were configured. As mentioned before, this report is printable along with every other report in this new system. Upon clicking the print button, it will open a new window with the printable information. <\/p>\n

\"clip_image002[4]\"<\/a> <\/p>\n<\/blockquote>\n

Hank Newman
VP, Development
hank@ownwebnow.com<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[…]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-575","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/575","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=575"}],"version-history":[{"count":2,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/575\/revisions"}],"predecessor-version":[{"id":578,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/575\/revisions\/578"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=575"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=575"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=575"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}