Dynpros are a little different, it is dynamic program, they allow the user to execution of the program and web process a series of screens which called dialog screens, the user determine the flow of the program itself by choosing which button of fields to interact with the screen, that action can triggers different functions that can be coded with the flow logical of the programs.
The following topics are included in the course:
Messages are a text is displayed on the user, for example, when the user enter data incorrectly, or when an error occurs in the application is running, and messages are displayed based on the language selected by the user.
And messages that appear to the user (such as information, error messages, warnings), and components of the messages is a part of every Web Dynpro application.
User messages are displayed if the individual in the form of links, or in the form of a table if the multiple, in the case of single-user can move on to the user interface by clicking on the link to remove the error, this adds to the efficiency of the messages.
Roadmap screen elements:
The Road Map UI element displays the steps followed in a wizard. Each step is represented by a separate Road Map Step object or Multiple Road Map Step. You can use the code from several symbols available, to determine the start and end points of this user interface element.
If more than the value of the start Point Design or end Point Design , this indicates to the user that there are other steps is the first step visual or after the last visible step.
The Road Map UI element helps the team to display small steps and clear the entire process because it displays step-by-step workflow.
At the time of the implementation process of the establishment of an interface in each component of the program components, this interface contains exactly one interface controller and at least one interface viewØ? the interface controller contains a context, events and methods.
Within the component the interface views and the interface controller there is no direct contact between themØ? Therefore they are generated automatically for every window that is created The component interface is implemented exclusively in its related component; it cannot be implemented in other components. The programming environment of Web Dynpros now allows you to enhance this pre-implemented interface by implementing additional interfaces, which have been definedÂ independent of a component.
Component interface definitions allow you to generically define a uniform interface structure and later use it in a variety of application components.
In fact, the importance of this measure is that it all the ingredients that are used in the interface definition contain a certain set of controls such as (methods, context elements, etc.), Developers can be treated interface views by the use of ingredients, The developer of a using component does not need to know which actual implementation of the interface is used â?? this can be determined dynamically at runtime.
Copyright ERPTRAINING9.COM 2009 - We are not affiliated to SAP AG