When a separator is defined anything that is written in the separator option is considered a separator. This becomes an issue when the client uses one of the separators while defining element code or task code. The rule doesn't work properly.

Example
The element with code value "A-B_1 WSD" needs to be assigned to a task. But the task has multiple such elements to be linked to it. Task code is defined as "A-B_1 WSD; A-B_1 WCD; A-B_1 WKD".
The separator between each element code value in the task code is "; " there is a space in the separator. But as the element code value also has space, the rule takes into account the value up to the space defined in each element code value eg "A-B_1" only.
There has to be a more refined way to mention that the separator is a combination of semi colon and space "; " and not only a space " ".