Xi4 Mobile Bi Rep Design en

Designing BI documents for mobile users
■ SAP BusinessObjects Mobile 4.0 Support Package 01
2011-02-17
Copyright © 2011 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP
Business ByDesign, and other SAP products and services mentioned herein as well as their respective
logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business
Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web
Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the
United States and in other countries. Business Objects is an SAP company.All other product and
service names mentioned are the trademarks of their respective companies. Data contained in this
document serves informational purposes only. National product specifications may vary.These materials
are subject to change without notice. These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only, without representation or warranty of any
kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The
only warranties for SAP Group 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.
2011-02-17
Contents
Chapter 1 About this guide......................................................................................................................5

1.1 Who should read this guide......................................................................................................5
1.2 What this guide contains..........................................................................................................5
Chapter 2 How documents are displayed on mobile devices..................................................................7
Chapter 3 Best practices for mobile document design............................................................................9

3.1 Designing Web Intelligence documents for mobile users........................................................11
3.1.1 Installing Web Intelligence images for mobile reports.............................................................13
3.2 Designing Crystal reports for mobile users............................................................................14
3.3 Setting up alerters on documents...........................................................................................15
Chapter 4 Embedding actions in report cells.........................................................................................17

4.1 Quick reference to embedded actions....................................................................................17
4.2 Syntax for actions..................................................................................................................18
4.3 Example: embed an action that launches a phone call to the sales representative named on the
selected report cell................................................................................................................20
Chapter 5 Linking documents................................................................................................................23
Appendix A More Information...................................................................................................................25
Index 27
3 2011-02-17
Contents
4 2011-02-17
About this guide
About this guide
1.1 Who should read this guide
This guide is intended for Enterprise report designers who want to provide users of SAP BusinessObjects
Mobile with data in a format that is optimized for display and ease-of-use when viewed on a mobile
device.
1.2 What this guide contains
This guide explains how to design business intelligence documents for optimum display and performance
when viewed on mobile devices.
5 2011-02-17
About this guide
6 2011-02-17
How documents are displayed on mobile devices
SAP BusinessObjects Mobile makes viewing and interacting with business intelligence content as
intuitive as possible on mobile devices. Documents are natively rendered to take full advantage of the
mobile device display space and capabilities.
The major presentation differences from the typical desktop user experience are:
• The user interface, which is designed to maximize ease-of-use for mobile content navigation.
• The ability to set up single-click document access by setting a default document or folder.
• The conversion of report tabs within Web Intelligence documents, which appear as a report list on
the device menu.
The constraints inherent in mobile devices

There are real limits to the size and complexity of reports that you can display on a small mobile device
while maintaining any semblance of acceptable usability; due to the small screen size, limited memory,
and interaction capabilities of mobile devices. Documents intended for mobile consumption must be
designed according to best practice design guidelines for mobile devices.
Related Topics
• Best practices for mobile document design
7 2011-02-17
8 2011-02-17
Best practices for mobile document design
SAP BusinessObjects Mobile user experience is best when reports are written specifically for easy
reading and navigation on a small screen.
Create and use mobile device design templates

Use image backgrounds as the report design template for target mobile devices. Embed an image of
the target device in the report background as a model of the screen size to help design the report to fit
the device constraints. In the Web Intelligence, for example, you can use the Insert Object feature to
place a *.jpg of your targeted mobile device in the background of a document, giving you an idea how
big the document is in relation to the device. Refer to the Performing interactive analysis using the
desktop interface for SAP BusinessObjects BI guide for details on using this feature.
IT Administrators are advised to install these graphics files on the SAP BusinessObjects Enterprise
server at the following location:
<BOBJ_INST_DIR>\SAP BusinessObjects Enterprise XI 4.0\images
SAP BusinessObjects provides two backgrounds for this purpose in the SAP BusinessObjects Mobile
download package. Alternatively, you can create your own backgrounds for specific mobile devices,
and save them to the same location.
Design for the device screen size

SAP BusinessObjects Mobile renders documents using pixel-to-pixel mapping of your report layout.
For the best control, authors can design reports to the pixel using the Java interface for SAP
BusinessObjects BI.
For optimal display on devices, do not allow graphics and data to exceed 2X the physical screen width
of the target devices.
Use a mobile device simulator to test your documents

Use a mobile device simulator on your desktop to simulate the mobile user experience when you are
authoring business intelligence content designed for mobile users. Install a device simulator on your
workstation and download SAP BusinessObjects Mobile on the simulator to test each report being
displayed inside the simulator. Testing your report ensures that there are no surprises.
Although the report appearance varies between the simulator and the mobile device, you get a good
idea of the size and format of your documents in terms of display and edit controls.
Group mobile documents under mobile category

It is recommended that the Enterprise administrator create a category in the BI launch pad called Mobile
under Corporate Categories, and assigns Mobile-related documents to this category. If the report
creators group all the documents designed specifically for mobile users into the same category, then
mobile users know that they are accessing content designed for mobile consumption through their
9 2011-02-17
mobile device. Hence, when users log into the mobile application using their mobile device, SAP
BusinessObjects Mobile presents the "Home" page with the list of mobile documents grouped under
Mobile category. This enables users to reduce the number of clicks required to access documents each
time they log on.
If you do not assign mobile documents to a category, SAP BusinessObjects Mobile displays folders
and documents located under Public folders or in the root folder.
In addition, you can search mobile documents by using the Search option. SAP BusinessObjects Mobile
searches the Mobile category and retrieves the list of documents that matches the specified search
string.
Design small reports

Report data sets can be large and can theoretically saturate available device memory. Large data sets
on the server can be mitigated by designing smaller report views. In Web Intelligence documents, drill
hierarchies in reports allow users to access related data in different report views. Drill hierarchies
alleviate the necessity of scrolling through large reports.
Small reports usually work better in mobile situations, because mobile devices are limited in bandwidth
and memory, and large reports are difficult to navigate in a small screen.
Make tables and graphs fit into the smallest device screen size
When you cannot reduce the size of tables and graphs:
• Design columns and labels to fit the screen of the target mobile devices.
• Do not design reports larger than two screen widths of the device screen.
• In reports that exceed a single screen width, make sure that at least two columns (and better three
or four columns) fit entirely in the physical screen width.
• Try to adjust the columns sizing so that the grid exactly fits the width of the mobile screen (or such
that at least a fixed number of columns exactly fits the screen width).
Use shortest significant names for headers and names

• Use codes instead of names for countries and cities.
• Use the short name for people (made up of their first name initials + their last name) instead of full
names.
• Use short labels for dates: FY04 instead of Year 2004, Q104 instead of 1st Quarter 2004.
Create short data display formats

Divide numbers by 1,000 or by 1,000,000 and express the numbers in K or in M using Web Intelligence
Custom format to reduce the number of digits displayed (to reduce column width). You can also put
k or m in the column title to make columns as small as feasible.
Change universe definitions of dimensions and measures, to enable drills on shortened text labels. For
example, you can convert the date dimension into two strings: a Text column Year string (four characters)
and a Quarter (two character) string. Then you can build an expression for YearAndQuarter made of
the Quarter string concatenated with the two last characters of Year.
To display charts with short numeric format display:

1. Convert the chart to a crosstab.
10 2011-02-17
2. Shorten the number digits as necessary (for example, divide by 1,000 or by 1,000,000).
3. Convert the crosstab back to a chart.
Use Position controls to maximize screen real estate

Place your elements as close as possible to the left corner of the report (for example, Charts, Grids, or
Tables):
• Place first report element, label, or grid (at position (0, 0)) so that no blank appears on the mobile
screen.
• Remove the border of the page (Left Margin, Top Margin) = (0 px, 0 px).
Limit font sizes to small-medium-large

Use Fonts 9, 12 and 15: Report display is limited to three available font sizes: Small, Medium, and
Large. Limiting the font sizes ensures greatest compatibility across the variety of device types available
in the marketplace. Font mapping on SAP BusinessObjects Mobile uses the following fonts:
• Arial 9 to map Small font of the mobile
• Arial 12 to map Medium font of the mobile
• Arial 15 to map Large font of the mobile
Design reports with these font sizes to achieve optimal rendering accuracy and consistency between
the server and client behavior.
Use small fonts for tables. Do not use bold styles for table content (use bold only for labels).
Design report structure to fit data within available column space

All numbers must display completely within available cell space. Strings must appear completely, or at
least the most significant part of each string must be visible.
Use short meaningful names for document and report tabs

In SAP BusinessObjects Mobile, report tabs are converted into a user selection list. Report tabs are
also displayed in the report context labels. Choose report tab names that are short and meaningful to
the end user as they become navigation aids. These name strings can be no longer than 20 characters.
Related Topics
• Designing Web Intelligence documents for mobile users
• Designing Crystal reports for mobile users
3.1 Designing Web Intelligence documents for mobile users
Use the Java interface for SAP BusinessObjects BI

For maximum formatting accuracy and control, use the Java interface for SAP BusinessObjects BI to
create and edit Web Intelligence documents for mobile users.
11 2011-02-17
Include additional icons to flag on-report alerters

SAP BusinessObjects Mobile users can subscribe to alerts that send a notification to the mobile device
when report values meet the conditions in specific Web Intelligence document alerters.
It is recommended not to place too many conditional alerts on one document (recommendation is 2-3
maximum), since device users cannot individually select only one of the available conditional alerts.
The SAP BusinessObjects Mobile download package includes trend and status alerting icons that can
be added to Web Intelligence conditional report alerters for greater visual impact when these reports
are viewed on mobile devices. IT administrators need to install these graphics files on the SAP
BusinessObjects Enterprise server at the following location:
To insert one of these icons into a report:
• Select the column for the alert and open the Alerters button.
• Select or create the alert you want activated on the selected data, then select the appropriate icon
for each condition of the alerter by selecting the Format button in the "Alerter Editor".
• In the Background section, select the Image from URL radio button and enter the following:
boimg://<image file name and extension>.
For example: boimg://icon_TrendRedDown.gif
Note:
The boimg:// prefix directs the Web Intelligence component to the images folder.
Integrate a background skin that portrays the screen size of the mobile device
SAP BusinessObjects provides two backgrounds for this purpose in the SAP BusinessObjects Mobile
download package, but you can create your own backgrounds for specific mobile devices, if required.
IT administrators need to install these graphics files on the SAP BusinessObjects Enterprise server at
the following location:
To set the background image for a Web Intelligence document creators, go to the Background Image
item in the Properties tab of Java interface foe SAP BusinessObjects BI and then select the Image
from URL radio button and enter the following: boimg://<image file name and extension>.
For example: boimg://skin_nokia.gif

Note:
The boimg:// prefix directs the Web Intelligence component to the images folder.
Refer to the Web Intelligence component of SAP BusinessObjects BI documentation for more information
on creating Web Intelligence reports.
Related Topics
• Designing Crystal reports for mobile users
12 2011-02-17
3.1.1 Installing Web Intelligence images for mobile reports
The SAP BusinessObjects Mobile server component includes image files designed to be used when
authoring Web Intelligence documents targeted at mobile devices. The images include:
• skins -- that provide a model of the screen size of some mobile devices, so you can design Web
Intelligence reports to fit specific device constraints
• icons -- to be used in cells that contain on-report alerters, so that alerters are easier to view via
mobile devices
The file names are:
Filename Description
skin_Blackberry.gif BlackBerry device skin
skin_Nokia.gif Nokia device skin
icon_SymbolFail.gif Fail alerts icon
icon_SymbolPass.gif: Pass alerts icon
icon_SymbolWarning.gif Warning alerts icon
icon_TrendGreenUp.gif Trend up (green) alerts icon
icon_TrendRedDown.gif Trend down (red) alerts icon
icon_TrendYellowDown.gif Trend down (yellow) alerts icon
icon_TrendYellowFlat.gif Trend flat (yellow) alerts icon
icon_TrendYellowUp.gif Trend up (yellow) alerts icon
Note:
The image files are automatically installed at the following path, so that they are easily accessible from
within the Web Intelligence component: <BOBJ_INST_DIR>\SAP BusinessObjects Enterprise
XI 4.0\images. If SAP BusinessObjects Mobile is installed on a dedicated server, as SAP
BusinessObjects recommends, administrators need to copy these image files from the Mobile server
13 2011-02-17
and paste them onto the SAP BusinessObjects Enterprise server at: <BOBJ_INST_DIR>\SAP
BusinessObjects Enterprise XI 4.0\images
3.2 Designing Crystal reports for mobile users
When designing Crystal reports for mobile users, verify that only the following elements are included
into the reports:
• Charts
• Simple sections and details
Note:
SAP BusinessObjects Mobile 4.0 supports viewing Crystal reports created by SAP Crystal Reports and
SAP Crystal Reports for Enterprise.
Font display
Font types, sizes, and formats can display differently on different types of mobile devices. It is
recommended that you test your reports on the popular devices used by your mobile users before you
make the reports available to users.
Table types
SAP BusinessObjects Mobile does not support crosstabs, used to analyze OLAP data, in Crystal reports.
Drilling capability
Drilling into data in Crystal reports is not supported on SAP BusinessObjects Mobile.
Prompts
SAP BusinessObjects Mobile only supports static prompts in Crystal Reports.
Linking documents and drill capability

Links to external documents and drill capability are not supported in Crystal reports when viewed by
users via a mobile device.
Parameters and filters

SAP BusinessObjects Mobile supports only simple parameters and static filters Crystal reports. Dynamic
and cascading parameters and the ability to modify filters are not supported.
ActiveX content
SAP BusinessObjects Mobile does not support ActiveX content in Crystal reports.
Database Logons
SAP BusinessObjects Mobile does not support prompting for database logons in Crystal reports. If a
Crystal report includes a database logon, the logon fails and the report cannot be opened.
14 2011-02-17
Suppression at view time

SAP BusinessObjects Mobile does not support suppression at view time in Crystal reports. The mobile
user cannot suppress sections while viewing a Crystal report.
Refer to the Crystal Reports documentation for more information on creating Crystal Reports.
Related Topics
• Designing Web Intelligence documents for mobile users
3.3 Setting up alerters on documents
Mobile device members can subscribe to alerts on specific server documents provided those documents
contain alerters. The following types of alerters are prerequisites for subscribing to alerts on the device:
Alert type supported on

devices Required pre-configuration of server document
Document Alert The document is modified on the server.

Scheduled Alert Configure the document with at least one schedule (recurrence) so that
the user receives an alert when the schedule is executed.
Conditional Data Alert Configure the document with a conditional alerter in SAP Crystal Reports
or the Web Intelligence component. The mobile user receives alerts for
all the conditions defined in the report (the user cannot choose to activate
a specific condition).
Scheduled Conditional Configure the document with at least one condition on at least one of the
Data Alert scheduled recurrences so that the mobile user can subscribe to receive
an alert each time the selected data fulfills at least one condition in the
server document.
Documents resulting from alerts and schedules can be saved locally to the device. The device user
selects this option in the "Alert Properties" screen.
For information on how to schedule documents, refer to the SAP BusinessObjects Enterprise BI
Launchpad User's Guide.
Note:
For information on how to include conditional alerters on the Web Intelligence and SAP Crystal reports,
refer to the Web Intelligence or SAP Crystal Reports documentation.
15 2011-02-17
16 2011-02-17
Embedding actions in report cells
SAP BusinessObjects Mobile supports user actions embedded in reports. Embedded actions defined
by the document creator enable end users to initiate a communication of a predefined type with another
application by clicking the embedded action hyperlink on the report.
For example, a typical business intelligence action requested by mobile users is the ability to leverage
predefined 'phoneto' or 'smsto' commands to contact a business collaborator who has a relationship
with the data content of the open reports.
Note:
You can embed local actions only on Web Intelligence documents.
Related Topics
• Example: embed an action that launches a phone call to the sales representative named on the
selected report cell
• Quick reference to embedded actions
4.1 Quick reference to embedded actions
The following actions are supported for SAP BusinessObjects Mobile:
17 2011-02-17
This command... Performs this action...
phoneto automatically dials a predefined phone number.
smsto enables you to send a text message to a predefined recipient.
plookup enables you to retrieve a phone number from the device address book, then either
call or send a text message to that contact.
Note:
plookup local action must be embedded within either the phototo or smsto local
action.
elookup enables you to retrieve an e-mail address from the address book and then send
an e-mail to that contact.
Note:
elookup local action must be embedded within the mailto local action.
mailto enables you to send an e-mail message to a predefined recipient.
Note:
The lookup action is deprecated in SAP BusinessObjects Mobile 4.0 , and is substituted with elookup
and plookup local actions. However, documents designed in earlier releases using lookup action still
works in SAP BusinessObjects Mobile 4.0.
Related Topics
• Syntax for actions
4.2 Syntax for actions
Understanding the syntax

The syntax for local actions is:
laction://action_name?param1=value1+param2=value2$
For example:
18 2011-02-17
Supported parame-
Local action Example ters
phoneto num, desc

laction://phoneto?num='0123456789'$
smsto num, desc

laction://smsto?num='0123456789'$
plookup name, desc

laction://phoneto?num=laction://plookup?name='jane doe'$$
elookup name, desc

laction://mailto?to=laction://elookup?name='jane doe'
&subject='Meeting'&body='What time is our meeting?'$$
mailto to, subject, body, desc

laction://mailto?to='john'&subject='Meeting'&body='What time is
our meeting?'
$
Including prompts
You can include prompts (or parameters) into local actions. The syntax for prompts is:
@paramName='Label|type|defaultValue'$
where:
• @paramName= indicates a prompt.
• label is the string that displays on the menu of the mobile device, before the field into which the
user will input data.
• type (optional) is the data type that the user is allowed to enter (the supported types are numeric,
decimal, password, string, url).
• defaultValue (optional) is the value that is entered in the field by default.
Note:
If you entered a default value, indicate the data type that the device can expect to receive as input.
• $ is a marker that signifies the end of an embedded action.
The lookup action can also take the @num parameter. For example:
<a href="laction://phoneto?@num='Enter number|numeric'$">Call</a>
The @ argument indicates to the device that the user can enter the phone number manually. When the
user accesses the report containing this action, the device displays the message "Enter number" and
expects the user to enter a numeric value, that is, a phone number.
Nesting multiple actions in a single command

You can nest actions to combine more than one action in a single command. For example, to create a
link that would look up "Edith Jansen" in the device phone book and then place a call to the number
that was found, you would use the following URL:
laction://phoneto?num=laction://plookup?name=Edith%20Jansen$$
19 2011-02-17
Note:
1. To include a space, it is necessary to enter %20.
2. When nesting multiple actions in single command, each laction must end with $.
Embedding multiple local actions in a particular cell in the report

You can embed multiple local actions in a particular cell in the report, thereby enabling users to perform
several actions on the cell content. You can simultaneously embed "phoneto", "smsto", and "mailto"
local actions on the cell content, and the mobile client displays a contextual menu with call, sms, and
e-mail local actions. However, you can perform only one action at a time.
The syntax for embedding multiple local actions is:

"mobile://menu?item1=laction1$îtem2=laction2$îtem3=laction3$" desc=\"item1 descriptionîtem2 descrip
tionîtem3 description \"
where:
• mobile://menu?
indicates the menu with which you can perform multiple actions on the cell.
• item1=laction1îtem2=laction2îtem3=laction3
indicates menu items with corresponding local actions.

• ^ (caret) is a marker that separates menu items.
For example,
<a href=\"mobile://menu?action1=laction://phoneto?num=laction://plookup?name= 'John'$$âction2=laction://mail
to?to='john@abc.com'&body=Test Body&subject=Test Subject$âction3=laction://smsto?num=1234567$\" desc=\"Call
John^Send Mail to John^Sms John\">MultipleActions</a>
Note:
Each menu item must have a corresponding description, which is the text that appears in the device
menu. If the number of menu items is not equal to the number of 'desc' provided, then the menu items
in the contextual menu are displayed as Open link[0], Open link[1] , Open link[2], and so on.
Related Topics
4.3 Example: embed an action that launches a phone call to the sales representative
named on the selected report cell
20 2011-02-17
As an example of how a local action works, here is a URL from a Web Intelligence report, which uses
the report variable '[SalesREPName] ' to invoke the local device Personal Information Manager application
(PIM) for making a phone call:
="<a href=\'laction://phoneto?num=laction://plookup?name='"+[SalesREPName]+"'$$\'desc=\'Call'+[SalesREP
Name]+'\'>[SalesREPName]</a>"
In this case "Jane Doe" is the current report value of [SalesREPName]. When the mobile user selects
the hyperlink on the report cell, the option "Call Jane Doe" displays on the device menu. When the user
selects "Call Jane Doe" this launches a lookup in the device address book for "Jane Doe" and then
activates a phone call to the corresponding phone number.
In this example, the formula terms have the following meanings:
Terms Definition
The phone call action that is invoked using the resulting phone
number that the PIM look up delivers from the local directory of the
phone.
phoneto? Note:
This feature can only be used if the device has a PIM package that
supports it. The phone directory must have this name in it to invoke
the call successfully.
The plookup action passes a value (phone number) to one of the

plookup? other two options. This feature can only be used if the device has a
PIM package that supports it.
The name to submit to the device PIM (Personal Information Manager

application) for lookup ('Jane Doe' which is the current report value
of [SalesREPName]).
name=
The function uses the first and last name as separate search param-
eters, so in the example above the function would search for 'jane'
and 'doe' in the directory.
The text that appears on the device menu when the hyperlink in the
desc= report cell containing the action is selected. (For example, 'Call Jane
Doe').
Related Topics
• Syntax for actions
21 2011-02-17
22 2011-02-17
Linking documents
Linking documents
Note:
SAP BusinessObjects Mobile supports document links in Web Intelligence reports, but not in Crystal
reports.
Document links are specific actions that enable navigation from one document to another. In the Web
Intelligence component, OpenDocument links are created through URL syntax in a cell that looks like
this:
=<a href=\"action_url\" desc=\"action_description\">"+[Cellvalue]+"</a>"
Specifically, the SAP BusinessObjects OpenDocument syntax is as follows:

action_url=\' http://<server>:<port>/BOE/OpenDocument/opendoc/openDocument.jsp?sDocName=<docname>\'
When a link is placed inside a Web Intelligence document, the field containing the OpenDocument link
appears as a hyperlink. Mobile users can move from the source document to the target document by
browsing to the cell that contains the hyperlink, and then pressing OK or selecting Open from the menu.
Supported parameters for document linking

SAP BusinessObjects Mobile supports a subset of the Web Intelligence OpenDocument syntax.
Specifically, SAP BusinessObjects Mobile supports the following parameters:
• sPath
sPath indicates the relative paths to the folder containing the current document, using the following
syntax:
[My+folder],[My+subfolder],
If this parameter is omitted, the function calls the document using the iDocId.
• sDocName
The sDocName parameter can be used without the iDocId when the document name is unique in
the CMS. If two documents in the CMS have the same name, you must use this parameter in
conjunction with sPath and/or iDocID. If a unique identifier is not specified and two documents
exist in the CMS under the same name, SAP BusinessObjects Mobile displays the first document
it retrieves when it searches the CMS.
• iDocID
iDocID represents the unique document CUID in the CMS.
• sReportName
sReportName indicates which report to open when the target document contains multiple reports.
• sRefresh
23 2011-02-17
Linking documents
sRefresh determines that a refresh is forced when the target document or report is opened.
• lsS[NAME]
lsS[NAME] specifies a value for a single prompt. [NAME] represents the text of the prompt.
• lsM[NAME]
lsM[NAME] specifies multiple values for a prompt. [NAME] represents the text of the prompt.
Note:
SAP BusinessObjects Mobile is case sensitive, so you need to use the exact syntax specified above.
For more information about viewing reports and document using URLs, refer the following guides:
• Viewing Documents Using OpenDocument
• Viewing Crystal Reports Using URL Reporting
24 2011-02-17
More Information
More Information
Information Resource Location
SAP BusinessObjects product infor-

http://www.sap.com
mation
Navigate to http://help.sap.com/businessobjects and on the "SAP Busi-

nessObjects Overview" side panel click All Products.
You can access the most up-to-date documentation covering all SAP
BusinessObjects products and their deployment at the SAP Help Portal.
You can download PDF versions or installable HTML libraries.
SAP Help Portal
Certain guides are stored on the SAP Service Marketplace and are not
available from the SAP Help Portal. These guides are listed on the Help
Portal accompanied by a link to the SAP Service Marketplace. Customers
with a maintenance agreement have an authorized user ID to access
this site. To obtain an ID, contact your customer support representative.
http://service.sap.com/bosap-support > Documentation

• Installation guides: https://service.sap.com/bosap-instguides
• Release notes: http://service.sap.com/releasenotes
The SAP Service Marketplace stores certain installation guides, upgrade
and migration guides, deployment guides, release notes and Supported
SAP Service Marketplace
Platforms documents. Customers with a maintenance agreement have
an authorized user ID to access this site. Contact your customer support
representative to obtain an ID. If you are redirected to the SAP Service
Marketplace from the SAP Help Portal, use the menu in the navigation
pane on the left to locate the category containing the documentation you
want to access.
https://cw.sdn.sap.com/cw/community/docupedia
Docupedia Docupedia provides additional documentation resources, a collaborative
authoring environment, and an interactive feedback channel.
https://boc.sdn.sap.com/
Developer resources
https://www.sdn.sap.com/irj/sdn/businessobjects-sdklibrary
25 2011-02-17
More Information
Information Resource Location
SAP BusinessObjects articles on https://www.sdn.sap.com/irj/boc/businessobjects-articles

the SAP Community Network These articles were formerly known as technical papers.
https://service.sap.com/notes
Notes
These notes were formerly known as Knowledge Base articles.
Forums on the SAP Community

https://www.sdn.sap.com/irj/scn/forums
Network
http://www.sap.com/services/education
Training From traditional classroom learning to targeted e-learning seminars, we

can offer a training package to suit your learning needs and preferred
learning style.
http://service.sap.com/bosap-support
The SAP Support Portal contains information about Customer Support

Online customer support programs and services. It also has links to a wide range of technical in-
formation and downloads. Customers with a maintenance agreement
have an authorized user ID to access this site. To obtain an ID, contact
your customer support representative.
http://www.sap.com/services/bysubject/businessobjectsconsulting
Consultants can accompany you from the initial analysis stage to the
Consulting delivery of your deployment project. Expertise is available in topics such
as relational and multidimensional databases, connectivity, database
design tools, and customized embedding technology.
26 2011-02-17
Index
A I R
actions icons report design templates 9, 11
embedding 17 for report design 11 reports
example 20 for reports 13 displaying 7
local 17, 18 icons
remote 17, 18 for report alerters 11
syntax for 17, 18 installation
S
Active-X graphics files 13 skins 9, 11
Crystal reports 14 SMS
alerter embedded action 17
creating 15
L
syntax
alerts links for actions 17, 18
icons for Web Intelligence 13 documents 23
T
C O
templates
crosstabs OpenDoc 23 for mobile reports 9, 11
Crystal reports 14
Crystal reports
designing 14 P W
mobile limitations 14
parameters 14 parameters Web Intelligence
Crystal reports 14 alert icons 13
phoneto designing documents 11
F embedded action 17, 20 device specific skins 13
prompts icons 11
folders in local actions 18 linking documents 23
default folder 9
fonts
Crystal reports 14
27 2011-02-17
Index
28 2011-02-17

Xi4 Mobile Bi Rep Design en

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Xi4 Mobile Bi Rep Design en

Enviado por

Direitos autorais:

Formatos disponíveis

Designing BI documents for mobile users

■ SAP BusinessObjects Mobile 4.0 Support Package 01

Chapter 1 About this guide......................................................................................................................5

Chapter 2 How documents are displayed on mobile devices..................................................................7

Chapter 3 Best practices for mobile document design............................................................................9

Chapter 4 Embedding actions in report cells.........................................................................................17

Chapter 5 Linking documents................................................................................................................23

Appendix A More Information...................................................................................................................25

About this guide

1.1 Who should read this guide

1.2 What this guide contains

How documents are displayed on mobile devices

The constraints inherent in mobile devices

Best practices for mobile document design

Create and use mobile device design templates

Design for the device screen size

Use a mobile device simulator to test your documents

Group mobile documents under mobile category

Design small reports

Use shortest significant names for headers and names

Create short data display formats

To display charts with short numeric format display:

Use Position controls to maximize screen real estate

Limit font sizes to small-medium-large

Design report structure to fit data within available column space

Use short meaningful names for document and report tabs

3.1 Designing Web Intelligence documents for mobile users

Use the Java interface for SAP BusinessObjects BI

Include additional icons to flag on-report alerters

For example: boimg://skin_nokia.gif

3.1.1 Installing Web Intelligence images for mobile reports

The file names are:

skin_Blackberry.gif BlackBerry device skin

skin_Nokia.gif Nokia device skin

icon_SymbolFail.gif Fail alerts icon

icon_SymbolPass.gif: Pass alerts icon

icon_SymbolWarning.gif Warning alerts icon

icon_TrendGreenUp.gif Trend up (green) alerts icon

icon_TrendRedDown.gif Trend down (red) alerts icon

icon_TrendYellowDown.gif Trend down (yellow) alerts icon

icon_TrendYellowFlat.gif Trend flat (yellow) alerts icon

icon_TrendYellowUp.gif Trend up (yellow) alerts icon

3.2 Designing Crystal reports for mobile users

Linking documents and drill capability

Parameters and filters

Suppression at view time

3.3 Setting up alerters on documents

Alert type supported on

Document Alert The document is modified on the server.

Embedding actions in report cells

4.1 Quick reference to embedded actions

The following actions are supported for SAP BusinessObjects Mobile:

This command... Performs this action...

phoneto automatically dials a predefined phone number.

smsto enables you to send a text message to a predefined recipient.

mailto enables you to send an e-mail message to a predefined recipient.

4.2 Syntax for actions

Understanding the syntax

phoneto num, desc

smsto num, desc

plookup name, desc

elookup name, desc