Jump to content

Jim

Hornbill Users
  • Posts

    390
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by Jim

  1. Hi, We have successfully got our servers updating in Hornbill from Azure Arc, Is there any information on how we can update the software inventory for the servers or refer to a defined query in Log Analytics Workspace at all?
  2. https://live.hornbill.com/{instancename}/admin/personalsettings/notificationsettings/ users manage their own notifications settings here
  3. Check your sql limit, I believe 2500 is the max, and add a filter on date range, I belive they max out and thus end up with 0
  4. You need to tell it what to 'count' at first glance, the (on column name) check the table for something like message id or primary ID and count on that
  5. Can we please add an ability to share asset views
  6. Just to filter on requests within the requests view, or to search for coworkers in the search bar at the top
  7. @billster I've been on leave, but I believe h_fixsecs will get you what you are after if you are marking a resolve time
  8. H_fixtime I believe there's another for seconds next to it can't think off the top of my head but it's fairly obviously named once you find fixtime
  9. Do we know of any movement on the integration for Azure Arc for asset management yet?
  10. Hi, We have a touchscreen desktop next to ICT which we direct users to log requests on rather than walking up to analysts, we have to manually log into it to allow user access. Is there anyway we can allow a catalog item to be public facing so we don't have to keep signing into it, Or does anyone know how to auto login using kiosk mode at all?
  11. ahh okay, would there be a way to be able to still search using archived users? as the filters hide them
  12. is there a change log for this so I can see what's changed between each version? PowerShell Gallery | HornbillAPI 1.3.0
  13. We just have a generic incident and service request process for each service if there is an 'other' possible as we gather data from its use we learn which services are required. You can't change a request type categorically. so if you want to switch a process a catalogue item would need to exist under service request and incident as an incident will only be able to use catalogue items for incidents and the same for service requests etc
  14. it would be really useful if we could use the class container for formatting though so we could account for this whilst still having the customisation
  15. just a thought, be careful with black text as any user in dark mode is going to see black as the color is overridden from top level styles
  16. I had to use <span style =""</span> to get most of this working for example: <span style="font-weight:700">Summary</span> But agreed its either a defect or not intended but hopefully this will help you achieve what you are trying
  17. I have been doing some work on the details form side of the system for our change service. I like that this takes wiki markup and I can use span styles to indent or colour etc, What would be really useful is to add: conditional fields conditional formatting data query for dynamic drop down lists I understand the obvious would be to use intelligent captures as that's there main purpose, but I would argue that both are forms by right Reason: Our change request forms are incredibly long and this results in information either being rushed and not enough detail. With adding this into the details form we are able to allow users to save as they go and return later to complete (These are licensed users) - We also have implemented a 'resubmit route' into our process so when a change is rejected for any reason before CAB, details can be modified rather than logging a whole new request This is just the one case but I'm sure there is plenty of use could be had out of these simple features
  18. Any chance of this being reviewed? I have dashboards with no owner so unable to 'Share' them back with me
  19. Brilliant! Slowly chipping away not far from the full import then?
  20. So they look correct which would point more towards an issue with the 'cached information', maybe run it, overwrite their respective custom values to the new information, and then the next one do the same so its sequential and print the custom fields after a new get req info node
  21. The application context is different in those 2 nodes btw, one is core and one is service manager, @Steve Giller that was my screenshot as an example of copying the out parameters not anything that is in use. When you are writing the values to the description, where you have shown them in the screenshot the one you have redacted what are the parameter references in there?
×
×
  • Create New...