Issue  

In WebEmbed, when users open an assignment and click Cancel or Save for later buttons, the assignment will not move into Review mode.  Instead, the user sees a CORS error in the browser console.  

Symptoms  

When users access the case flow and click on the Cancel or Save for Later buttons, a CORS error appears in the browser console: 

Steps to reproduce  

1. Create a WebEmbed and choose the Action as either Create a case or Open an assignment or Open a case and generate the code. 

2. Add the WebEmbed code to the HTML file.  

3. At runtime, open a case by clicking on the Go button then click on either Cancel or Save for later.

4. The case does not go back to Review screen.  A CORS error is displayed, and the Delete/Update request does not execute. 

  Root Cause   

This is a product defect.  The service broker is incorrectly sending the x-pega-app-debug-levels header through the Cancel and Save for Later buttons during case creation in the Web Embed portal. 

  
 Solution  

The product currently cannot specify by default that the service broker should not send the x-pega-app-debug-levels header. 

To avoid this scenario, there is a local change: 

Add x-pega-app-debug-levels in the APIHeadersAllowed rule under Allowed headers field. 

Steps to implement Allowed methods and Allowed headers: 

1. Navigate to Configure-->Integration-->Services-->Endpoint-CORS policy mapping  

2. Review the endpoints and CORS policies listed below.