Can Rule-File-Binary rule ID take illegal characters?
We have just found out that Rule-File-Binary can take space or illegal characters such as &, ', etc. Usually any rule type like property you can't have such characters in rule ID. Is this product's defect to forget to validate Rule-File-Binary rule name or is this developed as such for special purpose?
We want to verify this because when user download binary file from screen, the file name becomes rule ID (not short description). We use Microsoft Office for binary and it would be more user friendly if we can use these characters for downloaded file name.
I have verified the same use case in 7.1.9 and it goes well for me as expected. When you provide "Rule & ID" as label while creating the rule, it omits the spaces and special characters while generating identifier for the rule.
Things to be checked -
1. Is it happening only for "Rule-File-binary" rule?
2. Could you please trace the gap when you modify the label and the identifier generation to see if any of the customizations are done?
PRPC has Edit Input to automatically trim space or illegal characters when you focus out of Short Description. You need to "Edit" to change the ID if your setting for rule ID is read only. Try edit again.
This behavior happens only for Rule-File-Binary rule type and not other regular rule type like Property or Flow rule. I tried in 7.1.9, 7.2, and 7.3 and all behaves the same. Of course there is no customization and it is out-of-the-box specification. My question was if this is designed as such or some kind of defect to forget the validation properly.
No, we are not facing any issue or even this specification is better for us because when user downloads this binary file from UI, the downloaded file name becomes this rule ID, while I was expecting the short description to be it (I think that is a better design as a product). Customer has space, ampersands, apostrophe, and some odd characters usually in Microsoft word document name and they want to use as is as much as possible. And I am guessing that is why product team did this handling for Rule-File-Binary specially. I would like to get verification from product team for my analysis. Can I take this as product functionality then we will use it as such, but if it is a product defect for any reasons and there are some risks to take illegal characters then we won't use it.