SAP UX and Personas 3.018/03/2015
In 2013, SAP presented the new UX strategy, based on three pillars:
1. NEW: This part of the UX strategy focuses on all new applications to be developed, which is used as a technology SAPUI5.
2. RENEW: the most widely used SAP transactions will be unlocked with Fiori apps (now there are already several hundred available).
3. ENABLE: This part of the strategy focuses on providing tools that customers themselves are able to improve the user interface of transactions.
SAP Screen Personas (or simply Personas) belongs in this last block home and is already at version 3.0. Especially considering the announcement of SAP at SAPPHIRE in June that Personas is license-free for SAP customers, many companies are using version 2.0 went to work. Version 3.0 has been since mid-August in ramp-up, but the list of participants is now closed. Should we wait for 3.0 or we’re going to work with 2.0? To answer that question, we first present once again briefly the advantages of Personas in general:
• Since the new screens are much easier to use, users will be more inclined to accept SAP software;
• By simplifying the screens will have to be made less cost of training and education;
• Because there are fewer fields and / or screens need to be completed, productivity increases.
If achieving these benefits is the highest priority, then the implementation of version 2.0 the right choice. In version 3.0, however, is some of the advantages worth the wait is worth it:
• Global theming and extended copy functions make it easier to use once again chosen design;
• Many functionality is in version 2.0 in the advanced settings screen, and has now moved to menus so that the functionality is better accessible;
• Integration in the web gui and thereby improve performance. Also, Silverlight is not required for rendering, resulting in no local software installation is needed.
For companies that already have the 2.0 version implemented, there is already a wiki available to migrate to version 3.0. You can find this wiki here.
October 11, 2014