Professional Documents
Culture Documents
SAP Lumira
Document Version: 2.2 – 2018-07-31
The What's New Guide for SAP Lumira provides an overview of the features and enhancements that have been
added to the SAP Lumira . It directs you to the available product documentation to get you started using the
new features.
For information on how to use the features described in this document, see SAP Lumira product guides for the
appropriate release.
For the latest information on supported data sources, middleware, and service pack versions for SAP Lumira ,
see the Product Availability Matrix (PAM) available on SAP Support Portal at https://
apps.support.sap.com/sap/support/pam . Here you can enter SAP LUMIRA in the search field to retrieve the
information.
You can find more detailed information on the features in the Application Designer Guide: Designing Analysis
Applications.
There is no restriction on the nesting level. However, you cannot drag a composite into itself, either directly or
indirectly via some intermediate composite, as a circular reference will cause the runtime to fail.
For more information, see “Nesting Composites” in the Application Designer Guide: Designing Analysis
Applications on the SAP Help Portal at https://help.sap.com.
An application can contain multiple composites. Each composite can contain its own collection of components.
You can select components saved in a bookmark definition in these composites to be included as part of the
bookmark definition of an application.
To apply bookmark functionality to a composite, add a Bookmarks technical component to the Outline view. A
Bookmarks technical component is needed for each composite you want to include in the overall parent
bookmark definition. You can then define which components within a composite you would like to bookmark.
To ensure that the selected composite components are added to the overall parent bookmark definition, set
the Save with Parent Bookmark property value to true.
Planning Functions and Planning Sequences have properties that can be edited.
● Load in Script
● Process Changed Data
You can now copy data from the crosstab and paste the values into planning-enabled cells in any other
crosstab, Microsoft Excel sheet, Notepad, etc.
When working with copy and paste functionality in crosstabs, please note the following points:
● Using the copy functionality in crosstabs works for crosstabs that are in planning or non-planning mode.
Whereas the paste functionality is only possible if the crosstab is in planning mode, which means the
crosstab has input-enabled cells.
● You can only copy the visible area of the selected crosstab part on your screen. If you select for example a
column for copying that can be scrolled only the visible part of the column on your screen is copied.
For more information, see chapter “Working With Copy and Paste in Crosstabs” in the Application Designer
Guide: Designing Analysis Applications on the SAP Help Portal at http://help.sap.com .
There are several improvements in crosstabs when you use them at runtime.
There are constraints in the ways you can drag and drop in crosstabs.
Result members can be dragged, but cannot be dropped on drop areas or other dimension members. For other
members you cannot choose result members as drop targets.
The only drop action available to "Result" members is to drop them outside the crosstab to remove them from
the view.
● Chart Context Menu. For more information see the chapter called Chart Context Menu Enhancements.
● Chart Reset Color Property Setting and Conditional Formatting. For more information see the chapter
called Chart Reset Color Property Setting and Conditional Formatting.
● If a chart has more than 10,000 data points, the chart will show the first 10,000 data points along with a
message that not all data points are shown. You can retain or change the filter appropriately to view
required data points.
The Color property setting of the Chart takes higher priority over Conditional Formatting Settings.
The Color property setting of the Chart component can customize color settings down to the level of specific
data points. The Conditional Formatting Settings technical component sets conditional formatting colors in
more general way, in a chart or crosstab. The Color property setting takes higher priority over the Conditional
Formatting Settings. We recommend that you use either one color setting, or the other.
If you want to set a default color on all bars of a chart, for example, we recommend that you create a
conditional formatting rule that sets the color on is any value.
The Reset Color button in the Chart property tab, allows you to clear the Color property setting. Clearing the
property setting allows the Conditional Formatting Settings color to take effect.
The types of Chart that have this Reset Color property are as follows:
● bar
● column
● stacked bar
● stacked column
● dual axis
● line
● line chart for time series
● area
The context menu of the Chart component at runtime has been enhanced.
The context menu of the Chart component now offers the application user the option of adding a fixed or
dynamic Reference Line. The Reference Line context menu item allows the user to show important dates or
values in the Chart. The application user can edit the type of reference line and also format the appearance of
the Reference Line. To format the Reference Line, select the options available to them in the Add Reference Line
dialog. The Add Reference Line appears when you select the Reference Line context menu item. When the user
adds one Reference Line to the Chart, and selects the context menu again, the Manage Reference Lines dialog
appears. The Manage Reference Lines dialog lists all the reference lines added to the Chart. It also allows the
user to select to show or hide, add, edit, or remove a reference line.
The context menu also displays several other analytical actions from other components, such as the Crosstab
or Spreadsheet components, for example. The context menu items displayed depend on the element selected.
For details about these other context menu items, you can refer to the chapter in the Application Designer
Guide: Designing Analysis Applications called Using the Context Menu (Technical Component) on the Help
Portal at https://help.sap.com.
Use the Grouped List basic component to add items to a list, and to group the items into categories.
The Grouped List is a basic component. The Grouped List allows you to add data sources, composites or
components to a list, and to categorize these items into groups. You can insert items and adjust the order in
which they appear in the list. A new value can be added at design time, or at runtime through scripting. If the
list grows beyond the size set in the design tool, the scroll bar appears. The Grouped List component has the
following specific properties:
The Scroll Container component enables or disables horizontal or vertical scrolling on supported container
components at design time, or runtime of the application.
To enable scrolling, set the Horizontal Scrolling Enabled or Vertical Scrolling Enabled properties of the Scroll
Container to true. When these properties are set to true, the horizontal, and vertical scroll bars appear in the
Scroll Container, when they are required. When the user drags an item into the Scroll Container, the scroll bars
automatically scroll in the same direction. This automatic scrolling enables the user to see where they are
dropping an item within the Scroll Container.
● Authoring
● Document
2.1.11.1 Authoring
The application designer can use the Authoring technical component to enable end users to change the layout
of an existing dashboard.
When an application designer has created an application for an end user, they can use the Authoring technical
component to select an area in the application that the application user can change or personalize at runtime.
Use the Authoring Area property of the Authoring technical component to select the Composite component in
the application you want to enable for authoring at runtime.
The Composite component is the only component supported as an area in which authoring can be enabled.
Note
2.1.11.2 Document
Use the Document technical component to save a Lumira document to the BI platform.
We recommend you use the Document technical component with the Authoring and Components technical
components only. For more information, you can refer to the following SAP Note:2654202 .
You can use roundtrip optimization to improve the performance of analysis applications, especially if the
application is running over an internet connection with high latency.
In previous Lumira releases, some actions the user performed (such as clicks) led to roundtrips from Web
browser to server - even if this was not really needed.. These roundtrips were to synchronize a state change to
the server that would be needed later for a different user interaction. However, too many server roundtrips
reduce application performance. To optimize roundtrip performance, the number of server roundtrips is
reduced by queuing (holding back) changes caused by clicking in the browser. These changes are only sent to
the server in a roundtrip when it's necessary to keep the application's state on the server consistent.
For more information, see “Using Roundtrip Optimization” in the Application Designer Guide: Designing
Analysis Applications on the SAP Help Portal at http://help.sap.com .
● Use optimized components that load JavaScript and CSS Files only when needed.
● Use the application property Fast Startup Enabled.
For more information see “Optimizing Application Startup” in the Appplication Designer Guide: Designing
Anaylsis Applications on the SAP Help Portal at http://help.sap.com .
The Component API reference for SAP Lumira Designer has been enhanced as follows:
New Methods
New Constants
● CsvSeparator
○ CsvSeparator.COMMA
○ CsvSeparator.TAB
○ CsvSeparator.SEMICOLON
○ CsvSeparator.SPACE
New Parameters
● isFullView
It occurs in the following scripting method:
○ exportView
● isFullPanel
It occurs in the following scripting method:
○ exportPanelView
You can now specify the current document directly in special calls, to get all offline data sources of the
document at once.
In previous SAP Lumira releases, assigning an offline data source to a data source alias at runtime was only
possible via the CONNECTION.getConnections() API, which, if the document contains at least one offline
data source, also returns a special connection representing the document itself. This connection can then be
passed to APIs like CONNECTION.setSystemId() or DataSourceAlias.assignDataSource(). Since the
call to CONNECTION.getConnections() can cause performance issues, it's better to be able to specify the
current document directly in these API calls. For this reason, the special alias Document that represents the
current document has been introduced.
For more information see “Using Offline Data Sources in Scripting ” in the Application Designer Guide:
Designing Analysis Applications on the SAP Help Portal at http://help.sap.com
You can now navigate from one script to another directly in the script editor.
In the script editor, press and hold the CTRL key in an empty area of the script editor and hover over the script
text.
The script text that you hover over becomes a hyperlink, if it is a call to one of the following elements:
The Export CSV technical component has been enhanced to allow selection of CSV separator at runtime.
Using two new scripting methods for the separator property getSeparator(); and setSeparator();, you
can now create scripting so that the application user can select a CSV separator character dynamically at
runtime. They can choose one of the following CSV separator types:
● comma
● tab
● semicolon
● space
The following enhancements have been made to the Export PDF feature:
Related Information
You can decide which crosstabs are exported with auto sized column widths.
Use the Components with Auto Size Column Width property to allow you to optimize how data column content
is displayed when exported to PDF in a report style. You can use the Components with Auto Size Column Width
property at design time, to select which crosstabs in an application are exported with column widths that are
auto sized.When a crosstab has auto sized column widths, it means that the column widths adapt to the
Optional parameter allows you to export the full contents of the panel or application to PDF.
The scripting method exportPanelView(); includes an optional parameter called isFullPanel, which
allows you to export the full contents of the panel to PDF. The scripting method exportView() includes an
optional parameter called isFullView,which allows you to export the full contents of an application to PDF.
These optional parameters are set to true by default. With the isFullPanel and isFullView parameters set
to true, the entire contents of the panel or application is exported to PDF. You can opt to change the optional
parameters value to false. Changing the parameters to false means that only the section of the panel, or
application that is visible in the viewport is exported to PDF. If the visible view is small, scrollbars may be
included in the export to PDF. When you open an application that is already scripted with the previous version
of exportPanelView(); or exportView();, the parameters isFullPanel or isFullView are set to true
by default.
You can include components within composites when exporting an application to PDF. To export composite
components to PDF, you must add just one Export PDF technical component on any level within the
application. Components within composites for export to PDF can be selected in two ways:
● The first way is to use the Edit Report Order dialog of the Components property of the Export PDF technical
component.
● The second way is to select components within composites from any scope in the application by using
scripting.
With an X.509 certificate, logon to BI platform from Lumira Designer works without providing user credentials.
In SAP Lumira Documents mode and in SAP BusinessObjects BI Platform (Legacy) mode of Lumira Designer,
you can now log on to the BI platform using an X.509 certificate that is stored in the Microsoft Windows
certificate store on the local machine.
For more information, see “Launching SAP Lumira Designer in Different Modes” in the Application Designer
Guide: Designing Analysis Applications on SAP Help Portal.
You can now use variants in Lumira Designer. Query variants store selection data for variables in a SAP BW
query.
A variant has a technical name, a text description, and a scope. The scope can be either USER or PUBLIC.
To be able to use variants, you have to set the application property Variant Mode to either Query variants or
Document variants. In the Prompts dialog box you can select a variant, change its values, or create a new
variant. You can edit the technical name, description, and scope of an existing variant.
To make the menu behavior more predictable, the submenus are expanded by mouse click instead of
mouseover.
Depending on the data source, the application user can now use calculations that are based on dialogs.
The calculation dialogs can be called from the context menu, under the submenu Add dynamic calculation.
Since SAP Lumira 2.x JDBC-based SAP HANA connections are no longer supported, SAP no longer ships the
corresponding BICS provider, so existing data sources in SAP Lumira 1.x customer applications need to be
migrated to use HTTP-based HANA connections instead.
It is not enough to just point affected data sources to a different SAP HANA connection. As part of the
migration, existing initial views of affected data sources need to be modified as well. You can do this in the
property sheet of a data source, using the Exchange Data Source workflow, or it can happen during an import of
an exported 1.x application via the backend connection mapping wizard.
To support customers in these migration tasks SAP Lumira offers a migration tool that automates the tasks.
● Opening a SAP Lumira 1.x application scans it for JDBC-based SAP HANA connections and offers to
migrate the application on the spot.
● A mass migration of SAP Lumira 1.x applications stored on the BI Platform can be launched via the Tools
menu in Lumira Designer.
Some features for developing extensions with the Component SDK have been added or modified.
You can find more detailed information on the features in the Developer Guide: Component SDK.
● Roundtrip Optimization: The application performance is improved by reducing the number of server
roundtrips caused by user interactions.
For more information, see “Roundtrip Optimization” in the Developer Guide: Component SDK on SAP Help
Portal at https://help.sap.com.
● The option loadIncludesOnlyIfVisible defines for a component whether to load the files to be
included with this component when it becomes visible.
For more information, see “Elements” in the Developer Guide: Component SDK on SAP Help Portal at
https://help.sap.com.
● The option valueType indicates the type of the value returned by an SDK data source.
For more information, see “Runtime Property Values” in the Developer Guide: Component SDK on SAP
Help Portal at https://help.sap.com.
You can find more detailed information on the options in the Administrator Guide: SAP Lumira .
To improve the performance of analysis applications, user actions that lead to a roundtrip from the Web
browser to the server and are not needed instantly are queued on the Web browser until there is a user
interaction in the application that triggers a command that is really useful for the application user.
Administrators can influence roundtrip optimization for all analysis applications on the BI platform server by
setting a Java VM argument called ROUNDTRIP_OPTIMIZATION to one of the available values that allow
different degrees of optimization.
Application designers may want to configure the roundtrips between the Web browser and the embedded Web
server of Lumira Designer and set roundtrip optimization for all analysis applications in Lumira Designer to the
same value. They can set a Java VM argument in the SapLumiraDesigner.ini file called
ROUNDTRIP_OPTIMIZATION to the required value. This allows them to simulate the behavior of the
applications when executing them locally in Lumira Designer.
For more information, see the following chapters in the Administrator Guide: SAP Lumira:
With an X.509 certificate, logon to BI platform from Lumira Designer works without providing user credentials.
In SAP Lumira Documents mode and in SAP BusinessObjects BI Platform (Legacy) mode of Lumira Designer,
application designers can now log on to the BI platform using an X.509 certificate that is stored in the Microsoft
Windows certificate store on the local machine.
For more information about the prerequisites and configuration tasks, see “X.509 Certificate-Based Logon to
BI Platform” in the Administrator Guide: SAP Lumira.
You can find more detailed information on the features in the End User: SAP Lumira Discovery.
● If a chart has more than 10,000 data points, the chart will show the first 10,000 data points along with a
message that not all data points are shown. You can retain or change the filter appropriately to view
required data points.
● In this release, the general selection behavior within a chart and the selection behavior in linked analysis
have been enhanced and explained. You can select multiple data points in a chart. For more information,
refer to End User Guide: SAP Lumira Discovery and End User Guide: SAP Lumira Server
3.1.2 Filters
● Filter on Measure: In this release, you can now apply multiple filters on a measure, to filter data based on
certain conditions in a visualization.
● You can now propagate the filters applied on one dataset to another dataset. Filter propagation is
supported only for dimensions that are linked. The propagation of filters will be based on the links created
in the linking dialog. For more information, refer to End User Guide: SAP Lumira Discovery
In this release, you can save defined prompt values as data source variants, such as Variant1 and Variant2, and
reuse them as per your requirements. These variants are used when required to automatically fill prompt
values.
You can create user-specific variants f or public variants that are for all users. When you next open the
document, you can apply your user-specific variants and all public variants. You can also edit a variant by
This section provides a list of new and modified features in SAP Lumira Server. You can find more detailed
information on the features in the End User Guide: SAP Lumira Server.
If you have View rights or have been denied Edit rights, you can make changes to a document by using Design
View and choosing Save As to make a copy of the document to be modified. However, you cannot overwrite the
original document, that is, you cannot save the document with same name as the original document in the
same folder.
● If a chart has more than 10,000 data points, the chart will show the first 10,000 data points along with a
message that not all data points are shown. You can retain or change the filter appropriately to view
required data points.
● In this release, the general selection behavior within a chart and the selection behavior in linked analysis
have been enhanced and explained. You can select multiple data points in a chart. For more information,
refer to End User Guide: SAP Lumira Discovery and End User Guide: SAP Lumira Server
You can now choose to get the latest scheduled document when you open a Lumira document.
For more information, refer to the SAP Lumira Server End User Guide.
Using SAP Lumira Server, you can now refresh the offline data source of a Lumira Designer application.
For more information, refer to the SAP Lumira Server End User Guide.
In this release, you can save defined prompt values as variants, such as Variant1 and Variant2, and reuse them
as per your requirements. These variants are used when required to automatically fill prompt values.
TYou can create user-specific variants or public variants that are for all users. When you next open the
document or query, you can apply your user-specific variants and all public variants. You can also edit a variant
by selecting different prompt values and saving the variant again. You can also delete variants. For more
information, refer to End User Guide: SAP Lumira Server.
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
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.