EPM generating Grandstream config file problem

I found this behaviour in EPM 16.0.64.3 :

• if I added to Grandstream template string with spaces like this:

  
  P4200 = { x+ | *x+ | *xx*x+ | **x+ }

  Encoded in config file looks like

  
  %7B%2Bx%2B%2B%7C%2B%2Ax%2B%2B%7C%2B%2Axx%2Ax%2B%2B%7C%2B%2A%2Ax%2B%2B%7D

  Decoded is

  
  {+x++|+*x++|+*xx*x++|+**x++}

  Spaces are changed to "+" (plus) in generated config file.

• if I remove spaces from string in template all is ok
  This is change in behaviour against previous versions EPM.

Solution for me is change:
P4200 = { x+ | *x+ | *xx*x+ | **x+ }
to
P4200 = {x+|x+ |*xx*x+|*x+}