This content has been marked as final. Show 2 replies
If the custom section already exists on the spec, then the column will remain visible and editable. The reason is that we cannot change spec data from admin functionality. That spec could have been approved already, so it should not change unless it goes through the proper process.
When adding a custom section, the inactive columns should not show up. I just tested on a 126.96.36.199 build and it worked properly.
So which scenario are you referring to, new or existing custom section instances?
Which build are you using?