Static Ranking in WebI 4.1

Hi Guys,
I have a requirement where I need to rank the data based on Total Cost. Basically, the report has 2 tabs. In the first tab,I need to rank by applying some filters which is done. Now the same table is copied in the second tab and if I filter it out ,the positions which were there previously are changing and its beginning from 1...n so on..But I dont want in that way. I need only those positioned rows to be picked to know which groups got approved or awaiting for technical repairs. Just the way as Excel does when filtered out where the positions of records/row numbers are static. Appreciate your help.
Grtz
- Anila.

may be you can explain the scenario better with some screenshots ..

Similar Messages

DefaultServlet bug? forwarding to static content under WEB-INF

I've encountered what seems to be a bug in the DefaultServlet in WebServer 7.0u2, when trying to do a requestDispatch->forward to static content (e.g., a .png file) under WEB-INF. In general, I can forward into content under WEB-INF, and my servlet works fine when forwarding to dynamic content under WEB-INF (e.g., a .jsp file), but when I try to forward to static content, a 404 error is sent. The same servlet also works fine if I put the static content outside of WEB-INF. In summary:
forwarding to /WEB-INF/foo.png responds with error 404 (even though the content exists)
forwarding to /WEB-INF/foo.jsp works fine
forwarding to /other-dir/foo.png works fine
I'm baffled as to why I can't forward to static content under WEB-INF. I have a very simple web.xml file, and no suffix-based mappings, so the only servlet that should be responding to the forward is the servlet container's DefaultServlet. Is there some bug in DefaultServlet? Am I misunderstanding something?

pl. upgrade to latest update (web server 7 u5 as of now) and see if your problem is still reproduced.

Cisco Aironet 2600 not responding after changing static IP using web GUI

Hey guys, I am hoping someone can point me in the right direction with this problem I am having. Over the weekend I changed the IP address of one of our remote Access points so that it would be in the correct VLAN for the building it is in. There are already 2 other AP's in that office and so I changed the IP/Default Gateway of our newly installed AP to match. As soon as I did this, I lost connection with the AP. I can no longer ping the AP or connect to its web interface. I am able to view the AP when I do a #Show cdp neighbors detail. I can see that it has the correct IP address. But when I do a #show arp, I do not see the AP. When I do a #Show mac address-table, I can see the AP and it's MAC address as well. Does anyone know what I may have done wrong/still need to do in order to get this AP back up and running? I am unable to...
This topic first appeared in the Spiceworks Community

if the printer is shown under print in Airport Utility then select the update button.

Static Web Part

Hi ,
I have a basic doubt which I could not solve despite repeated trial and error . I could not differentiate between static and dynamic web part . By definition, placement of the VWP within a web part zone would classify it as a dynamic one . Only Dynamic Web
parts can be customized and interacted with , using the browser .
But I created a web part page and placed the web part outside the zone , which made it a static WP . But still I am able to customize the title and border .
Am I doing something wrong ?
Thanks,
Grigory

If the intent is to create a new page layout to meet your custom web part zone requirements, then you can create custom page layouts and use those. In the custom layout you can decide the zones you want and you can also embed specific web part if you don't
want them to be edited.
Regards, Mahesh

Web page composer for creating static pages

Hi there,
I have a scenario where I need to develop static pages in Web page composer. That is I dont want to build a complete site but only static pages. And then I want to enable the Approval workflow from KM for these static pages. Can someone throw some light on this how I can acheive?
Regards,
Ponraj M

Ponraj -
Procedure
1. In the Web Page Composer, navigate to the Web page that you want to integrate into the portal navigation.
2. To copy the path to the Web page to the clipboard, choose Copy Path from the context menu for the Web page.
3. Choose Content Administration → Portal Content.
4. Choose New → iView from the context menu of a folder.
5. Choose Portal Component as the source type.
6. Choose the com.sap.nw.wpc.runtime portal archive. On the next screen to appear, choose default.
7. Once you have created the iView, choose the Web Page Composer category in the property editor.
8. In the RID of Compound Document property, enter the path to the KM folder representing the Web page.
Example: /wpccontent/Sites/MyWebSite/Web Pages/MyWebPage
You can paste this path from the clipboard.
9. Open the workset or role that you created when you carried out the initial configuration.
10. To add the iView to the workset or role, choose Add iView to Workset/Role → Deltalink from the context menu of the iView.

Static NAT causes unable to access server via internal IP

Hi all,
Need some help. I running site-to-site IPsec VPN in Cisco 2811 IOS 12.4 both site. Here I encounter a problem to access server on Site A from Site B
Site A having Leased Line connected to router with Public IP. I have done static mapping 1 web server to Public IP (NAT). This to allow external users to access the server via Public IP. At the same time, users at Site B would need to access to same server via Internal IP since they have Site-to-Site VPN established. But once I done Static Mapping (NAT), user at Site B unable to access the server at Site A using its internal IP. But external user can access server via Public IP. What went wrong here. Do i need to add extra command to get this done? We really need this.

Hi sheik,
I'm accessing the server form Site B using its server's LAN IP.
If I remove the static NAT statement from my router at Site A, everything works well. I can access the server from site B using its LAN IP via Site-to-Site VPN. But in this case, external users unable to access server via Public IP since no Static NAT statement.

How do I get Started with Dynamic Web Pages?

I am presently following Janine Warner's Dreamweaver CS3 video series. I noted that the Advanced part of this tutorial series focuses on Dynamic Web Pages, but only uses Cold Fusion. From what I can gather, CF costs around $1000, while PHP is free! My question is really this: in going from static to dynamic web design I'M A COMPLETE NEWBIE, so what do I need? I am doing some planning here -- I know it won't happen overnight.
(BTW: I was surprised to discover that CF is NOT included in my CS3 Master Collection). It might appear then that support for PHP is better than for CF?
Apparently, I need a server -- well, OK I have PCs to spare. Fast internet, I also have: Comcast standard -- 12MP
Now, I think I also need Apache -- which apparently runs on the server and does something.
So then I DL PHP, figure out how it works, and it will integrate with DW CS3 in some way.
Now, what have I missed? Is there some really basic, first-time-with-using-a-server place or tut I should go to or read? Before you ask: No, I'm doing all this myself on a shoestring budget.
Are there expensive hosting fees for dynamic web sites or other items I will run into? Can I just use a PC over my Comcast cable as the server run from my home? (Really high traffic is not anticipated)
All recommendations appreciated, thanks.
Thom

Many of these questions have already been answered in your thread in the Dreamweaver General Discussion forum, so I'll just stick to a few basics.
You need a server whichever server-side technology you choose, but "server" is not a physical machine, but a piece of software that you install on your development computer. You'll find details of how to install a PHP environment in the following article: http://www.adobe.com/devnet/dreamweaver/articles/setting_up_php.html.
Similar instructions are available for setting up a ColdFusion server at http://www.adobe.com/devnet/dreamweaver/articles/setting_up_coldfusion.html. The article is for ColdFusion 8, but ColdFusion 9 is installed in exactly the same way.
Hosting for PHP/MySQL is plentiful and relatively cheap. However, make sure the hosting company offers a minimum of PHP 5.2 and MySQL 5.1. Hosting for CF is harder to find and tends to be a bit more expensive, but not prohibitively so.

Mapping of Web App context root and the physical directory of the web app

I'm running Weblogic 7.0 on Windows2000.The physical directory of my web application
is D:\WL8\weblogic81\TestDeploy\build\TestWebApp and under these directory I have
my JSPS, static HTML and WEB-INF. I define the context path of this web app in
the weblogic.xml ;-
<weblogic-web-app>
<context-root>/testapp</context-root>
</weblogic-web-app>
As a result of deploying this web app in the server (or it may be created manually
also), the following entry gets inserted in the server's config.xml ,-
<Application Deployed="true" Name="TestWebApp"
Path="D:\WL8\weblogic81\TestDeploy\build" TwoPhase="true">
<WebAppComponent Name="TestWebApp" Targets="myserver" URI="TestWebApp"/>
</Application>
Now, whenever I make a request of the form "http://localhost:7001/testapp/..",
it's properly executing my web app. My question is, how does the container knows
that for any request for the web app with context path as 'testapp', it has to
server files from D:\WL8\weblogic81\TestDeploy\build\TestWebApp. In the above
process, nowhere such mapping is specified. I expected something like Tomcat's
server.xml, where in docbase we clearly specify this mapping between the context
path and the physical directory. Please help.

Let me give some more details and hopefully this will make things clearer.
Say you deploy /foo/bar/myweb.war and in myweb.war you configure a
context-root of /rob
During deployment, the server creates an ApplicationMBean with a path of
/foo/bar/. It then creates a WebAppComponent with a uri of myweb.war.
Next, deployment calls back on the web container and tells it to deploy
the WebAppComponent. The web container reads the myweb.war, parses
descriptors etc. The web container then updates its data structures to
register that myweb.war has a context path of /rob. (It has to figure
out all the other servlet mappings as well.)
When a request for /rob/foo comes in, the web container consults its
data structures to determine which webapp and servlet receives the
request. This is not a linear search of all webapps and servlets.
There's much better ways to do pattern matching.
Hope this clears things up. Let me know if you still have questions.
-- Rob
Arindam Chandra wrote:
Thanks for the answer. Still one thing is not clear. Whatever context path I declare
for my web app as the value of <context-root> element in the weblogic.xml (in
my example it's "/testapp"), it is no where mapped with the "URI" attribute (or
any other attribute, sub-element whatsoever in the <Application> element).
Application Deployed="true" Name="TestWebApp"
Path="D:\WL8\weblogic81\TestDeploy\build" TwoPhase="true">
<WebAppComponent Name="TestWebApp" Targets="myserver" URI="TestWebApp"/>
</Application>
So when a request of the form http://myweblogic.com:7001/testapp/... arrives at
the server, how does the server knows that it has to serve this request with files
from D:\WL8\weblogic81\TestDeploy\build\TestWebApp ? It should not be like the
web container iterates thru all the web application entries in config.xml and
tries to match with one context-root declaration. I repeat, I expected some mapping
similar to Tomcat's server.xml, where in the <docbase> element u clearly specify
the mapping between the context path and the physical directory
Rob Woollen <[email protected]> wrote:
Arindam Chandra wrote:
I'm running Weblogic 7.0 on Windows2000.The physical directory of myweb application
is D:\WL8\weblogic81\TestDeploy\build\TestWebApp and under these directoryI have
my JSPS, static HTML and WEB-INF. I define the context path of thisweb app in
the weblogic.xml ;-
<weblogic-web-app>
<context-root>/testapp</context-root>
</weblogic-web-app>
As a result of deploying this web app in the server (or it may be createdmanually
also), the following entry gets inserted in the server's config.xml,-
<>So the server will look for your web application at the Application Path
(D:\WL8\weblogic81\TestDeploy\build|) + the web uri (TestWebApp). So
it
maps the context-root you've specified /testapp to that path.
It's a little clearer in the case where you had a full-fledged EAR.
Then you'r application path would map to the "root" of the EAR, and the
uris would point to the various modules (eg webapps.)
-- Rob
Now, whenever I make a request of the form "http://localhost:7001/testapp/..",
it's properly executing my web app. My question is, how does the containerknows
that for any request for the web app with context path as 'testapp',it has to
server files from D:\WL8\weblogic81\TestDeploy\build\TestWebApp. Inthe above
process, nowhere such mapping is specified. I expected something likeTomcat's
server.xml, where in docbase we clearly specify this mapping betweenthe context
path and the physical directory. Please help.

Add a link from image in web app

I need to add a link to social media site in a static image in a web app detail layout.
I have thought this would be...
<a href="{tag_facebook}"><img alt="" src="/_assets/css/images/social-facebook.png" /></a>
but this displays the link bedside the icon.
I have tried field type "Text string (Hyperlink)" and "Text string (String)".
any help appreciated.
thanks megan

Hey Liam,
Franchise list of stores added to a web app abd each store can have a different link added to the icon.
The icon is hard coded into the layout
The url needs to change for each
e.g. 15 Stores, some have their own Facebook page, some will link to a central Facebook page.
So the icon is static in the web app detail layout, but url changes.
When I add the code
<a href="{tag_facebook}"><img alt="" src="/_assets/css/images/social-facebook.png" />
the result in browser looks like...
thanks Liam

In web dynpro i want explanation/definition for the following things

Hi dudes,
I want explanation *** definition for the following
(1) web dynpro
(2) Cardinality
(3) methods
(4) Nodes
(5) Attributes
(6) Interface
(7) Views
(8) Windows
(9) Mapping
(10)Binding
(11)Model
(12)Controller

Hi,
Here are the defintions for the terms you hav requested-
Web Dynpro Architecture
Definition
Web Dynpro is the SAP NetWeaver programming model for user interfaces (UIs).
The Web Dynpro model is based on the Model View Controller paradigm, and has the
following features that build on the classic dynpro model:
Clear separation of business logic and display logic
Uniform metamodel for all types of user interfaces
Execution on a number of client platforms
Extensive platform independence of interfaces
Web Dynpro provides support for developing Web representation of a business application.
You use specific tools to describe the properties of a Web Dynpro application in the form of
Web Dynpro metadata. The necessary source code is then generated automatically and
executed at runtime. In addition to the events offered by the framework, you can also define
your own events for a Web Dynpro application. However, the event handling must always be
programmed in separate source code areas which are executed automatically when the event
is triggered at runtime.
In Web Dynpro, each user interface is always made up of the same basic elements. These
elements of the metamodel can be statically declared using Web Dynpro tools.
It is also possible to implement elements of the metamodel at runtime and to change them or
reintegrate them at runtime. Using these implementations, you can make any changes or
enhancements to a user interface that has been created by declarative methods by
generating new interface structures at runtime.
This means that you can combine declarative processes and the implementation of source
code.
A Web Dynpro component is a reusable entity. It summarizes all components that are
required as part of this programming unit for an executable Web Dynpro application.
The Web Dynpro component concept offers a number of advantages:
Structuring of the programming
Creation of easily manageable application blocks
Reusability of whole components
Decoupling of software projects in both time and space
The Web Dynpro component contains any number of windows and views and their
corresponding controllers. Additional Web Dynpro components can also be referenced.
View
A view describes the layout and behavior of a rectangular area of a user interface.
Every Web Dynpro application has at least one view. The layout of a view is made up of
different user interface elements, which can be nested in each other. The positioning of
interface elements in one view is supported by the supplied layout variants.
In addition to the visible part, the layout, a view also contains a controller and a context. The
data to which the elements of the view can be bound are stored and managed in the view
context, enabling them to be represented or used on the screen. The view controller can
contain methods for data retrieval or for processing user input.
Window
A window is used to combine several Views and View Sets (the concept of view sets is only
offered in Web Dynpro for Java). A view can only be displayed by the browser if it has been
embedded in a window. A window always contains one or more views, which are connected
by navigation links. One of these views, or a view set, is specified as the start view and is
displayed the first time the window is called.
Windows have inbound and outbound plugs.
Inbound Plugs and Outbound Plugs
A window has one or several inbound or outbound plugs. Using these plugs, a window can be
included into a navigation chain. The concept of these plugs corresponds to the concept of
the plug for a view. Each plug of a window is visible within the entire window and can be used
for navigating within this window. In addition, one or several plugs can be made accessible to
the component interface so that they are visible even beyond the limits of the component in
question. They thus belong to the interface view of the relevant window.
They are used to navogate from one view to other and pass the data between the views. Which view to be called next from current view - the flow of views is descriebd here using Plugs.
Controller
Controllers are the active parts of a Web Dynpro application. They define how the user can
interact with the Web Dynpro application. The data that a controller can access is defined in
the corresponding context. Different instances of controllers and contexts exist within a Web
Dynpro application.
View Controller
Each view has exactly one view controller, which processes the actions performed by the user in the view.
A view also has exactly one view context, which contains the data required for the view.
Interface Controller
Each Web Dynpro component contains exactly one component controller. This controller is a
global controller that is visible also outside the component. It is thus part of the interface of a
Web Dynpro component.
Context
Definition
The data used in the component or in the view are stored in the context. Read-write access to
this data is available using the controllers as a starting point.
Structure
The data from the contexts is managed in a hierarchical structure. Each context has a root
node, underneath which the individual data fields (attributes) are stored in a tree structure.
You create this tree structure according to the structure of your application.
CONTEXT is generally called as a ROOT Node.
Each context has nodes and attributes also.
Cardinatlity
Each node contains data fields that represent one of the following:
u2022
An individual instance of an object type
u2022
A table of instances.
This property of a node is known as its cardinality. The following table summarizes the
possible cardinalities for a node:
Cardinality Description
1:1 The node contains only one element instance, which is instantiated automatically.
0:1 The node contains only one element instance, which must not be instantiated.
1:n The node can contain multiple element instances, of which at least one must always be
instantiated (and is instantiated automatically).
0:n The node can contain multiple element instances, of which none have to be instantiated.
Further information about this and other properties of context nodes is available in the section
Context-Nodes: Properties.
Recursion Nodes
Dynamic node nesting is possible within a context, creating what is called a recursion node.
The node that is used for recursion is always a predecessor of the new node. The newly
created recursion node is a reference to a predecessor node and therefore cannot be
processed separately. Instead it takes on the structure of the node to be repeated.
Data Binding and Mapping
Within the Web Dynpro architecture, the contexts of the different controllers can be linked in
different ways:
u2022
A UI element of the user interface of the view can be linked with an element of the view
context.
u2022
A mapping can be defined between two global controller contexts, or from a view
context to a global controller context.
The context of a global controller can be linked to a Web Dynpro Model.
Defining Mapping Between Two Contexts
The elements of a view context can be locally defined. In this case (represented in the graphic
below as a "Local Node"), all the contained attributes are only visible within the relevant view.
When the view disappears, the attribute values are deleted.
Event
The component controller allows you to create events.
Events are used to communicate between controllers and enable one controller to trigger
event handlers in a different controller.
Cross-component communication can be implemented using the interface controlleru2019s events.
Events that were created in the component controller are visible within the component only.
Inbound Plugs
Inbound plugs in a view also react like an event. Therefore, when a view is called using an
inbound plug, the event handler that is optionally available for the inbound plug is always
called first. In this case event handling takes place within the current view controller.
UI Element Events
Some UI elements, such as the Button element have special events that are linked with user
actions. These events are predefined and have to be linked with an action at design time.
Actions for UI Element Events
Some UI elements such as the button element can react to a useru2019s interaction: clicking on
the corresponding pushbutton can trigger a handling method to be called within the view
controller. Such UI elements are equipped with one or several general events, which can be
linked with a specific action at design time (switching to a subsequent view, for example). If
such an action is created, an event handler method for this action is created automatically. In
this way, you can equip a UI element event (which has been inserted several times into a
view) with different actions as necessary. The event is then processed by the corresponding
event handler depending on the action that is linked.
Interfaces of Web Dynpro Components
Each component has an interface in order to enable communication between Web Dynpro
components and to enable a component to be called up by a user. This interface consists of
two parts:
Interface View of a Window Contained in a Component
The interface view of a Web Dynpro window is used to link a window with a Web Dynpro
application that can be called by the user.
Reward if helpful.
Best Wishes,
Chandralekha

Want docs for Web Dynpro ABAP

Hi All ,
Can anyone please send me the Docs or link for Web Dynpro ABAP .
Thanks in advance
Rahul

Hi,
Web Dynpro ABAP
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/db22242d-0701-0010-28a2-aeaa1fefd706
Also, I have the official Web Dynpro for ABAP documentation. Please let me know if I should send it to you.
Hope that the following also helps you.
Web Dynpro for ABAP (WD4A, WDA) is the SAP standard UI technology for developing Web
applications in the ABAP environment. It consists of a runtime environment and a graphical
development environment with special Web Dynpro tools that are integrated in the ABAP
Workbench (SE80).
Web Dynpro offers the following advantages for application developers:
? The use of declarative and graphical tools significantly reduces the implementation
effort
? Web Dynpro supports a structured design process
? Strict separation between layout and business data
? Reuse and better maintainability by using components
? The layout and navigation is easily changed using the Web Dynpro tools
? Stateful applications are supported that is, if the page is changed and the required
data remains intact so that you can access it at any time throughout the entire
application context.
Note that stateless applications are not possible.
? Automatic data transport using data binding
? Automatic input check
? Automatic operation of the Web Dynpro application using the keyboard
? User interface accessibility is supported
? Full integration in the reliable ABAP development environment
Web Dynpro Architecture
Definition
Web Dynpro is the SAP NetWeaver programming model for user interfaces (UIs).
The Web Dynpro model is based on the Model View Controller paradigm, and has the
following features that build on the classic dynpro model:
? Clear separation of business logic and display logic
? Uniform metamodel for all types of user interfaces
? Execution on a number of client platforms.
? Extensive platform independence of interfaces
Structure
Metamodel Concept
Web Dynpro provides support for developing Web representation of a business application.
You use specific tools to describe the properties of a Web Dynpro application in the form of
Web Dynpro metadata. The necessary source code is then generated automatically and
executed at runtime. In addition to the events offered by the framework, you can also define
your own events for a Web Dynpro application. However, the event handling must always be
programmed in separate source code areas which are executed automatically when the event
is triggered at runtime.
In Web Dynpro, each user interface is always made up of the same basic elements. These
elements of the metamodel can be statically declared using Web Dynpro tools.
It is also possible to implement elements of the metamodel at runtime and to change them or
reintegrate them at runtime. Using these implementations, you can make any changes or
enhancements to a user interface that has been created by declarative methods by
generating new interface structures at runtime.
This means that you can combine declarative processes and the implementation of source
code.
Graphical Development Tools
To support this declarative concept, both the SAP NetWeaver Developer Studio and the
ABAP Workbench contain a range of Web Dynpro tools. You can therefore generate a large
proportion of a Web Dynpro application using the tools provided, without having to create your
own source code. This applies to the following parts of the application:
? Data flow between the front end and back end
? Layout of the user interface
? Properties of user interface elements
The Web Dynpro tools enable you to create source text areas manually within generated
source texts. These areas are not changed if the source code is regenerated.
Separation of Business and Application Logic
Using Web Dynpro enables a clear separation of business logic and display logic. A Web
Dynpro application runs on the front end and has local or remote access to the back end
system via a service. This means that the display logic is contained in the Web Dynpro
application, while the business logic and the persistence of the business objects run in the
back end system. The following options are currently available for connecting Web Dynpro
applications and the back-end system:
? An interface generated using adaptive RFC, through which BAPIs of an SAP system
can be called
? An interface for calling Web services
? A self-generated interface
The source code required for connecting the Web Dynpro application can be generated
from a UML definition of the Web Dynpro interface. A UML definition can be imported
into the Web Dynpro tools as an XML file.
Conversion of the Model-View-Controller
Conversion of the Model-View-Controller Programming Model
Every Web Dynpro application is structured according to the Model View Controller
programming model:
? The model forms the interface to the back end system and thus enables the
Web Dynpro application access to data.
? The view is responsible for the representation of the data in the browser.
? The controller lies between the view and the model. The controller formats
the model data to be displayed in the view, processes the user entries made by the
user, and returns them to the model.
/people/thomas.jung/blog/2006/06/20/web-dynpro-abap-demonstration-videos
http://help.sap.com/saphelp_nw04s/helpdata/en/77/3545415ea6f523e10000000a155106/frameset.htm
Reward points if useful
Regards
Anji

Database ranking

Gentlemen,
the most recent BO documentation mentions the feature "database ranking" and lists some relational database management systems supporting this feature. I want to avoid ranking the WebI report itself but have the database do this job.
Is database ranking also possible when working with SAP BW based OLAP universes (sitting on BEx Queries) in BO XI 3.1 SP2?
Thank you.
Regards
Johannes

Hi,
Unfortunately its is not posssible to do a ranking on the Web Intelligence query panel usin SAP BW OLAP Universes: this should normally be addressed in Aurora.
By the way there are 2 alternatives:
<li>Use Data Federator for accessing SAP BW in relational mode and take advantage of relational ranking features
<li>Use OLAP universe and defined a calauclated measures that rank the members of a given characteristic/hierarchy for a given key figures then define a predefined filter to filter the calculated expression in order to have the Top N or the Bottom N.
Here is a sample that rank Company Code over Open order quantity
<EXPRESSION>Rank([0D_CO_CODE].CurrentMember, Order( [0D_CO_CODE].CurrentMember.Level.Members ,
@Select(Open order quantity in base unit (SAP DEMO)\Open order quantity in base unit (SAP DEMO)))</EXPRESSION>
Now here is the same example used in a predefined filter:
<FILTER EXPRESSION="Rank([0D_CO_CODE].CurrentMember, Order( [0D_CO_CODE].CurrentMember.Level.Members ,
@Select(Open order quantity in base unit (SAP DEMO)\Open order quantity in base unit (SAP DEMO)))"><CONDITION OPERATORCONDITION="GreaterOrEqual">
<CONSTANT CAPTION="Value"></CONSTANT>@Prompt('Enter value for Top n','N',,mono,free)</CONDITION></FILTER>
Regards,
Didier

Approval process in Web page composer

Hi there,
We are building static pages using web page composer and trying to implement the KM approval process for those static pages. Now my questions are:
1. What should be the value I need to give for the folders for service permissions (Layout, collaboration,Full control etc...) for anonymous users
2. What should be the value I need to give for the folders for service permissions (Layout, collaboration,Full control etc...) for users with approval authorities
Your help is highly appreciated
Regards,
Ponraj M

Hi,
The approval process has nothing to do with the service permissions. It's regular permissions you should be concerned about, for example: If a user is a permissions owner of a folder then he will be able to skip the approval process or If a user has only read permissions then he will be able to view only approved documents.
Best regards,
Avishai Zamir

Ranges to be fixed in web template charts

Dear friends,
I need a help in Web reporting.
While we run the web reports the scale in the chart cant be fixed as because of the values in the report.
I need the have a fixed scale for all the values.
How to make the scales static in the web template charts?
Could some one throw some lights on this?
Thanks in advance
Thanks
Sri

Hi Sri,
do you mean the scale of the axis? In the WAD choose Edit Chart and go to the corresponding axis. There you can set the minimum and maximum calculation to User Defined and specify your own value.
Best regards
Matthias

Web Dynpro concept

Hi all,
What is web dynpro concept in ABAP. What are the future scope for the same.
Regards,
John

Hi,
Web Dynpro ABAP
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/db22242d-0701-0010-28a2-aeaa1fefd706
Hope that the following also helps you.
Web Dynpro for ABAP (WD4A, WDA) is the SAP standard UI technology for developing Web
applications in the ABAP environment. It consists of a runtime environment and a graphical
development environment with special Web Dynpro tools that are integrated in the ABAP
Workbench (SE80).
Web Dynpro offers the following advantages for application developers:
The use of declarative and graphical tools significantly reduces the implementation
effort
Web Dynpro supports a structured design process
Strict separation between layout and business data
Reuse and better maintainability by using components
The layout and navigation is easily changed using the Web Dynpro tools
Stateful applications are supported u2013 that is, if the page is changed and the required
data remains intact so that you can access it at any time throughout the entire
application context.
Note that stateless applications are not possible.
Automatic data transport using data binding
Automatic input check
Automatic operation of the Web Dynpro application using the keyboard
User interface accessibility is supported
Full integration in the reliable ABAP development environment
Web Dynpro Architecture
Definition
Web Dynpro is the SAP NetWeaver programming model for user interfaces (UIs).
The Web Dynpro model is based on the Model View Controller paradigm, and has the
following features that build on the classic dynpro model:
Clear separation of business logic and display logic
Uniform metamodel for all types of user interfaces
Execution on a number of client platforms.
Extensive platform independence of interfaces
Structure
Metamodel Concept
Web Dynpro provides support for developing Web representation of a business application.
You use specific tools to describe the properties of a Web Dynpro application in the form of
Web Dynpro metadata. The necessary source code is then generated automatically and
executed at runtime. In addition to the events offered by the framework, you can also define
your own events for a Web Dynpro application. However, the event handling must always be
programmed in separate source code areas which are executed automatically when the event
is triggered at runtime.
In Web Dynpro, each user interface is always made up of the same basic elements. These
elements of the metamodel can be statically declared using Web Dynpro tools.
It is also possible to implement elements of the metamodel at runtime and to change them or
reintegrate them at runtime. Using these implementations, you can make any changes or
enhancements to a user interface that has been created by declarative methods by
generating new interface structures at runtime.
This means that you can combine declarative processes and the implementation of source
code.
Graphical Development Tools
To support this declarative concept, both the SAP NetWeaver Developer Studio and the
ABAP Workbench contain a range of Web Dynpro tools. You can therefore generate a large
proportion of a Web Dynpro application using the tools provided, without having to create your
own source code. This applies to the following parts of the application:
Data flow between the front end and back end
Layout of the user interface
Properties of user interface elements
The Web Dynpro tools enable you to create source text areas manually within generated
source texts. These areas are not changed if the source code is regenerated.
Separation of Business and Application Logic
Using Web Dynpro enables a clear separation of business logic and display logic. A Web
Dynpro application runs on the front end and has local or remote access to the back end
system via a service. This means that the display logic is contained in the Web Dynpro
application, while the business logic and the persistence of the business objects run in the
back end system. The following options are currently available for connecting Web Dynpro
applications and the back-end system:
An interface generated using adaptive RFC, through which BAPIs of an SAP system
can be called
An interface for calling Web services
A self-generated interface
The source code required for connecting the Web Dynpro application can be generated
from a UML definition of the Web Dynpro interface. A UML definition can be imported
into the Web Dynpro tools as an XML file.
Conversion of the Model-View-Controller
Conversion of the Model-View-Controller Programming Model
Every Web Dynpro application is structured according to the Model View Controller
programming model:
The model forms the interface to the back end system and thus enables the
Web Dynpro application access to data.
The view is responsible for the representation of the data in the browser.
The controller lies between the view and the model. The controller formats
the model data to be displayed in the view, processes the user entries made by the
user, and returns them to the model.
Web Dynpro ABAP Demonstration Videos
http://help.sap.com/saphelp_nw04s/helpdata/en/77/3545415ea6f523e10000000a155106/frameset.htm
Cheers,
vasavi.v

Static Ranking in WebI 4.1

Similar Messages

Maybe you are looking for