Definition Of A Scenario

Use

You define a scenario for each internal service requestfor which you later want to provide a form. A scenario is the technical description of a particular internal service request in Customizing.

Prerequisites

Since internal service requests are based on general notifications, you need to make settings in Customizing for notifications. For more information, see the Implementation Guide (IMG) under Start of the navigation path Cross-Application Components Next navigation step Internet/Intranet Services Internal Service Request Scenario Definition Prepare General Notification End of the navigation path .

Features

A scenario defines the appearance of an internal service request and how it is processed in the workflow. Particularly important are the fields in the request form in which users enter data, and the function of these fields.

For detailed information on the options for making settings when you define a scenario, see either the following sections or the documentation relating to the IMG activity under Start of the navigation path Cross-Application Components Next navigation step Internet/Intranet Services Internal Service Request (ISR) Scenario Definition Define Scenarios End of the navigation path .

Note Note

To simplify the definition of a scenario, the ISR Wizard is available that you can find in Customizing under Start of the navigation path Cross-Application Components Next navigation step Internet/Intranet Services Internal Service Request (ISR) Scenario Definition ISR Wizard. End of the navigation path This systematically guides you through the greater part of the settings for a scenario. When you activate a scenario created in the wizard, this scenario is available in normal Customizing and you can continue to process it. For more information, see the documentation for the ISR wizard IMG activities.

End of the note.

Actions

You define scenarios in Customizing under Cross-Application Components Internet/Intranet Services Internal Service Request Scenario Definition Define Scenarios .

Note
There are predefined scenarios that you can copy and adapt to your requirements (see Scenarios Provided ).

End of the note.
Under Basic Data , enter at least a name, a description and a long text, and the Entry Type in Web . Additional settings are needed with the following entry types:
- Entry Using ITS Service : Define an HTML form (see Definition of an HTML Form ).
- Entry Using Adobe PDF : Generate an Adobe PDF form (see Definition of an Adobe PDF Form ).
- Entry Using BSP : Specify a BSP application. An example application is ISR_DEMO1.
For a scenario that incurs costs , define rules for calculating the costs.
Create characteristics and name them. If necessary, assign a type to the characteristic.
Create tasks and name them. Enter a person who is to be responsible for the task (either direct or through a standard role).

For more information, see the documentation for the IMG activity Define Scenarios .