Different U16 Forms used by different Teams -- How to best direct users to the correct Form
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12m ago
We have three different teams that are using different Incident Forms. One is using a custom form and the other two are sharing the default form with custom rules for what fields are shown/required. For a while now, the company was setting the view/form used via a View Rule that would set the view based on a user's role. If they were in the specific role, they would be forced to a specific custom view/form. We now have a need for individuals to have access to both forms/views.
Ultimately, we want to redo this to work better overall, but for now to allow the business to continue processing work, we turned off the View Rule, created custom Application Menus with Modules that have specific URLs to force the view/form when creating and/or searching for tickets.
We then setup view rules to direct users to the correct form when opening an existing ticket as it did not always use the view/form applied at the list view.
For the most part this is working, but we have run into an issue where the Copy Incident functionality under the additional actions menu is not copying to the same form/view as the source with this configured. It always defaults to the default view/form for the copy.
If we disable the new view rules and then go to the list view that has the record we want to copy, set the appropriate view manually via the additional actions menu, then open the incident and choose to Copy Incident it works as expected.
Thus, we believe the issue is with the View Rule.
Looking for any thoughts on how to set the view programically so that it is set at the list view and holds when a records is opened from that view and then copied to a new incident. It then would need to switch if the user goes to a different list view and opens a record from there. We would prefer not to have to require the user to manually select the view before opening the incident.