Administration Guide Screen Persona

PUBLIC
2017-06-22
Administration Guide
Content
1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Object Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 Flavor Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Sharing a Flavor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Flavor Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 Theme Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Theme Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Assigning and Un-assign Themes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.3 Icon Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Icon Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.4 Resource Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Resource Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.5 Template Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Template Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3 User Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.1 Assigning Flavors to Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.2 User Maintenance Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4 Role Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.1 Managing Role Assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.2 Role Maintenance Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5 Customizing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.1 Whitelist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.2 Defining Corporate Colors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.3 Defining Corporate Fonts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.4 Quick Styles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Creating Quick Styles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.5 Flavor Naming Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.6 Transaction Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.7 Screen Overwrite Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.8 Control Overwrite Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.9 Import Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.10 Import Flavor from Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6 Additional Administrative Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2 PUBLIC Content
6.1 Global Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.2 Flavor Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Migrating Flavors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
7 Analytics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Content PUBLIC 3
1 Getting Started
This document provides an overview of the Administrative Transaction for SAP Screen Personas 3.0.
The administrative transaction for SAP Screen Personas 3.0 is divided into 5 sections. You can access it by
entering /PERSONAS/ADMIN.
The following functions are supported by the administrative user:
● Maintaining objects - import, transport, create, and maintain the following:

○ Flavors
○ Themes
○ Resources
○ Icons
○ Templates
● User and Role Administration - assign flavors, roles, and themes to a user.
● Customizing - modify the user experience of SAP Screen Personas.
○ Whitelist - URL's, Function Modules, and F4 Help
○ Modify Fonts/Colors
○ Create Quick Styles
○ Modify Naming Rules
○ Import Clients/Import Flavors
● Analytics - set up variables and gather analytics on the usage.
● Additional Administrative Tasks - check your system, migrate Flavors and change settings.
4 PUBLIC Getting Started
2 Object Maintenance
This page provides an overview of SAP Screen Personas 3.0 objects and how to maintain them.
There are 5 objects that are supported by SAP Screen Personas 3.0:
● Flavors - a flavor identifies a specific personalization for a particular SAP transaction. An SAP transaction can
have infinite number of flavors.
● Themes - visual treatments that can be saved and applied to any Flavor.A flavor can only have one theme.
● Resources - images that can be uploaded for use in Flavors. The following image types are supported: png,
jpg/jpeg, gif, and zip.Resources can be used for illustrative purposes or as backgrounds for your Flavors.
● Icons - small images that guide user actions. You can use existing SAP icons or add custom objects. The
supported icon image file formats are png, jpg/jpeg, gif, and zip.
● Templates - a drag and drop tool that enables you to build consistent flavors. A flavor can have multiple
templates applied to it.
There are 5 actions that can be performed in the Object Maintenace section:
Create via Upload - upload Icons, Resources, and Templates into SAP Screen Personas. The following image
types are supported: png, jpg/jpeg, gif, and zip.
Import -upload multiple objects (Flavors, Themes, Icons, etc.) at once. Files must be in zip file format.
Transport - transport multiple objects between environments.
Transport pushed objects - transport objects between clients in the same environment.
Changelog - logs changes that have been made to objects.
Related Information
Flavor Maintenance [page 6]

Theme Maintenance [page 10]
Icon Maintenance [page 14]
Resource Maintenance [page 16]
Object Maintenance PUBLIC 5
Template Maintenance [page 18]
2.1 Flavor Maintenance
This page provides an overview of Flavor Maintenance screens.
There are several actions that can be done to maintain Flavors from the main SAP Screen Personas
Administration screen. See Object Maintenance [page 5] for more information.
The administrator can find an individual Flavor or a range of Flavors based on various search criteria like:
● Name
● Owner
● Transaction Code
● Flavor Group
● Personas Version
● If Flavor is Unused
● Deleted Flavors
● Flavors marked as Final
● Other: Language, Transports Date, etc.
Flavor Maintenance screen[s] allow for both mass maintenance (multiple Flavors) and single Flavor maintenance.
Mass Maintenance
Import - upload Flavors, Icons, Resources, and Themes. Objects are uploaded simultaneously using zip file.
Note
To select multiple objects at once hold the CTRL key.
● Check -checks to see if all notes have been applied successfully

● Export - export the selected object
● Transport - transport multiple objects at once between environments
● Delete - marks the Object for deletion. If the object is marked for deletion, the users will not see it. but it will
exist in the database.
● Restore- restores the object from the deleted mode.
● Delete from DB - permanently deletes objects from the database.
Note
Once the object is deleted from the DB, it cannot be restored.
Single Flavor Maintenance
● Check, Export, Set Final Status, and Transport - Same as mass maintenance.
● Change/Display - change the Metadata for the Flavor.
● Remove History - remove version history of the Flavor.
6 PUBLIC Object Maintenance
Note
The following action of removing history cannot be reversed.
● Copy - Copy the Flavor.

● Show Version History - shows the history of the Flavor, if it has been versioned.
● Show Object Relations - shows all the objects that are used in the Flavor.
● Show Changelog - shows all the changes made to the Flavor.
● Translate - translate the Flavor inot another language, as well as view previous translations. See how to
Translate Flavor below.
● Documentation and Attachment - attach documentation for the Flavor.
● Sharing/Assignment - add users and/or roles that can access the Flavor.
How to Translate
1. Open the Maintenance Screen for Flavor or Template, click Change button.
2. When in Change mode, click Translate button.
3. From the Translation Screen, click Add language.
4. Select the Target Language.
5. In the Translations table, select the object that you want to change and click Edit Longtext button
6. Enter the Target Text.
7. Click Back to previous to go back to the Translation Screen.
8. Save
Related Information
Object Maintenance [page 5]

Flavor Properties [page 9]
2.1.1 Sharing a Flavor
Context
Sharing Flavors allows specific users or roles to access Flavors. Once the Flavor is shared, it will be visible in the
Flavor Gallery for the user or role.
Procedure
1. Open the Flavor Maintenance Screen for the flavor that you want to share.
2. Click Change
3. For the User, click Go to User. For the Role, clickGo to Role. If you do not see a user, go to transaction SU01 to
create one. If you do not see a role, go to transaction PFCG and create or copy a role.
Results
The user will see the flavor in the Flavor Gallery.
2.1.2 Flavor Properties
The following are the properties for the flavor:
Table 1:
Section Fields
Preview Allows you to preview the flavor.
Metadata ● GUID
● Framework
● Application ID - Transaction Code
● Average Rating – determined by your users
● Personas Version - the version of Personas the Flavor
was created in
● Size
● Reference Flavor ID
● Reference Flavor Name
● Created On
● Created By
● Changed On
● Changed By
● Deleted Flag
● History - shows the version history of the flavor
● Usage - shows what other objects the flavor uses
● Original System
● Client
● Latest TR- latest transport
● Transported On
● TR Status - transported status
Section Fields
Properties ● Name
● Description
● Final Version - controlled by the Done & Lock action
● Group - what group of flavor this flavor belongs to
● IT Support
● Original Language
● Show Changelog - shows all the changes that have been
made to the flavor
● Translate - See Flavor Maintenance [page 6] for step-by-
step instructions on translating Flavors
● Documentation and Attachment – attach any document
to your Flavors
● Owner
● Theme ID
● Theme Name
● Transaction Code
● Transaction Variant
Sharing /Assignment You can add users or roles to any flavor.
● User
● Assign Flag
● Full Name
● Role
● Assign Flag
● Description
2.2 Theme Maintenance
This page provides an overview of Theme Maintenance screens.
There are several actions that can be done to maintain Themes from the main SAP Screen Personas
The administrator can find an individual Theme or a range of Themes based on various search criteria like:
● Name
● Description
● Only unused Themes
● Deleted Themes
● Other: Transport Data, Administrative Data
Various mass maintenance or single theme maintenance can be performed.
Mass Maintenance
Note

Note
Single Theme Maintenance
● Check, and Transport - Same as mass maintenance.

● Copy - duplicate the Theme.
● Export - xport the Theme.
● Change/Display - change the Metadata for the Theme.
● Change Image - change an image for the Theme.
● Show Object Relations - shows all the objects that are used by or uses in this Theme.
● Transport Status - the flag shows if the Theme has been transported.
● Show Changelog - shows all the changes that have been made to the Theme.
● Assignment - add roles and transaction that the Theme is available. For the end user the Theme is visible in
the Theme Gallery.
Note
By default the ability to create or edit Themes is part of the /PERSONAS/ADMIN_ROLE.
Related Information
Object Maintenance [page 5]

Theme Properties [page 12]
Assigning and Un-assign Themes [page 13]
2.2.1 Theme Properties
The following are the properties for the theme:
Table 2:
Section Fields
Thumbnail ● Change Image

● Size
● Remove Image
Section Fields
Metadata ● GUID
● Personas version
● Created On
● Created Time
● Created By
● Changed On
● Changed By
● Changed Time
● Deleted Flag
● Usage - show object relations, and where the object is be
ing used
● Original System
● Client
● Latest TR - latest transport
● Transported On
● TR Status - transport status
Properties of Theme ● Name

● Description
● Show Changelog- shows all changes to the Theme.
Assignment of a Theme ● Unassign Theme for each Role Name/Transaction/

Theme Rank
● Assign Theme to Role/Transaction
2.2.2 Assigning and Un-assign Themes
Context
This option allows the administration user to control what theme(s) will be used for specific roles and
transactions.
Procedure
1. Enter the transaction /personas/admin into the Transaction field.

2. In the Theme Maintenance section, use the search feature to find the GUID of a theme and choose Display.
The screen displays the details of the selected theme.
3. Click the Change button in the toolbar.
4. In the Assignment section, enter the roles and transaction into their respective fields. Transaction codes can
also be specified using wildcards.
5. Click Save.
Results
The Theme is now assigned to the roles and or transactions specified. It will be available to all business users
within the assigned roles and transactions.
2.3 Icon Maintenance
This page provides an overview of Icon Maintenance screen.
There are several actions that can be done to maintain Icons on the main SAP Screen Personas Administration
screen. See Object Maintenance [page 5] for more information.
The administrator can find an individual Icon or a range of Icons based on various search criteria:
● Owner
● Description
● Group
● Unused Icons
● Shipped by SAP Icons
● Deleted Icons
Mass Maintenance
Note

Note
Single Icon Maintenance
● Check - Same as mass maintenance.
● Change/Display - change the Metadata for the Icon.
● Copy - duplicate the Icon.
● Export - export the Icon.
● Change Image - change an image of the Icon.
● Show Object Relations - shows all the objects that are used by or uses this Icon.
● Transport Status - the flag shows if the Icon has been transported.
● Show Changelog - shows all the changes that have been made to the Icon.
2.3.1 Icon Properties
The following are the properties for the icon:
Table 3:
Section Fields
Thumbnail Small image of the icon
● Change Image
Section Fields
Metadata ● Type
● Size
● Created On
● Created By
● Changed On
● Changed By
● Delete Flag
● Show the icon
● Original System
● Client
● Latest TR
● Transported on
● TR Status
● Show Changelog
● Show Object Relations
Icon ● Icon ID
● Description
● Group the icon belongs to
● Owner
2.4 Resource Maintenance
There are several actions that can be done to maintain Resources from the main SAP Screen Personas
The administrator can find an individual Resource or a range of Resources based on various search criteria:
● Name
● Description
● Only Unused Resources
● Public Available Resources
● Deleted Resources
Various mass maintenance or single resource maintenance can be performed.
Mass Maintenance
Note
Note
Single Resource Maintenance
● Check, Export, and Transport - Same as mass maintenance.

● Change/Display - change the Metadata for the Resource.
● Copy - Copy the Resource.
● Show - shows the Resource in another window.
● Show Object Relations - shows all the objects that are used by or uses this Resource.
● Show Changelog - shows all the changes that have been made to the Resource.
2.4.1 Resource Properties
The following are the properties for the resources:
Table 4:
Sections Fields
Thumbnail Small image of your resource
Metatdata of Theme ● GUID

● File Format
● Full Size
● Created On
● Created By
● Changed On
● Changed By
● Delete Flag
● Usage – where the resource is used
● Original System
● Client
● Transported On
● TR Status
Resource ● Name
● Description
● Owner
● Public Flag
● Show Changelog- shows all the changes that have been
made to the resource
Preview ● Regenerated Thumbnail

● Show
● Upload
2.5 Template Maintenance
This page provides an overview of Template Maintenance screens.
There are several actions that can be done to maintain Templates from the main SAP Screen Personas
The administrator can find an individual Template or a range of Templates based on various search criteria:
● Name
● Description
● Group
● Unused Templates
● Deleted Templates
● Other: Translation Data, Transport Data, Administrative Data
Mass Maintenance
Note

Note
Single Template Maintenance
● Check, Export, and Transport -same as mass maintenance.

● Change/Display - change the Metadata for the Template.
● Copy - copy the Template.
● Change/Remove Image - change or remove an image for the Template.
● Translate - translate the text on the Template.
● Show Changelog - shows all the changes that have been made to the Resource.
● Display Specifications - shows you the XML for the Template.
● Show Object Relations - shows all the objects that are used by or uses this Template.
How to Translate
1. Open the Maintenance Screen for Flavor or Template, click Change button.
2. When in Change mode, click Translate button.
3. From the Translation Screen, click Add language.
4. Select the Target Language.
5. In the Translations table, select the object that you want to change and click Edit Longtext button
6. Enter the Target Text.
7. Click Back to previous to go back to the Translation Screen.
8. Save
2.5.1 Template Properties
The following are the properties for the template:
Table 5:
Sections Fields
Preview ● Change Image - change the image of the template

● Remove Image
● Size - size of the image
Sections Fields
Properties ● Template ID
● Name
● Description
● Group - group template belongs to
● Owner
● Icon
● Original Language
● Translate - See Template Maintenance [page 18] on how
to translate a template
● Show Changelog
● Change Specification -XML for the Template
Metadata ● Created On
● Created By
● Changed On
● Changed By
● Deleted Flag
● Usage - Show Object Relations
● Original System/Client
● Transported on
● TR Status - transport status
3 User Administration
This page provides an overview of user administration on the SAP Screen Personas Administration screen.
There are two ways you can assign a specific flavor to a user from the administrative screen.
User Centric [page 23]
● Each User has the following properties that can be edited on the User Maintenance screen
Change/Display - allows you to change the User Data and add flavors from the Flavor Gallery to Flavor
Manager. If required, you can set the Flavor as default in the Flavor Manager.
Maintain Roles - launches transaction SU01 in the Roles tab.
Reset Role Assignments, Default Flavor - resets the user to the original roles and flavors.
Note
The list of roles that are listed in the User Status and Authorization section only lists roles that use Personas
Authorization Objects.
Note
The Flavor Theme always overrides the Theme that is assigned to the user.
Role centric [page 26]
22 PUBLIC User Administration
3.1 Assigning Flavors to Users
Context
This option allows the Personas Administrator to view and manage the user configurations and also assign flavors
to users.
Additional tasks that can be performed through this screen are:
● Unlock Users
● View User Status and Authorizations
● Maintain Roles (Refer to ) [page 27]
● Reset Role Assignments and Default Flavor
User Administration PUBLIC 23
Procedure
1. Enter the transaction /PERSONAS/ADMIN in the Transaction field.

2. In the User and Role Maintenance section, enter the username, Framework, and Application ID or Transaction
Code in the respective fields.
3. Click Display User Configurations.
4. Click the Change icon in the toolbar.
5. Select the desired flavors from the Flavor Gallery list in the Available Flavors section and choose the Assign
Flavor to User button. The selected flavors will be moved to the Flavor Manager list in the Available Flavors
section.
6. If you want to make this the default Flavor for the user, click the Default radio button in the Flavor Manager
list.
7. Repeat steps 6 and 7 to assign more Flavors.
Results
The Flavor is now available for the business user in the Flavor Manager in the UI.
To Un-assign a Flavor
To move the Flavor from the Flavor Manager, select the Flavor from the Flavor Manager list in the Available
Flavors sections and choose the Left Arrow from User button. This will move the Flavor to the Flavor Gallery list.
The business user will no longer be able to see this Flavor in the Flavor Manager.
3.2 User Maintenance Properties
The following are the properties for the User Maintenance screen:
Table 6:
Section Fields
User Data ● User

● Framework
● Application ID
● Lock/Unlock
● Reference User
● Name
● Alias
● Status
24 PUBLIC User Administration
Section Fields
User Status and Authorizations ● Role

● Profile
● Start Date
● End Date
● Runtime Framework
● Runtime Application ID
● Runtime Activity
● Edit Framework
● Edit Application ID
● Edit Activity
● Administrator
Available Flavors ● Flavors Gallery - all flavors that are available for this Ap
plication ID
Flavor Name
Description
Owner
IT Supported Flag
Shared w. User Flag
● Flavor Manager - all flavors that are visible in the users
Flavor Manager
Flavor Name
Description
Owner
Default Flag
IT Supported Flag
By Role Flag
Role Name
Assignment of Themes ● Name

● Description
● Created By
● Created On
● Changed By
● Changed On
● Original System
● Client
● Transport Status
User Administration PUBLIC 25
4 Role Administration
This page provides an overview of role administration on the SAP Screen Personas Administration screen.
As mentioned before, there are two ways you can assign a specific flavor to a user from the administrative screen.
● User centric
● Role centric
The role centeric method assigns Flavors and Themes to a roles, rather than specifc users.
Select a role, if the role is not visible in the drop-down list, click the Display/Search and Add a role.
For each role you can add a Theme per Transacation code or/and a Flavor. So all of the users that belong to that
role will be able to use the Themes and Flavors. For step by step instructions on how to add Roles or Manage Roles
see Managing Role Assignments [page 27]
Note
The Flavor Theme always overrides the Theme that is assigned to the role.
26 PUBLIC Role Administration
4.1 Managing Role Assignments
Context
This option allows the administrator user to manage roles.
Personas Roles are a subset of PFCG roles. These roles need to be enabled for Personas . You can access the
Roles table through the /PERSONAS/ROLES transaction.
Note
If you have selected a PFCG role, the metadata parameters will be displayed in read-only mode and cannot be
modified.
Procedure
1. Enter the transaction /PERSONAS/ADMIN in the Transaction field.

2. Choose Allowed Roles in the Role Text Field. This will take you to the Role List screen which lists all the roles
enabled for use in the Personas system.
3. If you do not see your role, click Search/Display. Once the Personas Role Maintenance screen opens, click Add
Role. You can either enter a brand new role or click next to Role text field to see a list of available roles.
4. From this screen you can perform the following actions: Assign Theme - Click Plus Icon enter Transaction
Code or * as wild card, select Personas Theme.
1. Assign Theme - Click the Plus Icon enter Transaction Code or * as wild card, and then select Personas
Theme.
2. Flavor Sharing/Assignment - Click the Share Single/Multiple button in the menu bar and then select a single
or multiple Flavors. Click Share selected flavors.
Mark Flavors as Flavor Assigned to the role and, if needed set it as Default
5. Click Save to save your work.
Results
The flavors and themes are now assigned to the role you have selected using the Manage Role Assignment
option.
Role Administration PUBLIC 27
4.2 Role Maintenance Properties
The following are the properties for the Role Item screen:
Table 7:
Section Fields
Metadata ● Role
● Role Name
● Comp. Role
● Role Rank
● Created On
● Created By
● Changed On
● Changed By
● Deleted
● Original system/Client
● Latest TR
● Transported on
● TR Status
● Show Changelog
Theme Assignment ● Add or Remove Themes

App ID/Transactoin Code
Theme ID
Theme Name
Theme Rank
Flavor Sharing/Assignment ● Share Single/Multiple or Unshare

Role Flavors Linkage
ID
Flavor Assigned Flag
Default Flavor Flag
28 PUBLIC Role Administration
5 Customizing
This page provides an overview of customizing capabilities on the SAP Screen Personas Administration screen
The following list of things that can be customized from the SAP Screen Personas Admin transaction:
● Whitelist: F4, URL, Function Module

● Corporate Fonts, Colors
● Transaction Mapping
● Screen Overwrite Entries
● Import Clients
● Create Help Include
● Quick Styles
● Flavor Naming Rules
● Control Overwrite Entries
● Import Flavor from Library
5.1 Whitelist
Use
Note
These features are not available in Web Dynpro ABAP applications.
When creating your flavors, you may want to use additional controls to enhance your flavor. In order to control the
security risk around objects like URL's, Function Modules, and F4 Help lists, SAP Screen Personas has
implemented whitelists.
Customizing PUBLIC 29
Features
F4 Help Whitelist
SAP Screen Personas 3.0 allows you to use an existing Table/Field for F4 help or to create a custom F4 help list.
Search helps for custom Personas fields must be explicitly allowed first via a whitelist before they can be used in
Flavors. To create a custom F4 help, select the Goto menu option in the/PERSONAS/ADMIN transaction, and
select Whitelist > F4 Help Whitelist.
You can add table/field combinations to the whitelist which will then be available as F4 Help Text Fields in the
Flavor Editor. These fields rely on the search help definition of the referenced fields in the Data Dictionary. In
addition, it is also possible to specify what authorization object / field / activity should be checked against the
user’s profile before allowing access to the search help value list. This is useful in case the search help provides
access to sensitive information.
Create Help INCLUDE
This function is used to allow definition of a custom search help assignment in event a suitable search help is not
used for any existing field. Adding a new field / search help association into the standard structure
CI_PERSONAS_SHLP, this structure / field name combination can then be referred to in flavors when a custom F4
Help field is needed.
URL Whitelist
You can use URLs in SAP Screen Personas to add external content to your flavors. In order to make sure that an
external URL works in your Flavor, you have to add the URL to the URL Whitelist. This whitelist defines which
URLs are available in the Flavor Editor for the creation of custom HTML controls and web page launch buttons. To
create the URL Whitelist, select the Goto menu option in the Personas Administration /PERSONAS/ADMIN and
select Whitelist > URL Whitelist.
Check URL Whitelist
You can check if the URL is accessible based on the whitelist entries.
FM (Function Module) Whitelist
You can use Remote Function Calls in your scripts. In order to have the function module available to you, you have
to add it to the FM Whitelist. To create the FM Whitelist, select the Goto menu option in the Personas
Administration /PERSONAS/ADMIN and select Whitelist > FM Whitelist.
5.2 Defining Corporate Colors
You can determine the set of colors available in the color picker in the Flavor Editor.
To define corporate colors, choose the related entry in the Goto > Corporate Colors menu bar in transaction
Personas Administration/PERSONAS/ADMIN. The corporate colors will be visible under the Corporate Colors
section in Themes, Border Style, or Fill Color options on the Edit Toolbar.
30 PUBLIC Customizing
5.3 Defining Corporate Fonts
You can determine the set of fonts that are available in Flavor Editor.
Defining corporate fonts, choose the related entry in the Goto > Corporate Fonts menu in /PERSONAS/ADMIN
transaction.
The defined fonts will appear on the Edit Toolbar and Themes.
5.4 Quick Styles
Quick Styles allow you to apply the same style to multiple objects at once. For example, the same Font/Font Color
can be applied to Labels, Sticky Notes, Group Boxes, Transaction buttons, and any other objects that have the
Font Family and Font Color as the Style Properties.
To define Quick Styles, choose the related entry in the GoTo > Quick Styles menu bar in /PERSONAS/ADMIN
transaction. For each Quick Style, enter the Property Name, and Quick Style Property Value.
Note
The Property Name has to be one of the properties that is available in the Style Properties in the
scripting inspector.
5.4.1 Creating Quick Styles
Context
This option allows the Personas Administrator to create Quick Styles that can be used by the end-user to create
flavors if they have the proper authorizations.
Procedure
1. Start /PERSONAS/ADMIN
2. Launch Quick Styles
3. Click Display/Change
4. Click New Entries
5. Enter ID and Description
6. Enter Property Name and Quick Style Property Value
Example
5.5 Flavor Naming Rules
You can require users to follow a standard naming convention when creating Flavors.
To define the naming convention choose the related entry in the GoTo > Flavor Naming Rules menu bar in /
PERSONAS/ADMIN transaction.
5.6 Transaction Mapping
Transactions enable the inclusion of screens of other transactions without leaving the original transaction context.
For example, you can navigate from transaction/PERSONAS/ADMIN to the flavor maintenance screens. These
screens belong to transaction /PERSONAS/FLAVORS. As you don’t leave the original transaction context in some
special navigation scenarios, for example when you navigate from /PERSONAS/ADMIN to /PERSONAS/FLAVORS
the transaction-mapping customizing table has been introduced. This customizing table enables administrators
to maintain the main transaction code of the related report sources. Usually it is only necessary to maintain the
program/report name and the new transaction code field. For example: Report /PERSONAS/FLAVOR_UI belongs
to the new transaction code /PERSONAS/FLAVORS.
5.7 Screen Overwrite Entries
SAP Screen Personas identifies screen modifications with a combination of “Transaction code and Screen
Number”. There are certain transactions where the program name and/or screen number changes at runtime.
This could result in inconsistent behavior, such as hidden controls showing up on your Flavors. To handle such
transactions in SAP Screen Personas, you need to define overwrite rules that would handle such cases.
In order to set up Screen Overwrite Rules, you need to know the App ID, ABAP Program Name, Old Screen
Number, , and the New Screen Number. The Program/screen number can be viewed by clicking the arrow at the
bottom right corner of the status bar on any transaction screen. You must execute the Screen Overwrite
Conversion before the Flavor is created.
Note
For most transactions SAP Screen Personas team has already pre-seeded all the Screen Overwrite Entries.
This feature is not available in Web Dynpro ABAP.
5.8 Control Overwrite Entries
Just like the Screen Overwrite, in certain transactions, when switching tabs or clicking or expanding panel
buttons, the Control ID changes dynamically for some of the controls. Control ID can be seen in properties
window of SAP Screen Personas editor when editing any flavor. You must identify such changes before creating
your Flavor. In order to create the Control ID overwrite rules., you need the Control ID. it can be found in the
properties window of the SAP Screen Personas editor when editing any Flavor. Important parameters to be
considered are App ID, Program Name, Screen Number and Overwrite ID Alias.
Note
In most transactions, SAP Screen Personas has pre-seeded all known Control Overwrite Entries.
This feature is not available in Web Dynpro ABAP.
5.9 Import Clients
All Personas objects (flavors, themes, resources) are saved in the application table. When transporting these
objects into a target system, they are only imported into the SAP master client (000). To make them available in
different clients than 000, on target system side you have to maintain this table.
5.10 Import Flavor from Library
In order to demonstrate best practices, the SAP Screen Personas team has created a demo transaction with
several Flavors. These Flavors can serve as an example or starting point for your project.
6 Additional Administrative Tasks
This page provides an overview of additional administrative tasks on the SAP Screen Personas Administration
screen.
The SAP Screen Personas Administration screen gives you the following options:
Run Health Check Tool
● This tool checks to see if your configurations have been implemented appropriately. Green lights mean that
things are configured correctly. Yellow lights mean that something is not optimal, but they system is still
operational. If the status of any of the elements is red, please contact your administrator.
Note
This feature is not available in Web Dynpro ABAP application.
Perform Clean Activities
This option allows you to permanently delete the following:
● Flavors
● Resources
● Themes
● Icons
● Roles
● Templates
● Flavor Cache
● MIME Cache
● Migration Mapping
Note
● Usage Mapping -shows where objects are being used.

● Performance Tools - synchronize information about transported objects from Transport Management System
with performance- optimized internal database tables.
● Data Model Analysis - checks for consistency among Flavors and Resources.
Migrating Flavors [page 41]
● Migration of flavors created from earlier SAP Screen Personas versions to the present version.
Show Flavor Migrations
● Displays all the flavors that have been migrated.
Change Settings
● Allows you to enable or disable some of the features in SAP Screen Personas such as hiding the original
screen, usage logging, wide layout and more.
Additional Administrative Tasks PUBLIC 35
The settings table can be viewed/edited using transaction SM30 and opeining maintenance view for table /
PERSONAS/STTNGS.
6.1 Global Settings
Global settings that can be changed from the Administration screen:
Table 8: Global Personas Properties
Property Name Available in Description
DISABLE_DEEP_LINK SP03+ Disables or enables deep link icon on fla

vor selection tab. If value set to 'X' then
deep link icon is invisible.
This property supports personalization.

Currently personalization can be set on
role level but not on the user level.
If any role assigned to user has set per

sonalized property /PERSONAS/
DISABLE_DEEP_LINK to ‘X’ then deep
link icon will be disabled. Personalization
on role level is only supported if property
PFCG_PERSONALIZATION is set to “X”.
DISABLE_JAVAGUI SP03+ When set to ‘X’ disables JAVA GUI client.
Starting from SP05, this property sup

ports PFCG personalization. If any role
assigned to user has set personalized
property /PERSONAS/
DISABLE_JAVAGUI to ‘X’ then JAVA GUI
client will be disabled. Personalization on
role level is only supported if property
36 PUBLIC Additional Administrative Tasks
DISABLE_ORIG_SCREEN SP03+ When set to ‘X’ Personas disables origi

nal screen Flavor in the Flavor selection
tab. The Original Screen Flavor will not
displayed. Currently is only supported by
WEB GUI.
This property supports PFCG personali

zation. If any role assigned to user has
set personalized property /PERSONAS/
DISABLE_ORIG_SCREEN to ‘X’ then orig
inal screen flavor will be disabled. Per
sonalization on role level is only sup
ported if property
DISABLE_WEBDYNPRO SP03+ When set to ‘X’ Personas is disabled for

WEB DYNPRO GUI client.

property /PERSONAS/
DISABLE_WEBDYNPRO to ‘X’ then
WEBDYNPRO GUI client will be disabled.
Personalization on role level is only sup
ported if property
DISABLE_WEBGUI SP03+ When set to ‘X’ Personas is disabled for

WEB GUI client.

property /PERSONAS/DISABLE_WEBGUI
to ‘X’ then WEB GUI client will be disa
bled. Personalization on role level is only
supported if property
DISABLE_WINGUI SP03+ When set to ‘X’ Personas is disabled for

WINDOWS GUI client.

property /PERSONAS/DISABLE_WINGUI
to ‘X’ then WIN GUI client will be disa
bled. Personalization on role level is only
supported if property
ENABLE_BDT_MODE SP05 When set to “X”, SAP Screen Personas

BDT mode is enabled.*
Note
This feature is piloted with only a few
customers.
HIDE_PERSONAS_CLIENT SP04+ If set to "X" SAP Screen Personas will

hide the Personas "P in WEB GUI.
This property supports PFCG personali

zation. If any role assigned to user has
set personalized property /PERSONAS/
HIDE_PERSONAS_CLIENT to ‘X’ then
SAP Screen Personas hides the Per
sonas P in the Personas WEB GUI. Per
sonalization on role level is only sup
ported if property
IMAGE_MAX_SIZE SP03+ The maximum size or resource in kB

which can be uploaded to Personas. For
example 1024 = 1 MB. If uploaded file is
bigger as this property defines, the re
source is not uploaded and error mes
sage is shown. The default value is 2048.
LIBRARY_PUBLIC SP03+ The location of personas flavor libraries

in MIME repository. Library is a zip file
containing serialized flavors. User can
define his/her own libraries by creating a
property name starting with LIBRARY
and assigning appropriate path to the li
braries in MIME repository. As this prop
erty defines path to folder and folder can
contain multiple files, then it is possible
to reference multiple flavor libraries with
one property. The libraries are managed
using Admin UI in transaction /
personas/admin menu Goto->’Flavor
Library.
The flavor libraries from MIME reposi

tory are loaded by pressing Sync Library.
Library synchronization should be per
formed once after each modification of
LIBRARY<…>” property or after already
defined library “zip” file updated. All
found library zip files along with flavors
inside them can be viewed by perform
ing Search action.
When flavor library is selected then it is

possible to import all flavors from se
lected library.
ORIG_SYST_CHECK_OFF SP03+ When objects are transported, they get

locked in all import-systems. Setting pa
rameter ORIG_SYST_CHECK_OFF to "X"
disables this check.
PERSONAS_LOG_LEVEL SP05 Sets log level for Personas Logger Utility.

For more information, please check KBA
“SAP Screen Personas Logging and
Tracing Tool”.
PFCG_PERSONALIZATION SP03+ When set to ‘X’ enables properties

DISABLE_ORIG_SCREEN and
DISABLE_DEEP_LINK definition in role
Personalization tab in transaction PFCG .
The value of personalized properties
DISABLE_ORIG_SCREEN and
DISABLE_DEEP_LINK still can be set/
edited but the values are not taken into
account.
PUSH_TO_CLIENT SP05 When set, objects, which should be

transported, will be pushed to specified
client. It allows to transport objects only
from client, which is set in this setting.
USER_FLOW_ENABLED SP03, SP04 When set to ‘X’ enables user flow log
ging. This property can be set using
transaction /PERSONAS/ADMIN.SP03:
Menu Goto-> Analytics should be
selected. By pressing Enable usage
logging, user flow logging is enabled.
SP04+: by pressing button to the right of
Usage Logging. The report can be using
Measurement point ID USER_FLOW.
Note
Starting from SP05, this setting is not
available. User flow logging can be
enabled/disabled only from /
PERSONAS/ADMIN and /PERSONAS/
ANALYTICS transactions.
Note
Use capital X when setting any of the above parameters.
6.2 Flavor Migration
Use
Flavors can be migrated from the Screen Personas 2.0 systems to the current systems. This will help you to avoid
recreating the flavors already created in your 2.0 systems.
Process
There are two options to migrate flavors:
● Migration: Select to migrate all the flavors

● Show Migration: Select particular flavors to be migrated, ignore selected flavors, or mark a flavor as migrated
6.2.1 Migrating Flavors
Use
As an administrator user, you can trigger migration of flavors created in earlier SAP Screen Personas versions into
the current SAP Screen Personas version. This helps you avoid recreating flavors. It is required to have both SAP
Screen Personas version 1.0/2.0 AND version 3.0 installed in the same instance for the migration to work.
Procedure
Note
1. Open transaction Personas Administrations/PERSONAS/ADMIN.

2. From the Migration option in the menu bar, choose the Migrate 2.0 Flavors option from the drop-down list.
3. In the Flavor Migration screen, select the required flavors based on the criteria given in Flavor Selection and
Status Selection sections.
4. Alternatively, select the Show Migrations option from the Migration drop-down menu.
5. Select the required flavors and choose either Migrate Selection, Ignore selected Flavors , or Mark as migrated.
6. Choose to save the changes.
You can view the migrations using the Show Migrations option in the Migrations dropdown menu.
7 Analytics
This page provides an overview of analytics on the SAP Screen Personas Administration screen.
Measurement Analysis uses the session.utils.log Measurement <Measuring Point>,

{MeasurementName:MeasurementValue} statement in scripting to log any data you would like to save as a
measurement. After you have finished your measurements you can use the Measurement Analytics tool on the
Admin UI side to analyze your measurements. Click on button Measurement Point to maintain measurement
points, which groups measurements of the same type. On the measurement selection screen, you can restrict
your measurement search for to a specific date/time range. You can also select whether you like to display the
analytics results in table or as CSV.
Click on the Usage Logging to enable or disable analytics measurement.
42 PUBLIC Analytics
Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does
not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency
(see: http://help.sap.com/disclaimer).
Important Disclaimers and Legal Information PUBLIC 43
go.sap.com/registration/
contact.html
© 2017 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company. The information contained herein may
be changed without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP or SAP affiliate company products and services
are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks
of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.

Administration Guide Screen Persona

Uploaded by

Copyright:

Available Formats

Administration Guide Screen Persona

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Administration Guide Screen Persona

Uploaded by

Copyright:

Available Formats

PUBLIC

6 Additional Administrative Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

The following functions are supported by the administrative user:

● Maintaining objects - import, transport, create, and maintain the following:

Transport - transport multiple objects between environments.

Changelog - logs changes that have been made to objects.

Flavor Maintenance [page 6]

2.1 Flavor Maintenance

This page provides an overview of Flavor Maintenance screens.

● Check -checks to see if all notes have been applied successfully

Single Flavor Maintenance

● Copy - Copy the Flavor.

Object Maintenance [page 5]

2.1.1 Sharing a Flavor

The user will see the flavor in the Flavor Gallery.

The following are the properties for the flavor:

Preview Allows you to preview the flavor.

Sharing /Assignment You can add users or roles to any flavor.

2.2 Theme Maintenance

This page provides an overview of Theme Maintenance screens.

Various mass maintenance or single theme maintenance can be performed.

● Check -checks to see if all notes have been applied successfully

Single Theme Maintenance

● Check, and Transport - Same as mass maintenance.

Object Maintenance [page 5]

2.2.1 Theme Properties

The following are the properties for the theme:

Thumbnail ● Change Image

Properties of Theme ● Name

Assignment of a Theme ● Unassign Theme for each Role Name/Transaction/

2.2.2 Assigning and Un-assign Themes

1. Enter the transaction /personas/admin into the Transaction field.

2.3 Icon Maintenance

This page provides an overview of Icon Maintenance screen.

● Check -checks to see if all notes have been applied successfully

Single Icon Maintenance

2.3.1 Icon Properties

The following are the properties for the icon:

Thumbnail Small image of the icon

2.4 Resource Maintenance

Various mass maintenance or single resource maintenance can be performed.

Single Resource Maintenance

● Check, Export, and Transport - Same as mass maintenance.

The following are the properties for the resources:

Thumbnail Small image of your resource

Metatdata of Theme ● GUID

Preview ● Regenerated Thumbnail

2.5 Template Maintenance

This page provides an overview of Template Maintenance screens.

● Check -checks to see if all notes have been applied successfully

Single Template Maintenance

● Check, Export, and Transport -same as mass maintenance.

The following are the properties for the template:

Preview ● Change Image - change the image of the template

User Centric [page 23]

Role centric [page 26]

Additional tasks that can be performed through this screen are:

1. Enter the transaction /PERSONAS/ADMIN in the Transaction field.

3.2 User Maintenance Properties

User Data ● User

DISABLE_DEEP_LINK SP03+ Disables or enables deep link icon on fla

If any role assigned to user has set per

Starting from SP05, this property sup

DISABLE_ORIG_SCREEN SP03+ When set to ‘X’ Personas disables origi

This property supports PFCG personali

Starting from SP05, this property sup

Starting from SP05, this property sup

Starting from SP05, this property sup

This property supports PFCG personali

The flavor libraries from MIME reposi