Would like special characters  in Chorus comments to error before a user is able to add the comment

[budrigby]

Prior in Classic AWD users were not able to copy and paste a special character comment.  AWD would error out and not allow the user to paste the comment. We would like this functionality to be added to Chorus Processor Workspace.

Once we had users in Legacy Processor Workspace and current Processor Workspace they have been able to add special character (nonunion) comments and this causes the object to completely error out when it is opened again.  Updating the comment and removing the special character () does not resolve the issue. Our only work around is to have the user create a new object and copy and paste from the previous Chorus comment.  Copying and pasting the comments from Chorus does not cause the object to error, only when we copy and paste from our other documentation and websites.  

This is in response to ticket CS0047171 and CS0039472

[HaleyHuffman]

This is defiantly needed! I think this should be a fix really because it shouldn't error on any sort of character.