How to only show certain Assignment Groups and Categories for a table that inherited Incident

[Navaneeth1]

I have a custom-scoped application that has inherited all the fields from the Global Incident table. I'd like to add certain categories and sub-categories to the categories and sub-categories fields by not making any changes to the global fields ( since they are inherited. Is this possible?

I'd also like to restrict the users from only seeing Assignment groups that are part of this application. Could you please tell me how ACL could be used for this as well?

[Sainath N · Accepted solution]

@Navaneeth1 : Yes, you can create your own choices in your scoped application. This is how it works: Until you create your own choices, choices inherit from the parent table (i.e., incidents in your case). Once you create your own choices, you should create all your choices, including those that are already available in the parent table.

As groups don't have application scope, I hope there is an indicator on the group that indicates that these assignment groups belong to your application (ex: type is xxxx).

If you want to restrict the users for selection, you can add the reference qualifier based on the conditions. As ACL's work as an OR condition, you should make sure that none of the existing ACL's grant access to your groups for unintentioned users, and you should create an ACL with your own logic.

Please mark this as correct answer and helpful if it resolved, or mark this helpful if this help you to reach towards solution.

[Sainath N · Accepted solution]

@Navaneeth1 : Yes, you can create your own choices in your scoped application. This is how it works: Until you create your own choices, choices inherit from the parent table (i.e., incidents in your case). Once you create your own choices, you should create all your choices, including those that are already available in the parent table.

As groups don't have application scope, I hope there is an indicator on the group that indicates that these assignment groups belong to your application (ex: type is xxxx).

If you want to restrict the users for selection, you can add the reference qualifier based on the conditions. As ACL's work as an OR condition, you should make sure that none of the existing ACL's grant access to your groups for unintentioned users, and you should create an ACL with your own logic.

Please mark this as correct answer and helpful if it resolved, or mark this helpful if this help you to reach towards solution.

[Sainath N]

@Navaneeth1: Did my response address your question, or is there anything else I can help you with?

Please mark this as correct answer and helpful if it resolved.

[Tai Vu · Accepted solution]

Hi @Navaneeth1 

Given that you have a new table in your scoped app, you have the ability to define your own choice set for that table, allowing you to override the choices from the parent one (Incident in your case).

Since groups are data and not application files, you'll need to establish a method for identifying specific Assignment groups for your app. You could consider leveraging the Group Type, standardizing Group Name, or other criteria.

After that, in the dictionary of the Assignment group field, you can create a Dictionary Override under the related list and apply the Reference Qualifier to display only those specific groups.

Cheers,

Tai Vu

[Navaneeth1]

Hey @Tai Vu ,

Thank you for your response. Is there a way to add the choices on the scoped application's category field without them being shown on the global field of categories for the incident table?

I tried adding the choices in the form design and it does only show the ones I need for the application but it added those choices on the global field for category on the incident table as well.