A user adjusts which columns appear on their incident list using the personalisation control offered on the list, saves the change, and then asks why a colleague opening the same list still sees the original columns. What accounts for the difference?
- AList personalisation is stored as a preference for the individual user, so it alters that user's own view of the list and no other. Correct
- BThe colleague holds a different role, and column choices are stored against each role rather than against the list record itself.
- CThe change waits for the next instance cache flush, after which every user opening that list receives the revised column set.
- DThe list was reached from a different application menu entry, so only the layout attached to that entry governs what appears.
Why A is correct: Correct because personalisation writes a preference tied to the user who made it, which is why the colleague continues to receive the shared layout.
Why B is wrong: Tempting because roles do govern much of what a user sees on the platform, but column selection is not stored against a role, so this misplaces where the setting lives.
Why C is wrong: Tempting because some administrative changes do need a cache to clear, but no flush will ever promote a personal list choice into a shared layout.
Why D is wrong: Tempting because navigation can open different views, but the menu entry used to reach a list does not turn a personal column choice into a shared one.