Jump to content

Bob Dickinson

Hornbill Product Specialists
  • Content Count

  • Joined

  • Last visited

  • Days Won


Bob Dickinson last won the day on February 26

Bob Dickinson had the most liked content!

Community Reputation

60 Excellent

1 Follower

About Bob Dickinson

  • Rank
    Senior Member
  • Birthday 08/26/1983

Profile Information

  • Gender
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi @Josh Bridgens Having had a look at this, I don't think we can get out exactly what you want. We do not store/record the "Total Time Open" in a single attribute against the request in the table h_itsm_requests. This means that a calculation would be required (something like h_dateresolved minus h_datelogged to generate the number of seconds/minutes between the two values) which you could then perform an AVERAGE calculation upon. However, when creating measures, we do not have the ability to perform calculations like that - we can only query specific existing attributes. There is a field called h_fixtime but this records the time taken to resolve the request based on the SLA asscociated (so would incorporate your working time calandar hours, and not record time the request was on-hold etc) We may be able to create a Real Time widget (which would give you the average time open of all tickets at the point of time you are viewing it) but this is not a sampled solution so you would not be able to compare it to other days without manually recording this figure every day. So unfortunately I'm not sure if what you are after if going to be possible through Hornbill right now - happy to help if you have any further questions though. Kind Regards Bob
  2. In this latest update, Team Hornbill have combined all of the fantastic new Service Manager features that were released in first two quarters of 2020, into a single update. If you missed some of these new features whilst they were being rolled out in the various Service Manager updates, please have a look at the link below for a refresher on this new functionality that is available to all subscribers right now. Here is a direct link to the latest edition: https://wiki.hornbill.com/index.php/Service_Manager_Quarterly_Update_2020_Q1/Q2 For links to our previous update round ups, please check out the Whats New Wiki Page
  3. Hi @Josh Bridgens I'm not sure if this is possible at the moment - but just to get some more information about what you classify as "Age" Are you incorporating calls that are On Hold? Are you taking into account Work Time Calendars? Or is this literally "The average of how many Days/Hours old all of our calls our, regardless of anything else?" Kind Regards Bob
  4. Hi @Alisha When you are creating your widget, if you click on the "Chart Settings" button, you should see an option called Label Display Lookup. Because h_createdby is the User ID, you need to select the option: "User Name from Id" This should then map all of the user IDs to their real names and make it look a lot nicer. Hope this helps Bob
  5. Hi @stepghg I don't think you can do any formatting on the view of the raw sample results within the measures screen. But there are some things you can do if you are using this data and showing them as widgets. For example, I've taken a measure here - and created a "Scorecard" widget (that pretty much looks the same as the result you get in the measures screen). From here you have a few formatting options, including the ability to round up/down the decimals places: Hope this helps Bob
  6. Hi @AndyGilly Nice idea for a report - I've not built this one before, so have given it a go. I've put in some date criteria (basically any reassignments that have happened since the start of Last Month and the Today) but feel free to play around or remove this in the filter section of the report. Upload it using the green button in your reports section, and let me know if it does the job. PS - Ignore the preview if it looks like the Previous Team Name and Assigned Team Name are the same...this is just a preview bug, when you actually run the report the data should hopefully show correctly. Kind Regards Bob incsr-reassigned-team-after-breaching-resolution-sla.report (1).txt
  7. @Martyn Houghton Not that I'm aware of, the above tip is for individuals mentions only
  8. @Martyn Houghton @samwoo This isn't exactly the answer to your query (as you rightly suggest, what you are asking for is a feature request). But one alternative that could be used in certain scenarios is to use an "Update Timeline" node in your business process, and you can actually add logic to the content to mention individual users (e.g. the equilivilent of typing "@Bob" in an update). Doing this will also result in them receiving the Hornbill Bell notification to say that have been mentioned. To do this, you can use this logic: {"<name>","urn:sys:user:<userID>”} so for example, to mention me it would be something like: {"Bob Dickinson","urn:sys:user:bobd”} Then you can get even more clever and inject variables from your BPM into the logic. So for example, if I wanted the BPM operation to mention the current owner of the request, I would inject the owner variables as follows: {"&[global["flowcode"]["owner"]]", "urn:sys:user:&[global["flowcode"]["ownerId"]]"} As mentioned, not the exact answer but it might give you some inspiration about other ways of achieving the requirement if you weren't already aware of this. Kind Regards Bob
  9. Hi @Martyn Houghton As a starting point, you should be able to do this on a list of counters widget relatively easily - I don’t have a huge dataset, but believe I have this working with the following set up: Kind Regards Bob
  10. Hi @chrisnutt Did you have any luck with fixing this? Kind Regards Bob
  11. @Michael Sharp Good to hear - and that's some interesting feedback, thank you. I'll suggest that to other customers we are onboarding and get their views to see if that's a common theme
  12. Hi @chrisnutt I'd suggest best practice would be to enforce catalog item selection, as it genuinely makes the layout and structure of BPMs far easier to understand and maintain. However I do appreciate that is easier said than done if a configuration has been performed in a particular way already and you are live. So in your example I'd have another decision node - after the Estates service decision, that is look to see if a Catalog Item has actually been selected or not. If yes - dynamically switch as per my example in the last post. If no - switch to the defined progressive capture (as you have it set up right now) That would cover all eventualities I believe. Let me know how it goes and if this works for you
  13. Hi @chrisnutt I've had a look at your video, and I think I can potentially see the issue (it took me a few watches!). From what I understand; if the Estates Service is selected, along with a Catalog Item - you would then like to Switch to the Progressive Capture related to the Catalog Item. You have a number of catalog items, some with their own captures (for example Lock and Key). However from what I can see - after the decision to establish whether the Estates Service has been made - you have specifed a specific capture that will ALWAYS been switched to next in this scenario - called Estates Incident. Estates Incident contains two forms - the Site and the Details. This means, that even if you select Lock and Key, it is always switching to Estates Incident....and never your Lock and Key specific one: What I believe you need to do, is change this Switch Capture node to dynamically be switching to the Progressive Capture asociated to your Estates Catalog Item that was selected. To do this, change the Switch Capture node above, to be configured as per below: Give that a try, and raise some requests against a few catalog items, including Lock and Key. Hopefully this will Switch as you expect. I may have misunderstood this - so if it fails for whatever reason, please switch it back to the current set up and let us know and we will take another look. Kind Regards Bob
  14. Hi @Michael Sharp We will get this amended so it's capitalised by default. But in the mean time for an immediate fix, you can simply update the translation string in the admin tool (under the Service Manager translations) The string you need to search for is: user.view.requests.requests From there you can change it to the correct case. Hope this helps Bob
  15. Hi @Michael Sharp I've had a look at this, and I'm not sure it's possible to achieve exactly what you are looking for in the form of a Scorecard. I'm just investigating if there is anything clever we can do using a combination of the "Count" option and the WHERE clause and will get back to you. Kind Regards Bob
  • Create New...