Uploading simulations and a book page with long text and subsequently converting it into a hands-on

[Helenka]

I would like to ask for your help.
I need to create a methodology for the S4/HANA application. It will consist of screenshots (simulations), but before these screenshots, there must be 3 pages of written text (introduction to the application, description of the fields found in the application). I tried inserting a book page into the simulation, but the text is too long and doesn't fit into a single book page.

I need to then convert the entire simulation into a Word format and have it translated into English using a translation machine. Is there any way to insert long text into the simulation and make it scrollable? Can users scroll through it later in the library?

Thank you so much for your reply, and have a nice day.

Helena 

[ShaneLipke · Accepted solution]

Hi Helenka,

It sounds to me like that you are trying to generate a Compound Document in Enable Now.  This Compound Document could consist of the content from multiple Book Pages and Simulations. 

As Bart mentions below, you have quite a lot of control over the way that content generates using Enable Now.  For example, you can modify the formatting of the content using Text Styles, the documentation templates located in the Resources > Adaptable Resources > Documentation Style section, and the documentation settings located in the Resources > Documentation Settings area in Producer.  For more information on the setup of your documentation, refer to this video.

Once you configure your documentation settings, you will need to structure your documentation into the order that you want it to generate into the documentation.  So, if you need the content of 3 Book Pages in front of the content of 10 Simulations, add the 3 Book Pages to a folder (Group) object, followed by the 10 Simulations.  Then, click on the folder in the Explorer view of Producer and select Documentation > Generate Compound Documentation.  This will generate a single document containing all the information in the objects that are child objects of your selected folder object.

It is possible to display this generated documentation in a library but it is best if the generated PDF documentation is loaded into Enable Now as Media Objects.  If the documentation is added into your content structure as PDF objects, they will not appear in the content hierarchy of your library.  If you reloaded the generated PDF documents into Enable Now as Media Objects and place them into the library structure, they will appear in the library structure and be easy to access by users of the library.

Good luck!

Regards
Shane

[BartRhoten]

In the workarea tree, each simulation has a Description field. This is for text, pictures, and the occasional video, but it doesn't have all the bells and whistles of a Book Page. The Description field should do what you need to do - have a lot of text. Paste your text into there as Plain Text, format it the way you want, and then when you generate your Word document from the simulation (such as a Standard document), make sure that your Tools > Settings > Documentation Settings > [document format] > Fragment section includes the Description (which Standard format does by default). Generate the document, and your pages and pages of text should display before the screenshots in your simulation. 

You can then send that Word doc out for translation. I always use the Producer's Automatic Translation function, which will spit out the Description text in either Word or XLIFF for your translator service to process. You can also use the SAP Translation Hub, which is included in your Cloud SEN subscription.

You can embed the same text in a Book Page that is linked into your sim, as you noted, and the text box is scrollable by default unless you turn off the scroll function for it. Users may not notice the scroll bar, so I would call their attention to it at the top of the text in the text box. 

You can also use the Scrollable Book Page. There is a template here SAP Enable Now Info Center . I don't know which would be more obvious to use for your users. 

Shane or other smart people, please correct me as needed.