Skip to end of metadata
Go to start of metadata

SAP Screen Personas


Debugging in SAP Screen Personas 3.0

SAP SCREEN PERSONAS KNOWLEDGE BASE - by Sushant Priyadarshi , Clemens Gantert , Sebastian Steinhauer , Kranthi Kumar Muppala


This document will discuss about the various debugging options in personas 3.0.

UPDATE: Please refer to the following KBA for more detailed information on the available debugging options - Scripting: Error Handling and Debugging

Debugging Scripts

Use Case: You want to find out the value of variable "firstname" in your script.

Using session.utils.log (string)

In Scripting, you can display value of any variable in the "Logging" section of scripting window.

Using "debugger" statement

If you are using Google Chrome, then launch Developer Tools by pressing CTRL+SHIFT+I OR by going through Settings->More Tools->Developer Tools.

In your script, add the statement "debugger;" from where you want to start debugging and execute your script.

In the resulting window of Chrome's debugger window, execution will stop where your debugger statement is HIT and you can hover over your variable to find the value.


Suppressing Scripts of onLoad/onAfterRefresh

When you want to add/edit any script attached to "onLoad" and "onAfterRefresh" events, use URL parameter "&sap-personas-ignoreloadevents=X" when you launch Personas. Note that the SAP GUI for Html in older kernels may not support the URL parameter sap-personas-ignoreloadevents. Use the deprecated URL parameter suppressOnLoadEvents=X instead.




Important News

This knowledge base is not solely SAP provided content - but community driven. Please also check on SMP and for SAP released information and notes on SAP Screen Personas.

Create New Article

Compare SAP Screen Personas versions

Search the KB

How to Open OSS Message

 What information is needed for creating OSS message?

  1. Make Sure you are on the latest patches and notes.
  2. Kernel Patch Level
  3. Two Types of connections to your environment: HTTP and R/3
  4. All the connections should be tested with proper credentials provided
  5. Steps to re-create the issue
  6. Attach related logs
  7. File tickets against BC_PER

  • No labels