Class: Security

[Dean Roddey]

As of 5.3.926, the zone security semantic field type has been updated to include a Bypassed option.

Also, the Unknown state should be reported via trigger, where it was ignored before. There is some possibility that this might cause some backwards compatibility problem, though probably not. If you had a triggered event that was not checking for specific states, then it already must be pretty generic and having Unknown reported won't make any difference.

The reason for this is that, even if you don't care about a change to unknown state, you may care about leaving one of the known states. So if you are keeping track of the state, you may want to know that it's no longer secure, even if you don't know the actual new state. You can store the new state and still watch for subsequent changes.

I'll update any shipped security drivers. In the immediate term, if you have one of your own that's not shipped, not having the Bypassed value isn't going to kill anything. But you can easily add it to the field limits even if you aren't immediately (or never will) use it. If you were explicitly filtering out sending triggers for Unknown, just remove that filter.