I opened a support request and was informed that the issue is a known bug that will be resolved in the next release...3.2. Not sure how such a bug made it past QA in the current release.
