Endevor Web Services - Package actions failing when package includes whitespace

Document ID : KB000118278
Last Modified Date : 26/10/2018
Show Technical Document Details
We are currently working with the Endevor Web Services feature in order to assist in package automation. Our standards have the package ids composed of two pieces separated by a space. As a result, when trying to do any package work we are returned with a EWS0700E message Example for /packages/07R247%20AAAAAAAAA/Cast { "returnCode" : "0012", "reasonCode" : "0000", "messages" : [ "EWS0700E The packagename 07R247 AAAAAAAAA is not valid. Valid are characters, numerics, nationals and maximum length is 16. " ] } Looking at the processing, this does not make it past the web application to spawn against Endevor so the failing seems to be on the server application side. Can CA advise on how to appropriately handle spaces in packages or see if this may be a bug?

Why do RESTful API calls fail when the package id has embeded spaces ? 
Endevor Release 18.0
This is resolved by an enhancement (P7441) under release 18.0.12. Apply RO93964