However, that would exceed the max length of pyLabel by one character, so Pega cannot modify the label as intended. To use a technical term, it barfs - Pega does something completely unexpected: it modifies both the label and the name of the rule like this:
The label problem is this is annoying but has a workaround: change the label value and save again
The rulename problem has no workaround other than to shorten the name of the function. For a function with a longer list of parameters, there is no workaround. To demonstrate this, I attempted to create a function with a one-character name, A, and enough parameters to exceed the length limit of pyLabel. Pega created this:
Maybe somebody else here knows whether this ID *is* somehow important to know....
If it isn't important (for Humans) to know - then I would say we log a Feedback Item, and basically show something simpler instead....(Curious mammals can always do a View XML if they really want to see the gory details I guess...)
I don't actually know whether I could call the function with the "normal" name when it is saved with the hex name. I guess I got spooked and ran off without trying that. I'll give that a go tomorrow and report back here.