ABAP_to_the_Future

Using Floorplan Manager to Modify Existing WDA Components 12.3
presses a button. You will see that the list of methods in Figure 12.30 is shown in
alphabetical order. The following list is a rundown of what each new method
means in the order in which they get processed at runtime:
왘 FLUSH
This goes first! The flush is the data transfer method from the UIBB to the
backend. The controller is the backend in this case—it needs to know from the
view layer (the UIBB) what the user just did.
왘 NEEDS_CONFIRMATION
You can pop up a box, such as one that says, Are you sure you want to launch
that Nuclear Missile?
왘 PROCESS_EVENT
Fire the missile.
왘 AFTER_FAILED_EVENT
This is for error handling, and it’s nice to see this built into the framework.
Here you can deal with what happens if something goes wrong with the missile
launch.
왘 PROCESS_BEFORE_OUTPUT
Process before output is a term we all know and love. In this case, before you
show the user the screen again, you want to update the display (e.g., add a success
or error message, or maybe remove the missile that was just fired from the
list of possible missiles that can be fired).
The important thing is that once you’ve added this interface to a WDA component
it then becomes visible to FPM.
The next step is creating another WDA application for our WDA component. Go
to the root node, and choose Create 폷 Web Dynpro Application. The screen
shown in Figure 12.31 appears.
Figure 12.31 Creating a New WDA Application for FPM: Part 1
551