In this presentation, a SAP Support Consultant from ArchitectSAP Solutions will find about important concepts and practical guidelines for building state-of-the-art freestyle SAP WebDynpro user interfaces.
For More Information, Please visit:-
http://www.architectsap.com/blog/sap-netweaver/sap-webdynpro-best-practices-for-design-and-development/
2. Today's time is a technological time. In today's world
newer languages, devices and innovations develop and
vanish nonstop and thus the fundamental test for any
instruments or technologies is to keep up their quality over
others.
SAP is one of the those who succeed to keep up there
quality.
Writing code is easy but writing a good optimized code is
very hard.
In this presentation, a SAP Support Consultant from
ArchitectSAP Solutions will find about important concepts
and practical guidelines for building state-of-the-art
freestyle SAP WebDynpro user interfaces.
3. The first essential piece of any application
development is to discover which code fits in with
which part and ought to be kept in which part, so
unnecessary hops and overhead should be lessened.
As a beginner the vast majority of programmers have
used to store quite much logic in their main
component controller.
Rather than this you can separate reusable logic far
from the component to assistance class and to
different business classes.
Along these lines you can utilize business schedules
again or even change/duplicate assistance class for
an alternate reason.
4. Following points definitely help you to create good context elements.
A standard naming convention ought to be utilized for setting hubs and
elements.
Try to stay away from different trips to the database or other outer
articles to get the information by holding a bigger dataset in the Context's
memory. Store information transparently by utilizing the Context instead of
buffering through ABAP or Java systems.
You can populate the connection information through Supply Functions
as opposed to inserting code in initialization methods.
Always make standard connection nodes in the Component Controller
and map to views. Typically make a context node for holding information
identified with properties of the views and an alternate for holding client
determination data.
Simple data types might be put away in Web Dynpro Attributes instead of
the context. This decreases the measure of code needed for getting to the
information.
5. Always utilize a standard naming convention for the method/action.
Methods that are often called/utilized ought to be kept as a part of
common piece of the application say a Common class or a common
controller.
Context components that are often called for upgrades could be
encapsulated in a method, it will help to decrease extensive measure of
code required.
Attempt above tips it will help you to create a decent WebDynpro
Application.
Have a question on this topic? Please read more on:-
http://www.architectsap.com/blog/sap-netweaver/sap-webdynpro-best-
practices-for-design-and-development/
6. Always utilize a standard naming convention for the method/action.
Methods that are often called/utilized ought to be kept as a part of
common piece of the application say a Common class or a common
controller.
Context components that are often called for upgrades could be
encapsulated in a method, it will help to decrease extensive measure of
code required.
Attempt above tips it will help you to create a decent WebDynpro
Application.
Have a question on this topic? Please read more on:-
http://www.architectsap.com/blog/sap-netweaver/sap-webdynpro-best-
practices-for-design-and-development/
