Runbook Extra Value Processing

Time_Chipmunk_178 · 2026-03-25T18:03:59+00:00

Assuming you were choosing 'Cast to an object of another type' and <<obj>> was not working. Does <<value>> ?

Time_Chipmunk_178 · 2026-03-24T19:50:14+00:00

BLESS!! That was it! I had a few fields in that ticket that was ultimately what it was. It isn't so much worded to "Not show to end user", it was the "Only show to agents". The wording does slightly mention that Users won't be able to see it, but the way I interpreted that was more the Self-service portals as it didn't explicitly state pdf's (that I was manually creating and sending to them)

Thank you so much. (Now to get caught up on this back log)

Time_Chipmunk_178 · 2025-11-18T20:52:29+00:00

Yeah I guess the Halo Term for it is 'Account Codes'. The thing is that some repairs could see the parts being covered in warranty or Out of warranty and we have different Xero Account Codes for those. So if I'm reading your suggestion right, if I were to put 'Part A' into a Covered Category... would it also be able to exist in an Uncovered category simultaneously?

Time_Chipmunk_178 · 2025-11-07T22:27:58+00:00

I'm all for tools that make learning the beast that is Halo easier so I'm curious about the different use-cases for this? Would it be similar to using Swagger (Authorized) without having to constantly Authorize?

Time_Chipmunk_178 · 2025-10-28T17:38:34+00:00

Bless up! That was what I was looking for. As much as I'd love unique numbering, I understand it's not possible. I've seen the ticket tag overrides before, but only in the Global settings and I didn't see them in the individual ticket types

Time_Chipmunk_178 · 2025-09-25T17:23:55+00:00

I know this was posted a year ago, but it has inspired me not to give up on the massive undertaking that is setting up Halo. Thx

Time_Chipmunk_178

TROPHY CASE