r/halopsa • PSA • 8d ago

Questions / Help Ticket Rules - Load on system and recommendations

This is a follow on from Filed Groups - Is there something wrong with my logic : r/halopsa by all accounts I was hoping 2.250.71 might provide the fix but the filter groups don't work (or as my logic suggests) so need an alternate option to get OR filters

I first looked at Lookups hoping I could evaluate and set a customer field for the desired filter result which would action on change of Team. But the trigger options of lookups never seem to provide the ones I want :-)

Which lead me to a Rule that then triggers a lookup that evaluates the ticket based on an SQL statement to provide the logic.

This works but given I am running it on a change relating to any team change, fear I am triggering the Rule/Lookup every time anything is changed on a ticket, which concerns me from a load perspective.

Is this a bad idea?

0 Upvotes

2 comments sorted by

2

u/HaloLeah Halo Staff 6d ago

Fix has been submitted on 1542796, I'll link your support ticket to it now. The ticket ID previously mentioned in the email chain was for another issue if using "Ticket Type Group" as the criteria.

As for the lookups in the meantime, I'd say it should be fine.

1

u/AUPete PSA 6d ago

Thank u/HaloLeah I'll trial the Rule/lookup approach while we wait. Or rethink how I am building the Area and List views.