use CORS choice not persisted in API when using Policy Template

Document ID : KB000099189
Last Modified Date : 04/06/2018
Show Technical Document Details
Issue:
 In the CA API Developer Portal 3.5 while trying to edit / create the API and selecting "Policy Template " Sample API Template encapsulated assertion  under Proxy Configuration tab , user tries to enable the CORS settings by enabling CORS via the radio button (TRUE/FALSE). However, after putting this setting, the enabled setting cannot be seen anymore in the same place ( radio buttons both empty). The only way to see what the setting is, to look in the service in Policy Manager. 
Environment:
CA API Developer Portal 3.5
Cause:
The issue was identified to be using  different encapsulated assertion.
Resolution:
The issue was resolved by creating a  new API Portal Sample Policy Template encapsulated assertion using the attached policy. This  template was selected for the API in CA  Developer Portal while editing the API.
Once the new template  was used the choice of CORS(true/false) persisted.
Additional Information:
This issue did not show up when Cors filed in encapsulated assertion was type String rather than Boolean.
File Attachments:
sample API Portal Encaps fragment.xml