There is some 'magic': When "Show Operational Attributes" is turned off and you add an operational attribute or an attribute not specified in the schema then it is turned on automatically.
Maybe we should rethink about this "Show Operational Attributes" checkbox.
Currently it has two functions:
1st: A filter function for the entry editor. When displaying the attributes of an entry there is a check if it is operational. This is the case if the usage differes from "userApplications" or if the attribute type doesn't exist in the schema at all.
2nd: Whether to fetch operational attributes from the directory or not (add a "+" to the list of returned attributes or not)
I think it would be better so separate these concerns:
The "Show Operational Attributes" checkbox should only have the filter function, like the other checkboxes "Show objectClass|must|may attributes".
Whether to fetch operational attributes from the directory should be configured diffently. I'd like to suggest to add an option in the connection properties for this which fetches operational attributes for each entry. Additional we should make it possible to fetch operational attributes on a per-request basis.