Use of multiple Incident forms

[GChanner]

We have a group that would like to have there own incident form rather than using the default incident form. They have a different set of questions and process which is the reason for the 'Ask'.

I understand that best practice is for everyone to use a single incident form but I am looking for options on how we can accomplish this use-case if we choose to do it.

1. Has anyone had a use-case for more than one indent form?

2. How can I use multiple incident forms and have the data populate the same default 'Incident' table?

3. What are some of the concerns we should be aware of?

Any insight will be appreciated.

Thanks

Garfield

[Dr Atul G- LNG]

Hi @GChanner It’s better to create different views for different teams or roles while keeping a common table. In each view, you can add as many fields as needed—whether they are unique to that view or shared with others. This approach is preferable to creating separate custom tables and processes for each team.

[Tanushree Maiti]

Hi @GChanner 

Create separate views for each group/individual  and define view rules accordingly.

Each view will have different set of questions and process. 

Within the view rule, you can write a script to check the assignment group and return the appropriate view name based on that group.

Using View rule,

• You can use a script in the View Rule to check if the logged-in user is a member of that specific group and then force the form to display your custom view. or logged-in user is intended user as per your requirement
• Advanced Script Example: Use ( gs.getUser().isMemberOf('Group Name') ) to return the name of your custom view .