Jump to content

Martyn Houghton

Hornbill Users
  • Posts

    4,015
  • Joined

  • Last visited

  • Days Won

    86

Everything posted by Martyn Houghton

  1. On the Timesheet view within the Service Manager request, it would be useful to have a breakdown of time spent by Analyst on the 'Values View'. Cheers Martyn
  2. @James Ainsworth Just wondering if there was any progress on having the 'Reason' pop up box more configurable, i.e. being able to turn it off? Cheers Martyn
  3. I am sure it is a common occurrence in most service desk, that a request will often spawn a follow on request(s), sometimes at the beginning of its life-cycle, but also at the end when you get ''there just one other thing that might be related' conversation. Therefore it would be could to have the option when raising a new request from an existing one to be able to selectively copy the connections and attachments from the current request. As this would save a lot of manual operations in doing so and ensure consistency. Cheers Martyn
  4. Coming back to the original post by @Kelvin, it would still be useful to have a field holding the details of who last updated it, which can be used in the BPM or email variables. This applies to both internal users and contacts, as with Organisation View on it is not always the owner of the request that updates it in the portal. Cheers Martyn
  5. @James Ainsworth Thanks for the update. Hopefully others will find this useful too. Cheers Martyn
  6. @James Ainsworth Thanks for the update. Just make the system more manageable when dealing with multiple service desks and large volumes of services. Cheers Marytn
  7. @Gerry Thanks for the update. Hopefully this is something that fits in the strategy in the near future. Cheers Martyn
  8. @Victor Thanks for the update. It would make managing annual renewals so much easier. Cheers Martyn
  9. @Victor Thanks for the update. Hopefully these will move forward soon. Cheers Martyn
  10. +1 for both Customer and Service Portals.
  11. @James Ainsworth Thanks for the update. hopefully will manage to go creep up the list. Cheers Martyn
  12. @NeilWJ That's spot on, in our case for Incidents, but the same thing applies. Lots of Red Zero's. Dont't Panic! Cheers Martyn
  13. @Steven Boardman Your scenario is correct and we are using Corporate Service Level agreements. I will give it another test, as it might have been something I done wrong in the workflow/config, as it appears it is designed to cope with the having the different combinations of timers. Cheers Martyn
  14. @James Ainsworth Thanks that would be a real help, in allowing customer to a more detailed over view of their requests without having to request reports. Cheers Martyn
  15. @James Ainsworth Just wondering if there had been any further thought on reporting/exporting requests in the Customer/Service Portals? Cheers Martyn
  16. @James Ainsworth Is there any update on having the ability to display the Service Level on the Customer/Service Portals? Cheers Martyn
  17. @Steven Boardman Following on from the extension of the maximum duration on an SLA in SM build 1117, is there any plans to allow the system to cope with an SLA only having one of the SLA timers set, either Response or resolution. I.e. the workflow has the start and stop timer nodes in for both as most of the priorities have both, but would not fail when there is no timer for the current service level. I know I could achieve this by hard coding in decision nodes to the workflow not to start the timer if there is no timer on the current SLA, but with a growing number of SLA's this requires quite a bit or work/administration. Is there a way to query the current Service Level assigned to a request to determine if there is a Response or Resolution Timer, which would allow you to route around the timer start/stop nodes. Cheers Martyn
  18. At the moment under a Catalog Item you have the Title and the Description, both of which are 'public' and displayed on the Service/Customer Portal. It would be useful to have a Notes field on the Catalog Items to contain internal notes/description which can be used by the Service Owner to record information, such as changes, catalog specific setup etc. Cheers Martyn
  19. Like 'Services' it would be useful to be able to group/filter Service Level Agreements by 'Service Category', as we use the category to differentiate between the different Service Desks we operate on the common platform. Cheers Martyn
  20. @James Ainsworth Is there any plans to add the ability to copy Service Level Agreements? I am in the midst of setting up a new sets for another Service Desk on our system and the SLA's are all a bit similar but just enough difference that you need to create a separate copy. Cheers Martyn
  21. @Victor It would still be useful to have a default value for the sub status to be set, as we still have active requests which were created with workflows prior to the setup of our sub-statuses. This will also be the case for any other sites who migrate to using sub-statuses with open requests using non sub-status aware workflows. Cheers Martyn
  22. @SJEaton Sam The basic way relies on a manual update to the parent (original) request either by the user app or portal. To automate it would need to include an integration node in the child (linked) request to make an update on the parent (original) request which would then trigger the status change. The latter would use the Hornbill integration elements within iBridge (https://wiki.hornbill.com/index.php/Hornbill). From @Steven Boardman update on the 8th January, I would guess that the Service Manager build with the fix in it is likely to come out mid next week, so might be work holding on for a further week rather than making the changes to your process now. Cheers Martyn
  23. @Daniel Dekel Thanks. I see we use the Instant Messaging field and change the type to Skype for Business. Do you know if it is possible to populate this field and set the messaging type using the LDAP Importer as we can update all our linked users? Cheers Martyn
×
×
  • Create New...