Hardware technicians must open incident records on a stripped back form carrying six fields, while service desk agents must keep the current full incident form. Both populations hold the itil role and open the same records from the same lists. Which approach delivers the two layouts with the least duplication of records?
- ABuild a UI policy on the incident table that hides the surplus fields whenever the logged in user belongs to the hardware technician group.
- BAsk the hardware technicians to use Personalize Form and drop the fields they do not need from their own incident form.
- CCreate a second incident table with the six required fields and point the hardware technicians at that table instead.
- DCreate a new form view holding the six fields and add a view rule that applies it for the hardware technicians. Correct
Why A is wrong: Tempting because it does produce a shorter form, but hidden fields still occupy the layout and every future field needs adding to the policy, so the maintenance grows with the form.
Why B is wrong: Tempting because personal layout is quick and needs no configuration, but it depends on each technician doing it and is lost for anyone who joins the team afterwards.
Why C is wrong: Tempting because a smaller table would certainly render a smaller form, but it splits the incident data across two tables and breaks reporting, assignment and the shared list the two groups work from.
Why D is correct: A view stores its own form layout for the same table and records, and a view rule selects that view for the matching users, so one set of records serves two layouts.