A hyphen in Operator ID
Hello!
I have the following question: what's wrong with a hyphen in Operator ID? Why we can't create an operator since PRPC 7 with a hyphen?
We have a system upgraded from PRPC 6.2 sp2 to PRPC 7.1.9, and we had a lot of old users with a hyphen in their IDs. Will the system work correct for these operators?
I have found these support articles (https://community.pega.com/support/support-articles/special-characters-operator-id, https://community.pega.com/support/support-articles/issue-creating-operator-id-hyphen), but the didn't helped me to understand the problem.
Accepted Solution
The check should be done during the save of the operator to safeguard against problems.
You can save the data by running an activity to create the Data-Admin-Operator-ID record, but you may run into other issues down the line (I have previously seen problems with Bulk Processing when using operators names that contain hyphens).
FDBK-5918 had been raised to request for support the use of hyphen in the Operator ID.
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.
Our Product management team is aware of it and there is already an enhancement request for the same,
David Kircheis can you please review this post once and provide your inputs.Thanks in advance.
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.
Accepted Solution
The check should be done during the save of the operator to safeguard against problems.
You can save the data by running an activity to create the Data-Admin-Operator-ID record, but you may run into other issues down the line (I have previously seen problems with Bulk Processing when using operators names that contain hyphens).
FDBK-5918 had been raised to request for support the use of hyphen in the Operator ID.