1 5 6 7 8 9 40 Previous Next

SAP Enterprise Portal

597 Posts
Tuvia Kahana

Theming Support Blog

Posted by Tuvia Kahana Dec 31, 2015

Hello


My name is Tuvia Kahana, and I am part of the Portal development support group.

In this blog we aim is to make your life easier, and to share with you important information about theming (EP-PIN-TOL component) new features and common fixes.


You are also, more than welcome to share your tips and concerns.


Hopefully you will find answers to your concerns here, and it will spare you the need of creating incidents.

 

Let’s start:


Some interesting notes that we released lately:


- When your custom theme does not appear in all your server nodes, or the theme sometimes applied and sometimes not, you can implement the below note:

2197656 - Custom themes does not exist in all server nodes

If you do not have the above note relevant SP, follow the workaround instructions in  the below KBA

 

 

2195099 -  Portal theme is inconsistent after upgrade

 

- When a theme that you created does not apply on your application(in your content area) as expected, and instead you see the backend’s theme, you need to apply the below note:

1446099   Application (Web Dynpro or ITS) is not displayed in customer theme

 

In addition ,you can see below interesting short movies related to theming:


How to set a parameter that is not exposed in the Theme Editor:

https://www.youtube.com/watch?v=xLkKzBdSHgQ&feature=youtu.be

It is also explained in the following note :1752515 - Updating Customer Theme Parameters Not Exposed in the Theme Editor.


How to create an RTL supported theme in the Portal:

https://www.youtube.com/watch?v=6axlHhGyolU&feature=youtu.be


Changing Portal theming from legacy structure to LESS structure:

https://www.youtube.com/watch?v=6KXh0RaFCDA&feature=youtu.be

You can create a new role by uploading it from a back-end ABAP system.

You use the New Role from Back End wizard to search for the role in the selected back-end system,

and then upload the role with its contents directly into the Portal Catalog, in the folder from which you initiated the upload.

Prerequisites for Role Upload

Motivation

Setting up SAP Enterprise Portal (EP) as an access point to Fiori Launchpad (FLP) allows combining capabilities such as EP roles, content management and integration capabilities with the new FLP UX world, and significantly simplifies the integration efforts on the client side.In this blog we will describe, on high level, the corresponding integration architecture.


FLP on EP simple landscape

FLP on EP can run using only portal resources and providing FLP look and feel with full FLP functionality using Portal Fiori Framework Page (FFP).

FFP components include a bootstrap html document, functional Fiori and UI5 resources and content.

The landscape for this scenario looks like this:

 

 

 

SimpleLandscape_.png



FLP on EP with remote content consumption from ABAP FES

An Enterprise Portal integrated with SAP Fiori scenario will require a more sophisticated landscape, where the client will get the resources from EP, Fiori Front-end Server (FES) and Gateway, with a single web url.

For FES, Gateway and Portal systems the ‘System’ objects should be configured in Web Dispatcher profile.

 

Distributing requests via SAP Web Dispatcher

To enable this scenario a reverse proxy concept must be implemented in the landscape. It is done with SAP Web Dispatcher.

Additionally, FLP requires SSL configuration throughout the entire landscape.

The content requests are distributed on the Web Dispatcher using redirection rules per ‘System’ object. These rules together define the landscape.

RemoteLandscape_.png


The configuration looks like an “non-portal” FLP landscape with an exception of a Portal added as the last rule.

So, Portal/FES integration configuration will have as minimum:

  • FES system
  • Portal system.

If other systems are included in the landscape (e.g. HANA system), they should be represented in the configuration as well.

 

Required steps:

  1. Configure FLP landscape, following the configuration guidelines Configuring SAP Web Dispatcher for FLP on ABAP.
  2. In the profile file add a configuration line for the Portal:

wdisp/system_# = SID=<EP SID>, MSHOST=<EP MSHOST>, MSPORT=<EP MSPORT>, SRCSRV=*:<WDISP PORT>, SRCURL=/irj;/

(See also: Configuring SAP Web Dispatcher for FLP on Portal )

Please note:

    • This line should be the last one in the configuration list
    • It should contain the redirection ‘/’, meaning that all un-matching requests will be redirected to the Portal.

 

Things to consider

  • SAP Fiori Launchpad  and Enterprise Portal integration supports various configurations, such as landscape components sharing (for example, for Dev & QA landscapes). For this you can configure different virtual hosts/ports on the same reverse proxy.

Please note:

    • There should not be any hard-coded network attributes
    • The request’s “host” header should not change along the flow in reverse proxy configuration.

 


More Info

SAP Help library links:

 

SCN Blogs:

 

Related Notes:


If you use Remote Role Assignment (RRA) in a federated portal network (FPN), and have encountered some performance or availability issues on the consumer portal whenever the producer portal is down, the following information is relevant for you.

 

When using Federated Portal Network in the SAP Enterprise Portal, one of the considerations that need to be addressed is the availability of the producer portal.

 

The following is a quote from SAP Note 880482 – “FPN: Federated Portal Network Central Note”:

Performance regression on FPN consumer portal when producer portal is not available:

An SAP NetWeaver [enterprise portal] consumer can become unresponsive when any of its registered producer portals are either unavailable or not responsive. When planning to shut down or restart a portal that functions as a producer for any other consumer portal, you must first block the connection to the producer portal from its respective consumer portals using the FPN administration UIs.

 

It is expected that the producer portal is up and running at all times, because unexpected downtime or lack of proper planning from the FPN perspective can damage the consumer portal functionality.

 

To overcome these issues, there are several options, described below.



Planned Producer Portal downtime

 

In case of a planned downtime of the producer portal, it is recommended to block access to the producer in advance. It can be done easily using the UI under System Administration -> Federated Portal.

 

For SAP Enterprise Portal 7.3 and above, under “Manage My FPN Connections”, you can prevent/allow access to connections (as consumer or as producer):

1.jpg

 

In addition, for newly-created FPN connections, you can control access to and from your system via the “Connection Options” tab under the Control Panel.

2.jpg

You can read more about it in the following documentation:

 

Enabling/Disabling Remote Access in FPN Connections - Implementing a Federated Portal Network - SAP Library

 

If you haven’t upgraded yet to 7.3 or above and still using the legacy SAP Enterprise Portal 7.0 versions, you can control the access to the Producer portals under “View My Producers”:

3.jpg

 

Take into consideration the following facts:

  • When a producer blocks access from a consumer, the block is applied only after the dedicated cache on the consumer is cleaned.
  • When a consumer blocks access to a producer, the block is applied to the current users only after a new browser session is opened by them on the consumer portal.

 

It is highly recommended to upgrade to a newer version, such as 7.4 / 7.5.
Refer to Everything you wanted to know about SAP Enterprise Portal Upgrade

 


Unplanned Producer Portal downtime

 

For cases where the producer portal is not available unexpectedly, new configurations have been added in enterprise Portal 7.3 and above. These configurations were added in order to slightly improve the performance of the consumer portal when the producer portal is down.
If your consumer portal is one of those versions, then this option is relevant for you.

 

To check for the relevant SPs where it was added, refer to SAP Note 1718291 – “Consumer Portal availability when producer Portal is down”.

 

With this new configuration, you can control the timeout interval of SOAP calls to the producer portal. Once such a timeout occurs, the mechanism blocks that producer portal. You can also configure the length of time this producer will be blocked.

 

In addition, there are two approaches in case such a call gets a timeout after the defined interval – blocking for all users, and blocking only the users who encounter the issue.

 

Following is the information quoted from the note:

First, decrease the timeout value for the remote call (The default is 3 minutes):
Go to NWA on the consumer portal:
Configuration -> Infrastructure -> Application Modules.
Look for 'com.sap.portal.ivs.global.bridge' and in the 'web module details' select 'SenderBridge'.
Set the 'SOAPCallTimeout' parameter for a desired time. The recommended value is 30 seconds. The value for this parameter is in milliseconds so for 30 seconds you should put 30000.
Save the changes and restart the service/application in order to apply the changes.

4.jpg
Secondly, in the 'web module details' select 'SecuritySessionManager'.
This service has a parameter which determines the behavior of the consumer in this case.
There are 2 approaches for solutions from which you can choose:

Approach 1 - blocking for all users:
If you would like to prevent every user from suffering the long login time process, due to a producer down time, you should configure the 'blockAllUsersOnError' parameter to 'all'.
In this case, whenever the first user encounters a timeout event for the remote call, all other users who will log in in the future will not trigger a remote call and the login process will be normal.
The administrator can unblock the problematic producer portal by navigating to the Federated Portal Iview, -> System Administration -> select the connection with this producer portal -> connection -> allow access to remote content.
In addition, the parameter 'BlockingInterval' of the 'SecuritySessionManager' service, determines for how long this producer will be blocked.
*** This configuration is recommended when there is a problem with the producer portal and it is crashing and not running. [It should be set before the crash ]

Approach 2 - blocking only user who encounters the issue:
Set the 'blockAllUsersOnError' parameter to 'user' and save.
This configuration will prevent the current user's session from triggering a remote call to the producer that caused the timeout and it will remain blocked until the user logs out of the consumer portal and logs in again.
5.jpg
After you set the parameters, click on 'More Actions' -> View Corresponding to Application.
Stop and Start both services 'SecuritySessionManager' and 'SenderBridge' on all instances.

 


Overcoming consumer unavailability

 

In a case where the consumer portal is not available at all, it might be that all threads are taken by the SOAP calls. The available steps:

  1. If possible, start the producer Portal, in order to prevent from such cases in the future.
  2. Disconnect one instance from the Web Dispatcher / Load Balancer, so that end users will not be able to reach it. This operation will ensure that no new problematic threads are generated.
  3. Restart the instance in order to release all threads, and make the portal of this instance available again.
  4. Log in to that instance with an administrator that has no remote roles assigned, and configure the relevant properties from SAP note 1718291. In addition, if the producer is still not available, block the producer portal, as described under Planned Producer Portal downtime section.
  5. Restart the instance and connect it back to the Web Dispatcher / Load Balancer.
  6. Restart the rest of the instances to release all other threads.

This blog is for portal end-users and content administrators who would like to learn about the new features developed in the latest Enterprise Portal SP for FLP@EP, their added value, and the required configuration.


These features include the following functionality from NW7.40 SP12 Java stack blog:

  • Configurable SAP Fiori Borders for iViews/pages  (header and footer bars) with Back button, Related links, dynamic navigation and Save as Tile button
  • Enhanced Fiori Framework Page (FFP) configuration for Home Page personalization
  • Hide/show groups action in Option Menu
  • Search configuration in Tile Catalog and Home page
  • FFP extensions: enabling custom plugin to load on SAP Fiori Launchpad opening
  • Embedding SAPUI5 apps

and new features such as:

  • Configurable iView/Page width
  • EP Tile dimension 1X2 (Please refer to SAP Note 2321074 - EP Tile Sizes 2x1 and 2x2 are not Supported
  • FFP personalization enhancements:
    • Enabling Settings as tile action for editing of EP tile properties in the Home page
    • Enabling Filtering by Tags in Tile Catalog
    • Enabling Alphabetical sorting of tiles within a category
    • Enabling Remove of duplicate tiles
  • FFP extension points
  • Window feature property for iView/Page, relevant when the navigation target is in a new window.


Prerequisites:

  1. SAP Web Dispatcher or any other reverse proxy,which is responsible to dispatch the requests between the ABAP FES and Java server (EP). 
  2. Minimum required SP for ABAP FES server is SAPP_UI750 SP01 component. For additional information please refer to SAP note 2031108.



1 Configurable iView/Page Width

The Open in Full Width property specifies whether an iView or page opens in the full width of the screen area or in a narrower width. Administrators can check-in the property:


FullWidthProperty.JPG


And in run-time the layout will look as following:


WDR_UITest.JPG


If the property Open in Full Width is not checked, the page looks like this:


notFullWidth.JPG


2 Tile Personalization

If FFP personalization is enabled by administrators and Enable 'Settings' as Tile Action option is checked-in, end-users can change the tiles properties, such as name, subtitle and info text in run-time (the tiles should be representing an iView or page):


TileSizeConfig.JPG


In the Settings pop-up an end-user can change the tile title, subtitle and info properties value, and immediately get a preview of the changes:


TileSettingsAction.JPG


3 Alphabetical Sorting of Tiles

This FFP configuration option determines whether tiles are sorted alphabetically by title within a category.


AlphSortingTilesConfig.JPG

 

4 Remove Duplicate Tiles from Remote Content

This FFP configuration option determines whether only a single tile appears within a category when multiple tiles from remote content exist with identical title, subtitle, and intent.


DuplicateTilesConfig.JPG


5 EP Tile Dimensions

Using the Tile Size property for iViews and pages, administrators can specify the dimensions of the tile (1X1, 2X1, 1X2, 2X2) representing an iView or page in the home page and tile catalog. For example:


TileSizeConfig.JPG


All possible variants look like this:


TileSizeRT.JPG


6 Filtering by Tags in Tile Catalog

Using FFP configuration option administrators control whether end-users can filter by related terms in the tile catalog:


TagConfig.JPG


The terms are maintained in the Tags property for iViews/pages:


Tag.JPG


FilterByTagRunTime.JPG

7 Window feature property for iView/Page

Window feature property for iView/Page specifies the appearance of a new window. This property can contain the list of JavaScript parameters, for example” fullscreen=yes; toolbar=yes;…”. If the property is empty, a new window is opened according to default browser parameters.

This property was also downported to the lower Java stack releases, such as NW7.31 SP16,17 and NE7.40 SP12.


8 Fiori Framework Page Extension Points

FFP extension points allow performing actions on FLP events, for example an action on tiles in catalog or home page before rendering.

The customers can extend the standard FLP functionality, with, for example, an additional action in Option menu, a custom action in a footer, etc.

These extensions can be used inside a custom bootstrap plugin in FFP (details). 

 

9 Web IDE Integration

A plugin for SAP Web IDE enables a Web IDE app deployment to Enterprise Portal.

 

Prerequisites:

  • A user has been subscribed to SAP Web IDE
  • The required destination to the SAP Web IDE system is configured in SAP HANA Cloud Platform (details).

 

 

To learn more:


  • Web IDE deployment video



Welcome to the Q4 edition of the SAP Portal news blog. The news blog contains information on classical Portal on-premise topics as well as on Cloud experience products as SAP Fiori Cloud Edition. Have fun!


We have news for you in the following topic areas:

  • SAP Fiori Cloud Edition - controlled availability for customers
  • SAP Fiori Overview Page - a new SAP Fiori experience
  • New release of SAP HANA Cloud Portal
  • News on SAP Enterprise Portal
  • HANA Cloud Portal Developer Challenge - Contributions
  • Blogs from the community

 

 

SAP Fiori Cloud Edition

 

SAP Fiori, cloud edition is available for customers as part of a controlled availability program for few weeks already. At SAP TechEd in Barcelona we have announced the availability of SAP Fiori, cloud edition to the market via a press-release. For more information see also the announcement blog. If you would like to experience how SAP is running SAP Fiori Cloud Edition, just navigate to: http://fiorilaunchpad.sap.com.

 

Watch also this movie showing how SAP IT is running SAP Fiori Cloud Edition:

 



SAP Fiori Overview Page (OVP) - a new interaction within SAP Fiori UX

 

The SAP Fiori Overview Page (OVP) enables business users perform their daily tasks quickly and effectively by having all the information they need on a single page. Information is visualized on cards for multiple types of content in an attractive and efficient way. SAP Fiori OVP first release, which is part of SAPUI5 1.32, is available for both to on-premise systems and on HANA Cloud Platform. For more information, visit SAP Fiori Overview Page.

 

Watch this demo movie on OVP:

 

 

 

New Release of SAP HANA Cloud Portal

 

At SAP TechEd in Las Vegas we announced the upcoming 1511 major release of SAP HANA Cloud Portal. The new release is a completely redesigned and improved version of SAP HANA Cloud Portal that brings major changes in the product architecture to embrace Fiori technology and concepts (SAP UI5, SAP WebIDE, oDATA etc.), tighter integration with SAP Web IDE for advanced developer flows and new out of the box templates and business solutions.

 

 

SAP Enterprise Portal News

 

New Support Package Stacks for Enterprise Portal on SAP NetWeaver 7.4


To get an overview on the Portal features of SAP NetWeaver 7.4 SPS11/SPS13 (Java stack SP12), have a look at this presentation.


For more (technical) details, check out the following material:


  • SAP NetWeaver 7.4 SPS11:
  • SAP NetWeaver 7.4 SPS13 (Java stack SP12):
    • read this blog outlining the features in detail (for example integration of analytical apps, search for factsheets, enhanced personalization etc.)

 

Watch this movie focusing on the end user features (based on SPS13):

 


 

Enterprise Portal on NetWeaver 7.5

SAP NetWeaver 7.5 is the compatible follow-up release of SAP NetWeaver 7.4 and the on-premise foundation for SAP Business Suite (as of Enhancement Package 8 for SAP ERP) and for the on-premise edition of SAP S/4 HANA. For more information, have a look at the SAP NetWeaver 7.5 landing page. Have also a look at this blog and learn about the (planned) highlights of Enterprise Portal running on NetWeaver 7.5.

 

For more detailed information, check out the release notes. The features of Support Package Stack 01 also contain a plugin for SAP Web IDE, which enables you to deploy any Web IDE app to the Portal and run it with the Ajax framework page and on Fiori launchpad. Watch this movie to get an insight into this new capability:

 

 

 

Developer Challenge: Contributions


The HANA Cloud Portal developer challenge 2015 ended on November 30, 2015. The challenge gave people the chance to demonstrate their developer excellence and leverage the capabilities of the trial developer environment of HANA Cloud Platform and HANA Cloud Portal.

We received the following great contributions and we want to thank all people and teams for their engagement and feedback:



All participants already received a participation award of developer excellence. All contributions will be reviewed by our Cloud Portal experts from our team. This expert committee will also define the finalists and the winner who will receive additional awards. The final results will be published beginning of January.



Blogs from the Community


Blogs, which are recommended to read:



and watch the video blog How to run the PCD check tool.


Subscribe to our Newsletter!

To get regular information on SAP Portal and our Cloud solution offerings, you can also subscribe to our newsletter.



The error "Could not open iView. The iView is not compatible with your browser, operating system, or device. Contact your system administrator for more information." will appear if you try to access the portal or open certain content using an unsupported browser or device. There are a number of scenarios where this error can be thrown and I will discuss each of them.

 

 

browser not supported error.PNG

 

  • Error appearing only at login

 

If if is then you need to check the following:

 

 

1) Check if note 1666862 - 'Allow other browsers to access the portal' is applicable for your version, if so please ensure that the fix is applied

 

2) Are you using a custom login component? If so you will need to update the useragent string in the portalapp.xml file as described in  kba 1646680 - 'Cannot access Enterprise Portal with Apple Safari browser'

 

3) Is the browser you are trying to access with actually supported for your version? You can check the browser support section of the Product Availability Matrix (PAM) at Product Availability Matrix | SAP Support Portal

 

4) Is this happening on a certain OS or device? Again you need to ensure that they are supported for your portal version and check PAM. Also note 1995454 - 'Central Portal Browser Support for Portal Mobile & Desktop' provides a list of OS and devices which support portal access

 

 

  • Error appearing when accessing certain content only

 

1) If the error is not thrown at login and happens only when navigating to a certain iview

 

Open the problematic iView and check "Supported User Agents" property - it should be set like this:

(MSIE, >=5.5, *) (Netscape, *, *) (Mozilla,*,*) (Safari,>=3.1, *) (Chrome,*,*)

 

 

2) Also check the Core iView under Content Administration -> Content Provided by SAP -> Core objects -> Core iView and ensure the property "Supported User Agents" is set to

(MSIE, >=5.5, *) (Netscape, *, *) (Mozilla,*,*) (Safari,>=3.1, *) (Chrome,*,*)

 

 

  • Error appearing when using IE 11 only

 

Check note 1972506 - 'Cannot access portal with IE11 or Framework page not loaded correctly'

 

 

  • Error appearing when using Microsoft Edge browser only

 

Check note 2226409 - Can't access Portal logon screen on Microsoft Edge browser

Background: In the Universal Worklist (UWL) in the configuration setup you are encountering an error exception referencing the ActionInboxConnector.

 

What you see: The UWL iView displays the error exception "failure in retrieving from ActionInboxConnector" 

 

Logs: In the defaultTrace log file (\usr\sap\<SID>\<J2EE_instance_number>\j2ee\cluster\<server#>\log\) you see an exception related to ActionInboxConnector with its associated connector status e.g.

 

#EP-KM-CM#sap.com/com.sap.netweaver.bc.uwl.aibconnector#C00090048127005A0000003400007A79#443247250000005400

#sap.com/com.sap.netweaver.bc.uwl#com.sap.netweaver.bc.uwl.core.connect.aib.ActionInboxConnector#PELLIPE01#0##EB7695EE741711E5BF6E005056141073#52016186741811e5cb6200001a6b6a92##0#Thread[UWL Pooled Thread:4,5,ApplicationThreadGroup]#Plain## while trying to invoke the method com.sap.netweaver.bc.uwl.core.connect.aib.AIBUtils.itemType2Categories(java.lang.String, com.sap.netweaver.bc.uwl.UWLContext) of a null object loaded from field com.sap.netweaver.bc.uwl.core.connect.aib.ActionInboxConnector.aibUtils of an object loaded from local variable 'this'java.lang.NullPointerException: while trying to invoke the method com.sap.netweaver.bc.uwl.core.connect.aib.AIBUtils.itemType2Categories(java.lang.String, com.sap.netweaver.bc.uwl.UWLContext) of a null object loaded from field com.sap.netweaver.bc.uwl.core.connect.aib.ActionInboxConnector.aibUtils of an object loaded from local variable 'this'.

 

FailureIn.PNG

 

Identifying the issue: Log into Enterprise Portal.  In the portal, navigate to System Administration -> System Configuration -> Universal Worklist & Workflow -> Universal Worklist -> Administration. In the list of systems, select the ActionInboxConnector. The UWL in the Enterprise Portal shows the message  "An error occurred while trying to connect to the provider". While the connector status returns "failure in retrieving from ActionInboxConnector".


Why this is happening: Discrepancy in the attributes associated with the ActionInboxConnector.


Resolving the issue: With the ActionInboxConnector errors exceptions may appear for a wide range of different reasons.


The first point of analysis is to check if you are currently using KM or KMC (pcd:portal_content/com.sap.pct/admin.templates/iviews/com/sap.km.Config). If you are using KMC attempt to deactivate -> then reactivate the ActionInbox Connector > System Administration -> System Configuration -> UWL -> UWL Admin;

 

Important Point: Computer Monitor Service Under KM must be working. Next navigate to the UWL administration -> select the system 'ActionInbox' -> open the tray for 'Universal Worklist Service Configuration'. Analyze the current value setting for 'Timeout Value for the Connected Systems'. Increase the value presently configured to a new value setting e.g. 300 seconds.Then retest the connector.



Background: In the Universal Worklist (UWL) after you perform an action (Approve/Reject) on a workitem the action window remains open instead of closing automatically.

 

Expected Behavior:The expected behaviour is that the window closes without any required action instead however you encounter the "Close Window" screen option.

 

UWLCloseWindow.PNG

 

Identifying the issue: Log into Enterprise Portal. In the portal, navigate to System Administration -> System Configuration -> Universal Worklist & Workflow -> Universal Worklist. Launch the main UWL iView and select a workitem of choice. Perform any definite action on the workitem e.g. approval or rejection and the popup window remains open.

 

Why this is happening: Discrepancy in the property view settings. The Notification/UWL item launches the work item by calling transaction SWNWIEX (Report RSWNWIEX) from a backend system and passes the work item ID. This transaction starts the work item execution by triggering the method of the object, which is defined in the single step task. The transaction SWNWIEX is not aware of the functionality implemented in the method of the object.

 

Resolution:  Log into Enterprise Portal.  Navigate to the Universal Worklist (UWL) -> select UWL Administration. Open the UWL Standard XML (uwl.standard). In order for the window to be closed automatically as desired the returnToDetailViewAllowed property needs to be maintained in the UWL standard XML setup. Add the correct property to the uwl.standard XML -> returnToDetailViewAllowed="yes". Re-upload the XML with a value of "High" and clear the UWL Cache.

Background: You can use the UserDecisionHandler to handle execution of items of typesUserDecision.The UWL is shipped with the UserDecisionHandler for the WebFlowConnector.Their execution is handled through function modules SAP_WAPI_DECISION_COMPLETE or SAP_DECISION_COMPLETE.

.

Issue: From the UWL, a task that requires a user decision such as Approve or Reject along with a reason for this action via the UserDecisionNote is failing.


Exception: The system responds with the message "Grounds for refusal - required information failed".


KBAERROR.PNG

Environment: EP Release Independent & SAP NetWeaver


Encountering the issue: Logon to the Enterprise Portal. Go to Home -> Work -> Universal Worklist .In the "Tasks" tab, select a workflow task.Perform the required action on this task (eg Approve/Reject) and then enter the reason for this decision via the UserDecisionNote field. You receive an error message “":Structure/Table DECISION_NOTE not found for SAP_WAPI_DECISION_COMPLETE".


Why does this issue occur:  The container element Decision_NOTE is not maintained for the relevant workflow item in the back-end system.


Resolving this occurrence:  In the Workflow Builder, you have the option of also specifying whether a note is to be entered for a user decision. There are three options: 'Not required', 'Note should be entered (requested)', 'Note must be entered (required)'.  At runtime, the system opens a note depending on the entry.  If you have already created user decision tasks in the customer namespace, you must also add the container element DECISION_NOTE (Type SOFM, Exporting) to the task container.

Until now session termination in portal required appearance of the pop-up window every time user closed or refreshed the screen with Application Integration iView.

From now on there will be an option to suppress appearance of that pop-up windowwhen executing the above mentioned scenarios.

In the below video you will see how to omit a session termination pop-up

 

 

Please refer to SAP Note 2114932 for further details

This blog is for portal end-users and content administrators who would like to learn about the new features developed in the latest Enterprise Portal SP for FLP on EP, their added value, and the configuration required.

The new features include:

  • SAP Smart Business analytics and fact sheets access
  • Enhanced personalization capabilities of Home Page / Tile Catalog
  • SAP Fiori borders in iViews and pages
  • Hiding groups on Home Page
  • Etc.


1 SAP Smart Business Analytical Apps Consumption

 

Analytical apps are supported in the Fiori Launchpad. These apps present up-to-date data from HANA databases in the home page and thus let end-users monitor business activities and key performance indicators (KPIs) in real time (more information).

This is how the analytic tiles in My Home group might look like:

HPwithAnalytics.JPG


Prerequisites:

  1. SAP Web Dispatcher or any other reverse proxy,which is responsible to dispatch the requests between the ABAP FES and Java server (EP).  It has to be configured to access SAP HANA catalogs.
  2. For FES minimum required SP please refer to SAP note 2031108.


To enable this feature administrators have to follow the steps in SP16 blog for Remote ABAP Content Consumption.

To manage HANA catalogs and groups the remote content editor is used. Both runtime and design-time HANA catalogs can be assigned to portal roles. The catalogs and groups can be defined in the SAP Fiori Launchpad Designer.

 

2 Search for SAP Fiori Fact Sheets

 

Fact sheets are applications that display contextual information and key facts about central objects of the SAP Business Suite, such as Customers or Suppliers. End-users can open a fact sheet tile and drill down into its details, or navigate from one fact sheet to its related fact sheets (more information here).


Prerequisites:

  1. SAP Web Dispatcher or any other reverse proxy, which is responsible to dispatch the requests between the ABAP FES and Java server (EP).  It has to be configured to access SAP HANA catalogs.
  2. For FES minimum required SP please refer to SAP note 2031108.

 

To enable this capability, administrators have to go to Framework Page Configuration, select Fiori Framework Page in dropdown list, check-in Enable Search for Fact Sheets checkbox and save:

FactSheetEnabled.JPG

 

In run-time an end-user will be able to search for the fact sheets using the enhanced Quick search bar:

FactSheetRT.JPG


FSSearch1.JPG


The search result looks as following:


FactSheetResult.JPG

3 SAP Fiori Borders in iViews and Pages

 

SAP Fiori borders allow to enhance end-user experience with portal iViews and pages. Portal administrators can enable the following:

  • Header bar - contains the iView/page title and a back button
  • Footer bar - can contain the following UI elements:

o Related Links – end-users select this option to open a popup window with the related links

o Dynamic Navigation – end-users select this option to open a popup window with a dynamic navigation iView/page

o Save as Tile – end-users save an iView/page as a tile to the Home page.


Procedure

In the portal, open an iView/page.

From the Show Category dropdown list, select Personalized Launcher and SAP Fiori Borders property:

HeadernFooterConfig.JPG


Note

  • For all iViews and pages except for SAPUI5 and SAP Fiori iViews, Header and footer bars is the default option.
  • For SAPUI5 and SAP Fiori iViews, No header and footer bars is the default option.
  • In the Launch in New Window property, select one of the following:
    • Display in Portal Content Area
    • Display in Separate Headerless Portal Window (standard mode).


SAP Fiori borders example:


BordersRT.JPG

If a user clicks on Related links, the following appears:

RelatedLinksRT.JPG:


 

 

4 Home Page Personalization Options

 

The configuration options are used by the administrators to provide end-users with various personalizing abilities for their home pages. If configured by an administrator, end-users can use:

  • Floating action
  • Option menu action
  • Hide/show groups.

The main switch Enable Personalization should be checked-in for other options to make an effect. If this option is switched off, in run-time there is no access to Tile Catalog and personalization actions:


PersSwitchOffConfig.JPG


NoPersonalization.JPG

4.1 Floating Action and Option Menu Action

 

If portal administrator enabled the following personalization options in FFP:

 

FloatingActionConfig.JPG

 

The end-users have floating action in the low right corner and Option menu action, both allowing to re-arrange the Home page:

 

FloatingActionRT.JPG

 

 

4.2  Hiding Groups on Home Page

 

If the option Enable Hide Groups in Option Menu is checked in FFP configuration, the corresponding entry will appear in Option menu in the Home Page:


HideGroupsConfig.JPG


HideGroup.JPG


By choosing this option end-users can control the groups to be hidden/displayed on the Home Page:


HideGroupPopUp.JPG



5 Search Options in Tile Catalog and Home Page

 

Several options allow the administrators to control search abilities for end-users, both in Tile catalog and Home page.

In Tile Catalog there might be no search possibilities at all:


TileCatalogNoSearch.JPG


Or three search options in Tile Catalog due to the following configuration on FFP:


SearchConfig.JPG


End-user experience with full search and filter capabilities will look like this:


TileCatalogSearch.JPG


Enable Search Icon in Header Bar option is relevant also for the Home Page.



6 Resetting User Personalization

 

After end-users have logged on to the SAP Fiori Launchpad for the first time, any consequent changes made by administrators are not reflected in the home page.

Personalization Data Cleanup tool is used to clear personalization and reset the home page for end users.

Warning: Resetting user personalization also removes all changes on the Home page made by the end user. There is no Undo for this action.


Procedure

Navigate to System Administration -> Support -> PCD Tools -> Personalization Data Cleanup.

In the Search for field, type a user login ID, and choose Go.

Select com.sap.portal.navigation.flp.pl.UserData entry, and choose Remove Application Personalization.


PCDClean.JPG


7 Role Editor Enhancement


A new Device Groups column displays the device group object IDs defined for objects in a role. A new Remote Content table displays the SAP Fiori catalogs and SAP Fiori groups, assigned to the role.


RoleConfigEnhanced.JPG


8 Enabling Fiori Framework Page Extensions

 

The Fiori Framework Page core capabilities can be extended by enabling custom plugin to load when the SAP Fiori launchpad opens.

This allows the customers to extend the standard FLP functionality, with, for example, an additional action in Option menu, a custom footer, etc.

The extensions are activated by the following FFP configuration (details):

  • Custom SAPUI5 Module Plugin Name
  • Custom Plugin URL.


9 Embedding SAP UI5 Apps

 

Administrators can embed SAPUI5 applications directly into the SAP Fiori launchpad on Portal without iframes to get a better performance, a harmonized look-and-feel, and good support for mobile browsers.

SAP UI5 application can be hosted on the portal server (Web Resource Repository is a recommended location).

The embedding is enabled with the following iVIew properties (detailed description):

  • Embed iView in SAP Fiori Launchpad
  • SAPUI5 Component Name
  • SAPUI5 URL Path.

 

 

Watch also this product demo focusing on the end user features described in this blog:




For more information: see SAP Documentation.

Background: You are utilizing the Universal Worklist and notice that there are no action buttons for the workflow setup e.g. approval/rejection appearing. This change may have be noticed after completing a recent upgrade. From the end-users perspective the buttons are no longer appearing in the Preview Area and after further investigation you notice that the Action Buttons are in in fact placed within the "Context Menu". The action buttons should be viewable and accesible through the context menu. You access the context menu by clicking on the dropdown menu which is beside the task names. Select the task and then select the dropdown. Are the action buttons visible here?


Adding buttons to a description area must be done by defining them in the view.


Buttons of Interest: Approve, Reject, Print Preview, Forward, Resubmit, Assign to me.


Why have the buttons disappeared?  The UWL UI was changed in 7.10 and higher releases so the look and feel of the UWL is different. Some buttons have indeed been removed e.g. the "You Can Also" area has been removed. In this scenario the buttons will appear only if the buttons (actions) are explicity defined within the UWL View in the XML configuration file.


Important Point: The buttons are only in the preview area if UserDecisionHandler is used and the actions are EXPLICITLY defined in the views.

 

Property of Interest: <Property name="showButtonInPreviewArea" value="yes"/> Important: Add the property showButtonInPreviewArea property as recommended in SAP Note: 1803438 to all Action definitions.


Core Notes:  SAP Note: 1730719 - Action buttons on UWL not visible after upgrade && SAP Note: 1803438 - Showing UWL item action as a button - only in context menu.



 

 




 

Definition: The Universal Worklist (UWL) gives users unified and centralized way to access their work and the relevant information in the portal. It collects tasks and notifications from multiple provider systems – SAPBusiness Workflow, Collaboration Task, Alert Framework and Knowledge Management Recent Notifications - in one list for one-stop access.

 

The Buttons: A UWL Action defines an activity that can be performed in UWL. Actions can be defined for views and items. Item actions can be displayed in the item preview, detail view and UWLiView as action buttons. Item actions are also displayed as context menu items for a certain workitem. View actions displayed as buttons can have an effect on none, one or multiple selected items. Group actions can be used in views to render decision options directly as check boxes or radio buttons in the item rows, for example, for mass execution scenarios.

 

Button Placement: Before attempting to move the buttons in terms of place you need to ensure they are defined correctly. Do you have the action defined in the view?

 

Switching Placement (Sample):

 

<Views>

<View name="com.sap.pct.erp.mss.tra.view.TripCheckView" selectionMode="SINGLESELECT" width="98%" supportedItemTypes="uwl.task.webflow.decision.TS00008267" columnOrder="statusIcon, subject, priority, creatorId, createdDate,

dueDate, processor, forwardedDate, attachmentCount, detailIcon, APPROVE, REJECT" sortby="priority:descend, dueDate:ascend, createdDate:descend"

tableDesign="STANDARD" visibleRowCount="10" headerVisible="yes" queryRange="undefined" tableNavigationFooterVisible="yes" tableNavigationType="CUSTOMNAV" refresh="300" dueDateSevere="0" dueDateWarning="0" emphasizedItems="none"

displayOnlyDefinedAttributes="yes" dynamicCreationAllowed="yes" actionPosition="bottom"

referenceBundle="com.sap.pct.erp.mss.tra.TripCheck">

<Actions>

<Action reference= "<ACTION BUTTON NAME REQUIRED>"/>

</Actions>

</View>

</Views>

 

 

Where I have <ACTION BUTTON NAME REQUIRED> you should have something like forward, etc.

 

Also if you are using the UserDecisionHandler, you will find that the buttons will appear on the view based on the actionPosition in the xml reference.  Your view name will probably also be different, as I just used this one as an example. Please also remember after changing the XML file to clear the cache and re-register the system.


Important:


If your item type is defined like this: <ItemTypes> <ItemType name="uwl.task.webflow.TS10007947.SAP_SRM" connector="WebFlowConnector" defaultView="DefaultView" defaultAction="launchSAPAction" executionMode="default"> <ItemTypeCriteria systemId="SAP_SRM" externalType="TS10007947" connector="WebFlowConnector"/>

 

For task e.g TS10007947 the buttons will only appear in the context menu. For the buttons to appear in the bottom, you will need to use UserDecisionHandler. 


Buttons that are associated with the task actions will appear at the bottom of the view depending on the action position reference in the XML file as I mentioned above.

 

The nice thing about the Action Handlers is that you can re-customize them. You can make the task into a decision task in the backend and use the UserDecisionHandler to launch the task in a different way.


Please see the help documentation:


http://help.sap.com/saphelp_nw73/helpdata/en/4a/f9b39a7b721115e10000000a42189c/content.htm

Background: In a setup which involves business requirements managed and accessed through the Enterprise Portal landscapes and environments can quick become diverse and multiplex.

 

Backdrop: The SAP NetWeaver Portal is one of the building blocks in the SAP NetWeaver architecture. With a Web Browser, users can begin work once they have been authenticated in the portal which offers a single point of access to information, enterprise applications, and services both inside and outside an organization.


Expanding Viewpoint: When using SAP NetWeaver Portal, organizations can give their employees, customers, partners, and suppliers a single point of access to the company applications, services, and information needed for conducting daily work. In addition, the portal offers business users the capability to easily create and manage portal pages and to generate their own portal content.

 

Why Monitor & Analyse?

The alchemists in their search for gold discovered many other things of greater value -  Arthur Schopenhauer


monitoring users.PNG











What does active monitoring provide?


  • View and analyse usage statistics
  • Identify performance concerns and bottlenecks
  • Identify generic system operation constraints
  • Analyse user activities
  • Reporting
  • Usage trends


The means of monitoring: The Computer Centre Management System in the Solution Manager, SAP’s service and support platform ensures central and efficient monitoring of SAP Enterprise Portal. Log data is displayed and analysed centrally in the Log Viewer (service of the J2EE server).  You can also monitor specific data directly in the portal.


Different Monitoring Technologies:


Actions

Filter Blog

By author:
By date:
By tag: