Yaroslav,

I confirmed this limitation was added in PRPC 6.3. I also did a little digging and I didn't find any specific problems caused by the hyphens being in the operator name, but the SMEs tightened validation to no longer allow it and that was probably in response to something. Since that was done a couple of years ago, I'd be concerned that newer code specifically hasn't been written with that possibility in mind. You'd need to test your application to know for sure if you'll have any specific problems. It seems other people have replaced the hyphen with an underscore in the operator IDs to avoid the possibility of a problem.

Thanks,

Mike

We encountered issues in Pega 6.1 when the operators with hyphen character in the ID are created.

Basically issues in the JavaScript , Operators are created by automated way using activities , when they are opened for manual editing , browser started throwing JavaScript errors, which upon browser debugging we understood it is hyphen character which created that issue, when removed that hyphen it worked good. May be to resolve that pega would have introduced the limitation.

It seems the special character check against the operator id only happens if you create a new operator record using the new form of data-admin-operator-id.

I found it is possible to create an operator id contains hyphen by running an activity which copies existing operator id and set the pyUserIdentifier to a new value.