--------------Original Comment History----------------------------
Comment from = cf126330 on 2016-01-12 18:28:33 +0000
The spec should give a clear rules which chars are allowed and not allowed in job, step, decision, flow and split id string values. This will help apps save and exchange job data more easily and consistently.
The spec currently only says they are valid "XML string value" (more accurately ID).
For instance, I need to store a list of job ids, separated by some delimiter. I should be able to pick one that is guaranteed will not appear in any job id.
Originally opened as bug 7479 by cf126330
--------------Original Comment History---------------------------- Comment from = cf126330 on 2016-01-12 18:28:33 +0000
The spec should give a clear rules which chars are allowed and not allowed in job, step, decision, flow and split id string values. This will help apps save and exchange job data more easily and consistently.
The spec currently only says they are valid "XML string value" (more accurately ID).
Some obvious blacklist chars: whitespace anywhere \ / = , * # { } ? :
. (dot) should be allowed.
For instance, I need to store a list of job ids, separated by some delimiter. I should be able to pick one that is guaranteed will not appear in any job id.
A maximum length of id will also help.