Error adding number as string within configuration element

[FSvcoe]

Just noticed when I attempt to add a new attribute of string to a config element, it will not allow you to type a leading number as the name-you have to enter a character, them numbers, and then backsapce the character out. Not sure if anyone else has encountered this....

[cdecanini_]

I confirm this is the case. Funny thing is I use config elements since the first build of vCO that had it (was VS-O back then) and never had the idea to start a configure element with a number.

I have found a work around if you really need this. Here is the result

Here is how: You need to script it to avoid input checking:

Set a workflow with an input of type configure element, then add a scriptable box, add the config as input and do:

config.setAttributeWithKey("1Test","");

Christophe.

[FSvcoe]

Chris,

We use it as a storage array number lookup, so it needs to be numeric. As described, I can simply enter a character, then numbers, then backspace out the number, and it will save the number correctly. Works fine as a workaround, just something to add to your list. Thanks.

[cdecanini_]

Can't you use the work around I posted ? You could even import a long list from a file to have these created automatically.

If the UI issue is a problem then please open a support request at GSS. Issues opened by customers / partners have the priority.

Christophe.

[FSvcoe]

Thanks, but we're not presenting this in a UI. It's just defined once for the workflow to reference. Not a big deal, just took a couple of minutes to figure out what was causing it. BTW-Couldn't paste the value in either.