Recording a Document and Making It Available for Context-Sensitive Help

NOTE:

For Infor Ming.le, the recording must be performed in Internet Explorer and the Context Viewer enabled.  

NOTE:

For more information on recording, editing, and using the recorder toolbar, refer to the companion manual Creating Content.

NOTE:

Ensure that the Transaction Code(s) built-in property is marked as visible in the template. By default, the display of all built-in properties is disabled in the template.

Record and edit the document

1. Using the template you created in Creating a Template, record and edit the document using the Editor.
2. Go to the next step.

Insert steps into a previously recorded uPerform document

1. Update the template associated with the document.
2. Open the document associated with the template.
3. Select the Simulation tab.
4. Select Insert > Steps From Recording.
5. Record the steps using the Editor.
6. Edit the document.
7. Go to the next step.

Make a managed document available for context-sensitive help

NOTE: Refer to Adding a Managed Document and Updating Properties if you need to add the managed document to the Server.

Go to the next step.

Provide context-sensitive help using Oracle E-Business, SAP SRM version 4-6 or SAP Fiori and UI5

NOTE: For Oracle E-Business, specify an author account as described in Specifying an Author Account for Oracle E-Business.

NOTE: For SAP SRM 4-6, perform the steps described in Modifying the Workplace Integration API.

1. Revisit the screens in the application for which you want to provide context-sensitive help, and click on the help icon on each screen captured in the recorded document.

   NOTE: This will open up a new browser window containing the context identifier for the screen.

2. Highlight and copy the context identifier string from the browser window.

   NOTE: For SAP Fiori and UI5, copy the value of the Terms field on the Search Results page.

3. Repeat until context identifiers for all screens within the procedure have been collected.
4. Go to Step 4.

Provide context-sensitive help using SAP EP, SAP CRM Web Client, SAP SRM version 7, SAP GUI for Windows, SAP HTML GUI, Siebel, PeopleSoft 9, and generic web pages

1. If iView/Portal page IDs are not automatically collected, enable and include the iView/Portal Page IDs as needed.

   Refer to Enabling the Required iView/Portal Page Options, Locating the iView/Portal Page ID, and Including the iView/Portal Page ID in Documents.

2. Go to Step 6.

Provide context-sensitive help using Salesforce

1. Hover the mouse over the relevant “help for this page” or “XXXX Help” link for a given Salesforce screen.
2. Review the URL for the help link and note the value that follows “target=”.

   NOTE: The URL for a link you hover the mouse over usually displays at the bottom of the browser. In Microsoft Internet Explorer you may have to choose to show the Status Bar.

   NOTE: A typical “target” value is of the form filename.htm.

3. Drop the “.htm” part and retain only the filename part.

   NOTE: Some Salesforce screens, such as Opportunity screens, may have multiple help links. You must decide which of these you want to support from the CSH solution perspective, and your content creator must collect the context for each relevant help control and add it to uPerform documents that contain steps for the screen containing that help control.

4. Repeat until context identifiers for all screens within the procedure have been collected.
5. Go to Step 4.

Store the context at the document level

NOTE: Refer to Adding a Managed Document and Updating Properties to edit properties for a managed document.

1. Select File > Document Properties....
2. Select Properties.
3. Paste the context identifier(s) into the Transaction Code property.

   NOTE: Use a separator character such as a comma or semi colon between multiple context identifiers.

4. Click OK.

Store the context at the step level to take advantage of auto-scroll

1. For the relevant step, go to Step > Properties >Context Information.

   NOTE: Your uPerform file may contain multiple steps associated with a given application screen. You only have to apply the context identifier for the first step for a given screen.

2. Enter the context identifier in the Primary field.

   NOTE: Use a separator character such as a comma or semi colon between multiple context identifiers.