
Determining Action Profiles and Action Definitions
Use
This procedure describes how you determine action profiles and templates using the PPF user interface. You can call this transaction either directly or in the Implementation Guide of the relevant application. The latter procedure is recommended because the application-specific documentation is provided in the Implementation Guide. This documentation only describes the settings options in general terms.
The applications provide the default settings for the action profiles and templates. Some default settings (like, for example, for the applications and contexts) must not be changed. For more information, see the documentation for the relevant application.
Procedure
Application-specific call
The procedure is described in the documentation for the relevant application.
Direct call
.Creating and Changing the Action Profiles and Templates
By using the symbol
you can go to change mode.
Create and change application
The date rules defined in the date profile can be used for the formation of time-dependent conditions.
.Create and change action profile
The context class created by the application developer should be specified here.
If you want different settings to those given in the application (see above) to be used, you can enter these here.
.Create and change action definition
Here you can enter the default setting for the partner function, at which the action is directed. The partner function is preset when an action is manually created. (This is also called the partner function in CRM.)
Select this field if a partner determination is to be performed. In this case, the application developer must transfer a partner class to the PPF.
Enter whether an automatically found action can still be manually changed.
Enter whether the user of the action can be triggered manually during editing of the document.
Enter whether the action is to be displayed for the application document in the toolbar of the generic object services. This only happens if the object type of the application document supports the object services.
Enter whether actions of this action definition are to be deleted immediately after they have been successfully processed. The actions are never deleted automatically if there are errors in the processing.
Enter the technology with which the actions are to be found.
Enter the technology with which newly found actions are to be merged with existing actions.
The context class attributes can be used as fields. The display or processing can be sorted according to these fields.
.
.Set processing
.If you use processing using SmartForms, note the following:
You must enter the name of the form that is to be used. You must also enter your processing class that the application developer has created, and the processing method, with which the actions are transferred to the SmartForms.
If your application supports optical archiving using ArchiveLink, you can set in the store mode field that the executed actions are automatically archived with the application document. For this, you must make settings such as archive object type and document type in ArchiveLink.