Morning everyone.
I've been designing this process for a client and they want a category/subcategory split. Now normally I'd do this through services, but they're adamant on an interface that offers options based on a previous selection of a given dynamic field, so... I gotta do it with ACLs.
Trouble is my knowledge of ACLs is middling at best. I've already put together an ACL that blocks all dynamic fields of a given type (the subcategories) within a given process. That was the easy part. But I can't for the life of me figure out how to do the opposite.
Thankfully, the fields in question are always single-selection, so that makes things a teensy bit easier.
Any help with this would be greatly appreciated.
Need help writing ACLs: categories and sub-categories
Moderator: crythias
-
- Znuny newbie
- Posts: 1
- Joined: 22 Aug 2022, 20:06
- Znuny Version: 8.0
- Real Name: Daniel Sallenave
- Company: Complemento Tecnologia
-
- Znuny Employee
- Posts: 132
- Joined: 13 Sep 2021, 09:38
- Znuny Version: Znuny 6.3.x
- Real Name: Shawn Beasley
- Company: Znuny
Re: Need help writing ACLs: categories and sub-categories
Hi,
I think the option you are looking for is PossibleAdd. If you use Possible or PossibleNot and want to return the options at a later point, use PossibleAdd. It would be much easier in your case to use the ticket attribute relations in Znuny https://doc.znuny.org/manual/admin/tick ... index.html to upload your restrictions via csv.
HTH
Shawn
I think the option you are looking for is PossibleAdd. If you use Possible or PossibleNot and want to return the options at a later point, use PossibleAdd. It would be much easier in your case to use the ticket attribute relations in Znuny https://doc.znuny.org/manual/admin/tick ... index.html to upload your restrictions via csv.
HTH
Shawn