SAP Companion content - Moving from test to production

[marie_pelstring]

Hello,

we have created content for SAP Companion in our test environment. Now we want to move this from the test environment to the production environment. To do this, we have exported the content in the test workarea and imported it into the production workarea.

At the moment, the imported content is not visible in the SAP Companion carousel, not even for admins and not even in the editing view.

Has anyone had this problem and can give us tips and tricks?

[Anton_Mavrin1]

First impression: you did a lot of potentially unnecessary actions: I mean moving SAP Enable Now content from one workarea to another, instead of just applying the same SAP Companion configuration to you Prod system.

If nobody (even authors in the editor mode) can see the content you migrated, the Chrome or Edge browser developer tools are your best friends to spot the issue. If there is something wrong, with the authentication or else, you will see it in the developer tool console.

[ShaneLipke]

Hi Marie,

There could be a number of issues:

1. The SAP Companion configuration is not correct or complete in Production
2. If you are trying to access the content using and Enable Now Learner account, the content must be published in the Production WA
3. The Workarea Permissions may not have been setup to allow users to access content from the Production WA

My initial guess is it's the first item that is the problem but it's impossible to say without more information.  You can either post a screenshot of your SAP Companion configuration here so I can check or raise a support ticket using the Component ID KM-SEN-CMP and get someone to take a closer look.

Regards
Shane

[BartRhoten]

Anton and Shane are correct as always. Companion is designed to pull content from up to two workareas (Context Help and Guided Tours come from a designated workarea, and Learning App content comes from a designated workarea. Typically they are the same workarea but they do not have to be). You built your content in the designated workarea that Companion is configured to look at. By moving the content (unnecessarily, as Anton said), you probably now have it in a workarea that Companion is not configured to look at. SAP Enable Now does not work like SAP ERP systems, in that it does not require more than one workarea/instance. You build your content in the Production workarea of SEN, and you play/deploy it from there. There is no promotion from one workarea to another as content is developed.