SAP Enable Now – Add new content to an existing workarea – Method 2
?In my previous article I discussed the process of adding new content to an existing workarea using a DKP file and Method 1 – Save to Server. Your takeaway should be an understanding of the process and the ability to perform it.
?In this article, I will review the process of adding new content to an existing workarea using a DKP file and Method 2 - Keep Locally. Your takeaway should be an understanding of the process and the ability to perform it.
The premise is we have content created in Enable Now, but it was not part of your original workarea. This could be content created by someone else in a development workarea, or from a different regional workarea that is now approved for use within your workarea. This is a common situation for global organizations that are incrementally rolling out Enable Now based training.
?The Keep Locally option is used when the new content has not yet been fully enriched and keeping it locally avoids anyone from using or accessing it in its unfinished state. The best practice is to use Method 1 – Save to Server, but as in everything, there are exceptions.
Importing the EDO folder
?We begin the process within Producer and select Workarea from the toolbar menu. If you read my previous article - SAP Enable Now – Add new content to an existing workarea – Method 1, you will notice that most of the steps are identical to what was previous covered. The value of writing a separate article is to bring attention to the differences between Save to Server and Keep Locally as it relates to the synchronization between Manager and Producer.
?From the displayed list, select Import Archive.
?A new window will appear with a list of available Backup DKP Files. Select the desired file. In this instance we are selecting the EDO_Customized – EDO – 12162022 file.
?Next, click on the Ok button to restore the file to Producer. A new pop-up window will display showing all of the components within the selected file. We could deselect parts we don’t want or leave everything checked and continue to download all of the file content. For this example, we will leave all boxes checked and select Ok.
?Next, scroll down and expand the Unsorted folder to locate the EDO folder.
?Left click on the EDO folder and hold while dragging it out of the Unsorted and on top of the destination folder and then release the button.
A pop-up window displays giving you the option to Save to Server or Keep Locally. We want to select the option to Keep Locally.
?The EDO folder is placed under the parent folder. If you notice the EDO folder does not have the edit pencil ICON as it would if we selected Save to Server. The parent folder is noted with the asterisk as shown here.
?With the parent folder selected, right-click to display the dropdown list and select Server Bulk Actions and then from the flyout menu, select Finish Editing All Objects.
A new pop-up window displays and since we want to include all of the content in the Finish Editing action, we leave all of the content checked and select Ok. Notice the EDO folder is not displayed under the parent folder. This is due to our selecting the Keep Locally option in a prior step.
Another pop-up window displays with the option to publish amongst other choices. In this example we will ignore the publish option and immediately click on the Finish editing button.
?We now see the blue cloud ICON on the parent folder indicating we are in sync with the server, but there is no similar ICON next to the EDO folder. Again, this has to do with our choice to Keep Locally.
Validating Manager Status
?To verify the Manager status, switch again back to Manager and locate the parent folder. We see it does not yet reflect the update, but if we refresh Manager, we see something new, a question mark on the EDO folder indicating it exists in Producer but not in Manager. This is what we expected to find.
Saving to Server
?When our imported content is ready to share, we need to save it to the server. From within Producer let’s start by highlighting the EDO folder and attempt to Finish Editing All Objects.
?We are presented with a pop-up message that indicates there are no objects actively being edited. Click Ok to continue.
?We highlight the parent folder and right click to present the dropdown menu. Select Server Bulk Actions and then Save All Objects to Server from the flyout menu.
?In the pop-up window we now see the EDO folder. I have expanded it here to reveal the contents within the EDO folder.
?Next, click Ok and then at the next pop-up we can select the Save to Server button. In the image that follows you can see that I checked the Publish checkbox. This is optional depending on your situation.
?In the previous step we saved to the server, but we did not finish editing as we see in the next image.
?We need to complete the process by highlighting the parent folder and Finish Editing All Objects as shown here.
The Finish editing pop-up window appears and I have again expanded the EDO folder to reveal its contents. Click Ok to continue the process.
?Another pop-up window displays with the option to publish amongst other choices. In this example we will ignore the publish option and immediately click on the Finish editing button.
?We now see the blue cloud ICON for the EDO folder and all of its contents.
Validating Manager Status
?Next, we switch back to Manager and refresh the window. After locating the parent folder and expanding it we can see the EDO folder and its contents are tagged with the blue cloud ICON and we can confirm the contents have been saved to the server.
Best Practice
?It is recommended that the Save to Server option be used as a best practice. Having Producer and Manager content synchronized is important when sharing assets across the development team. The exception is when the new content has not yet been fully enriched and keeping it locally avoids anyone from using or accessing it in its unfinished state. When the Keep Locally option is used, it takes much more effort to bring the Producer contents into alignment with Manager.
Summarizing the process
?Adding content from a different workarea using the DKP file and the Keep Locally option allows you to isolate the contents from other Enable Now users until it is ready to be shared. It does however add additional overhead effort to sync the Producer with Manager once the edits are complete.
?We also learned the validation steps are important and that it is much more complex for the Keep Locally option as compared with the Save to Server method. Your takeaway should be an understanding of the process and the ability to add new content to your workarea using the DKP file.
What’s next?
?In my next article I will discuss how to manage content from another workarea.
?If you like what I wrote please take the time to share it, as others may find it interesting, if not amusing. Let’s not be just consumers of information or share only the works of others. Your voice matters, and I’m sure you have good ideas that could help others. Try being a thought leader and not just a follower.
To those of you who take the time to read my efforts I sincerely thank you. I would be remiss if I didn’t remind you that this is a two-way conversation so put your comments in and let’s have a volley of ideas, so we all continue our intellectual growth.
Mr. Gray is a seasoned business strategist experienced in PMO stand up, digital and business transformation, process development, and best practice guidance. He has developed industry-leading methods for staff modeling, project deployment, financial performance, team onboarding, and business readiness. Mr. Gray is a problem solver at heart and a sharer of knowledge by choice. He has authored more than one hundred and fifty thought provoking articles which are all available on Linked-In.
If Mr. Gray makes you think then he considers the effort worthwhile.
Your PMI Guy can be found on LinkedIn at: https://www.dhirubhai.net/in/yourpmiguy/
Follow me on LinkedIn
And on Twitter at: https://twitter.com/YourPMIGuy