Question
Last activity: 27 Aug 2015 9:28 EDT
Why is there a 30 char limit on the JNDI Property Name and Value pairs on the Custom Properties tab of the JNDI Server rule
Anybody know why is there a 30 char limit on the JNDI Property Name and Value pairs on the Custom Properties tab of the JNDI Server rule?
for example we have a jndi property name = java.naming.factory.object with a value = com.tibco.tibjms.custom.CustomObjectFactory (44 chars).
Cheers,
Barry.
Pegasystems Inc.
GB
I think that as well as finding out the Reason for the business decision to restrict that field we need to know if there are any repercussions if you modify the field using the workaround where you do a private check-out of the pzCustomProperties section on Data-Admin-Connect-JNDIServer and altered the Max chars on Presentation tab
This limitation does not seem to exist in earlier versions.
I tested in ML4 and there I was able to save names longer than 30 characters:
I think that as well as finding out the Reason for the business decision to restrict that field we need to know if there are any repercussions if you modify the field using the workaround where you do a private check-out of the pzCustomProperties section on Data-Admin-Connect-JNDIServer and altered the Max chars on Presentation tab
This limitation does not seem to exist in earlier versions.
I tested in ML4 and there I was able to save names longer than 30 characters:
--> Does this have anything to do with the change with Ruleforms where now some are Harness based versus some which are still form based?
--> And if so, can the fact that this has now restricted the Min/Max chars be considered as a new limitation/bug?
This is clearly a bug. Enter a Support ticket with us and we'll get it addressed.
Pegasystems Inc.
GB
Thanks Vipin. This was already logged under SR-A5050 (see 'Related Work' on the right hand side bar).
I will send this to Engineering now.
Accepted Solution
Pegasystems Inc.
GB
HFIX-23380 now exists. In the hotfix they have Removed max chars.