Signal names are not restricted by Engine and almost not restricted by XML attribute definition, but designer UI prevent users to set most of the characters.

This is very annoying for Case Management, since as signal names used Nodes names and nodes names doesn't have any restrictions on it's names.

Acceptance Criteria

Signal names on UI side should be limited by XML attribute chars limitations only as described in ML specification (Extended Backus-Naur Form (EBNF) notation is used)

AttType    ::= StringType
StringType ::= 'CDATA'
CData	   ::= (Char* - (Char* ']]>' Char*))
Char	   ::= #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF] /* any Unicode character, excluding the surrogate blocks, FFFE, and FFFF. */

Not clear points

• It is not clear what to do with " symbol, since it is possible to use it as node name (node name is stored in CDATA block), but this symbol can't be used without encoding/decoding in signal name, since signal name is attribute and attribute will be broken by unprotected " symbol, but engine not doing encoding/deconding as well.

Possible solutions:

• Do not allow to put " symbol for names (can be done only for Case Management)
• Use CDATA block for signal name as well as for node names
• Clear signal name from " symbol
• Implement encoding/decoding on engine side