Targets

A navigation target defines an end point (e.g. transaction, report, etc.) using a previously defined handler. When the navigation target is defined, the corresponding handler is fully parameterized using the parameters.

The possible parameters and values are provided by the handlers using F4 input help.

Navigation in ProFramework

For the navigation in a ProFramework application there are basically different approaches available:

• Starting an application with transfer of the object type and key

• Starting a designated command

• Starting a designated command with specification of an application

The start of an application optionally leads to the display of the passed object. However, if the navigation target is determined via a Navigation , then an action (Change, Create, etc.) may also be available. If the action is either Change or Create, then an attempt is made to execute this action. However, the application is not terminated after completion of the action and accordingly no data is returned.

To start commands, they must be prepared accordingly. For this reason, only commands that fully support an external call are available in the search help for the COMMAND parameter. In contrast to the start of an application, the application is terminated after the command is completed. In principle it is possible to take over the key data after completion of a command (object type and key). For this purpose, further parameters must be maintained.

Since commands are internally also based on parameters, these are transported back completely. Al-lerdings is also view of the navigation not automatically determinable, in which of the parameters the object key is stored. Therefore, the NEW_OBJECT_KEY parameter must be used to select the corresponding export parameter of the command. Furthermore, it is not recognizable from the command which object type is processed with it. For this reason the object type must also be made known with the parameter NEW_OBJECT_TYPE.

If a command is executed directly, then a layout with widgets is automatically created by the command. For this reason, in addition to a command, an application ID can also be passed when the command is called. If an application is defined, then the command is started, but the appropriate application is used for it, which can define its own layout for the concrete command. The prerequisite for this, however, is that the command can be executed in the application. For commands whose widgets are based on the so-called Custom View Engine, the layout of the data widget can be transferred depending on the command. This makes it possible to start commands without an application, but still influence the layout.