Enable Now - Bad connection. Try to reload error

[pengfei_rornl]

Having issues getting Ariba Guided Buying to connect to extended workarea content.
1. Standard workarea content is connected

2. A custom workarea is created and extended with the standard content. (Moved content from unsorted into rooted folder and also fetched content)

3. Setup the SAP Companion integration connecting to the standard Guided Buying snippet (Used the custom workarea ID + turned off Ariba Standard content toggle)

4. Pulled the URL from SAP Companion integration and set it up in Guided Buying.

When accessing the "?" icon in guided buying; the system consistently throws a "Bad connection. Try to reload" error. I've tried to enable standard content toggle in my described step 3 above. While the system pulled up content for me to view; the system does not allow me to make edit to the content in app.

[DirkManuel · Accepted solution]

Did you enable CORS in the SEN Manager Server Settings?

Also, re: your Step 2 - you don't need to move the content from Unsorted to under Root (in fact, it's sometimes better if you don't), and you don't need to Fetch the content unless you want to change it - it will still be visible to users; that's the beauty of Extended workareas.

(Also check that Learners have Display Published Content permissions against both Workareas.)

Hold on: In Step 3 why do you have an Extended workarea and then turn off using Ariba standard content? Why don't you just not have an Extended workarea? I guess technically it will work as you have Fetched content anyway, but that's not really how it's designed to work...

[pengfei_rornl · Accepted solution]

It was CORS setting issue after some troubleshooting, and specifically it had to do the the COR's allowed URL values.

Original value: *ariba.com

Value that worked: *.ariba.com

The extra period in front was the connectivity issue.

Thanks you!

[Anton_Mavrin1]

Hi pengfei.rornl,

Please check what's going on in the internet browser's developer console. (Ctrl + Shift + i). Navigate then to the Console tab and check all these awesome errors highlighted in red;) Some of them will likely be thrown by the SAP Enable Now or Companion.

P.S. Have you also enabled the CORS-allowed sites in your SAP Enable Now Manager?