Action triggers VIEW_TRIGGER_EVENT_DEF permission could be improved

[Steve Callender]

I tested this in 2.7.8 but I suspect it's happening in all releases. Not so much a bug as more of a design issue.

When a user is limited to system only VIEW_TRIGGER_EVENT_DEF permissions, what appears to happen is the notification / trigger screen still loads all the events but then just eliminates the rows on screen that the user doesn't have access to view. This may not be a common need however as it also eliminates consortium events, but I just wanted to document the behavior.

So let's say the system the user has permissions to view only has 10 events out of 200 total events in the action_trigger.event_definition tables. When going to the screen, limited to viewing just those 10 events, the screen may display 1 on the first screen. Maybe 2 on the second screen. Maybe none on the third, and so on. It spreads the events the user has access to view out across all the screens as if the user was able to see all the events, and you have to repeatedly hit next to see them all.

A work around is to just filter on your own system which causes just those events to be lumped up on the first page.

Steve