This is part of a multi-part series addressing myths about SAP Screen Personas.

This myth, similar to myth 3, probably started when someone saw a demo and extrapolated what they saw. (I hope no one does this based on what they saw at TechEd last week!) When I demo SAP Screen Personas to customers, I generally show how to simplify a screen and how to use a simple script to improve user productivity. Since all demos show only a subset of the product’s capabilities, viewers assume that with more time, you can do more. This is certainly true, to a point. The key is understanding where the boundaries lie with this line of thinking.
Yes, SAP Screen Personas is very flexible and allows you to modify many screen elements. For many customers, their goal is to simplify multi-screen transactions with Personas. Or, to retrieve information from different transactions and display the content on a single screen, without ever having to leave the initial screen.
Personas gives you many ways achieve these goals and others on the path to improved usability. Its capabilities allow you to remove buttons and controls, re-label any text on the screen, add new buttons to launch transactions or perform a series of keystrokes, change the color or shape of buttons, and add images to beautify the background or make screens more intuitive. You can even layer images to make screens more attractive and intuitive.

However, there are limits to what Personas can do on its own, based on its architecture and the underlying components on which it relies. For example:
We have documented some known limitations of Personas in two notes:
· Personas: 1884539
· Web GUI: 314568
Some of our beta customers encountered other limitations during the co-innovation process. We addressed many of their issues before we released the product. And, we continue to make enhancements based on customer feedback.
So, can you customize everything in Personas? Maybe not everything, but pretty much.

In the next post, we will explore myth 5, which will discuss the screen transformation process.
For SAP Imagineering, peter.spielvogel.
Read the entire SAP Screen Personas Myth vs. Truth series
Myth 4 (this post)