About structuring the Standard content in Extended... - SAP Community
source link: https://community.sap.com/t5/sap-training-and-change-management/about-structuring-the-standard-content-in-extended-workarea-in-sap-enable/td-p/13638503
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
yesterday
Hi All,
As part of SAP Companion configuration, I established a connection to SAP Standard Content and got the Connected Workarea. Next, when I created the Extended Workarea based on the Connected Workarea, all the standard content from SAP is copied into the Extended Workarea. By default, the standard content is loaded under the Unsorted folder, as shown in the picture below:
Question 01: Can the standard content remain under Unsorted? OR, As a best practice, should I move it to a separate Content folder created outside Unsorted? In addition to standard content, I will be creating lots of custom SAP Companion content as well? In that case, can my custom content + standard content be under the same Content folder? Is there any best practice for that? If I move the standard content to a different folder, will there be any issue when the standard content is automatically refreshed?
Question 02:
How frequently is the standard content refreshed in my Extended Workarea? If I happen to edit any standard content in my Extended Workarea, will the edited object be reverted when the standard content refresh happens?
- Labels:
- sap enable now
Hi Angad,
Just like custom content, it's best not to leave standard content under the Unsorted folder as well. You can move the content out of the Unsorted folder by moving the Ariba Content out of Unsorted; this will also move all child objects at the same time.
It's up to you how you structure the standard content, primarily Simulations, but my personal preference would be to keep this content in a separate part of the content structure. The benefit of this is that you are unlikely to use every standard object so it makes more sense to me to create a structure that contains your custom content and the standard content that you do want to use.
SAP Companion content can be moved into the same structure but is likely to be broken off into a different path very early in the structure. For example, at a point very high in the content structure, you are likely to have a node for your content library and at the same level a node for courseware and a node for SAP Companion content. The reason for doing that is that the library structure and the courseware structure will likely be different. The content structure for SAP Companion content will be different to the structure for the library and courseware so each delivery approach then has its own structure.
The following image shows an example of how you might structure your content:
Standard content is updated on a regular basis, at least new versions are added regularly. If you modify - Fetch - the standard content in any way, you disconnect your version of the standard content object from the standard. If you do this, your version of the standard content object is not updated, in the Extended WA, when the SAP author updates their the standard object; it is still updated in the Connected WA. To get the version of the standard content object to show the latest changes, in the Extended WA, you must delete the modified version of the standard object in the Extended WA. This will immediately reset the object to the standard version. If you want to keep the modified version of the standard object and get the latest version, duplicate the modified version of the object, and then delete the original version.
Hope this helps.
Regards
Shane
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK