Week 3: Build BI Applications Unit 1 ... - Free SAP Training

Week 3: Build BI Applications

Unit 1: Creating an Application on Offline Data

Sources

2PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Creating an Application on Offline Data SourcesWhat are the takeaways of this unit

▪ Understand the workflow of acquiring offline data sources to build Designer applications

▪ Some considerations regarding Data Refresh


Creating an Application on Offline Data Sources Workflow of acquiring offline data sources for Designer applications

Upload data (CSV, Excel, BW, SAP HANA

etc.) into velocity engine

Blend/merge data

Prepare/manipulate data

Analyst / End User

Consume SAP Lumira document

Use offline data as data sources

Build application

Discovery ServerDesigner


▪ Upload data from Excel, CSV, or imported data from SAP BW,

SAP HANA, SAP Universe, or other systems

▪ Merge, blend, enhance, or manipulate this data using

discovery capabilities

▪ Save as SAP Lumira document with option ‟Save with Data”

Creating an Application on Offline Data Sources Upload data in Discovery client

Upload data

Merge/Blend/Enhance/Manipulate data

Always save with data


▪ Open SAP Lumira document in SAP Lumira Designer

▪ Create application within this SAP Lumira document

▪ Add offline data sources in SAP Lumira Designer

▪ Customize offline data sources by using initial view editor

Creating an Application on Offline Data Sources Reuse data in Designer application

Add offline data sources

Initial view editor


▪ Offline data sources behave like other online data sources (properties, content assistance within scripting

editor, data binding, etc.)

▪ Leverage Designer capabilities to create analytical application or dashboard

Creating an Application on Offline Data Sources Use Designer capability to create application

Example dashboard

based on offline dataset


▪ Offline data sources are contained within a LUMX document. Only applications within the same LUMX

document can share the offline data sources.

▪ Only data source with option “Save with Data” in the Discovery client can be reused in the Designer client

▪ Options to refresh data:

SAP Lumira Designer 2.1 itself has no capability to refresh the data

You can refresh data in the Discovery client or on BI platform with Discovery stories, thus data in the

Designer application will be auto-refreshed

Creating an Application on Offline Data Sources Some facts of using offline data sources

Contact information:

[email protected]

Thank you.

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.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release

any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products,

and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The

information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various

risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements,

and they should not be relied upon in making purchasing decisions.

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.

See http://global.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

© 2017 SAP SE or an SAP affiliate company. All rights reserved.

http://global.sap.com/corporate-en/legal/copyright/index.epx


Unit 2: Creating Designer Applications Based on

Pre-delivered Templates


Creating Designer Applications Based on Pre-delivered TemplatesWhat are the takeaways of this unit?

▪ Overview of templates, ready-to-run application, and samples

▪ Understand the concept/built-in functions of Generic Analysis as the ready-to-run application

▪ Get to know the functionalities that are built in within delivered samples (demo composites and demo

dashboards)


Creating Designer Applications Based on Pre-delivered TemplatesNew document wizard

New Document Wizard:

▪ Start Lumira Designer & create new

document locally or on BIP with the new

document wizard

▪ 3 Categories

– Standard: including blank and other layout

templates

– Ready-to-run: including Generic Analysis

– Samples: including Dashboard Sample

and Feature Samples


Creating Designer Applications Based on Pre-delivered TemplatesGeneric Analysis

▪ Delivered by SAP as standard content

▪ Cover the slice-dice analysis scenario

based on SAP BW/HANA as data sources

▪ Cover the scenario/use case of SAP BEx

Web template

▪ Deployed on BI platform

▪ Enhanced with the new functionalities

− Bookmark

− Export to PDF

− Conditional formatting

− Export to SAP Analysis for Microsoft Office

− Filter line or filter bar option through global

variables

− Chart feeding panel and chart properties

− Flexible layout option through new API

Move Components


Creating Designer Applications Based on Pre-delivered TemplatesBuilt-in functions 1)

Context Menu

Navigation

Panel

Drag & Drop Between Components

Chart/Table

Switch

Filter Line/ Filter Bar, Configurable at Design TimeLayout

Options



Application InfoBookmark Dialog

Export to PDF Dialog

Bookmark


Design Panel

▪ Navigation

Panel

▪ Chart Type

Picker

▪ Feeding

Configurator

▪ Chart

Formatting

Chart Property Editor

Chart Feeding

Panel

Chart

Type

Picker

Runtime Chart

Configuration

Options

Basic Chart

Combination Chart



Creating Designer Applications Based on Pre-delivered TemplatesExport options

Export to PDF in Report Style

Export to SAP Analysis for Microsoft Office

Export to Microsoft Excel


Creating Designer Applications Based on Pre-delivered TemplatesBookmark dialog

Bookmark

▪ Capture the state of chart, table, filter

bar/filter line, application header, favorite list

▪ Type: Global and Personal

▪ Add, open, and delete selected bookmark

▪ Move selected bookmark to another folder

▪ Add selected bookmark to favorite list

▪ Set selected bookmark as default

▪ Share selected bookmark via URL

or email

▪ Sort bookmarks

▪ Display bookmarks as tree structure

▪ Bookmark Information


Creating Designer Applications Based on Pre-delivered TemplatesDemo composites

Demo Composites

▪ Can be used like any other components

▪ Visible in Components view

▪ Includes:

– Application header

– Cards/tiles

– Comments panel

– Comments dialog

– Export to PDF dialog

– Bookmark dialog

– Related applications


Creating Designer Applications Based on Pre-delivered TemplatesDemo applications

Demo Applications

▪ Contained within one LUMX document

▪ Based on offline data sources

▪ Includes:

– SAP_Demo_City_Analysis_Simple

▫ Tiles, maps, and their interaction

▫ Commentary feature

– SAP_Demo_City_Analysis:



▫ Dynamic creation of charts

– SAP_Demo_City_Analysis_Advanced



▫ Dynamic creation of composites

SAP_Demo_City_Analysis Simple

SAP_Demo_City_Analysis

SAP_Demo_City_Analysis_Advanced


[email protected]

Thank you.


Unit 3: Optimizing Applications and Dashboards with

Reusable Components


Optimizing Applications and Dashboards with Reusable ComponentsWhat are the takeaways of this unit?

▪ Understand for which scenario composites can be used

▪ Benefit of composites

▪ What the key steps are in creating composites

▪ How to consume composites in applications

▪ Best practices around composites


Optimizing Applications and Dashboards with Reusable ComponentsOverview

Composites

▪ Designers can create own components without

sophisticated JavaScript programming, similar to

app development (formatting by drag & drop of

standard components, logic definition by data

binding and scripting)

▪ Based on a clean interface concept

▪ Usable like any other standard component:

properties, methods, events (interface)

▪ Re-usable across applications, stored on the

BI platform

▪ Used to define global components (header,

footer, toolbar, global script pool)

▪ Used to decompose complex applications into

smaller, better manageable parts

Composite: Header

Composite:

Bookmark DialogComposite: KPI Tile

Composite:

PDF Dialog


▪ Composites are only supported in SAP Lumira Documents mode in SAP Lumira Designer

▪ Applications can use composites from the same document and other documents. To use composites from

another document, the referenced document must already exist. Therefore, dependent documents need to

be considered during transportation of objects (promotion), for example.

▪ One composite can be part of multiple applications. One application can contain multiple composites.

Composites cannot contain other composites.

Optimizing Applications and Dashboards with Reusable ComponentsYou need to know


Composites behave like standard components as

they can have the following interface elements:

▪ Properties

like the Text property of Text component

▪ Functions

like the setText method of the Button component

▪ Events

like the onClick event of the Button component

Optimizing Applications and Dashboards with Reusable ComponentsProperties, events, and functions


Optimizing Applications and Dashboards with Reusable Components How to create a composite

You work in SAP Lumira Documents mode in SAP Lumira

Designer

You have created a local or remote document for which you want

to create a composite

▪ In the Documents view of the design tool, right-click a document in the

Local or Remote Documents folder and choose Create Composite...

▪ The New Composite dialog box appears

▪ Enter a name for the composite

and choose Create

▪ Now you can start editing the

composite


▪ Editing composites works the same way as

editing applications

▪ You can start editing your composite by

– adding components from the Components view

– adding data sources in the Outline view or from

the menu bar

– setting properties in the Properties view

– adding an interface with properties, events,

and functions in the Outline view

– adding global variables in the Outline view

– adding technical components in the Outline

view

▪ After editing your composite, save your work by

choosing File → Save in the menu or by clicking

the Save symbol

Optimizing Applications and Dashboards with Reusable ComponentsHow to edit a composite


Optimizing Applications and Dashboards with Reusable ComponentsCopy & Paste composites

Simplified Usage of Composites

▪ Much more convenient to create or modify composites

through copy & paste

▪ Possible to change the reference of composites for


▪ Composites are visible in the Components

view, as other standard SAP components

▪ Add composites to the application from the

Components view, Documents view, or

Outline view

▪ Interface properties, events, functions etc.

can be edited in applications

Optimizing Applications and Dashboards with Reusable ComponentsHow to consume composites in applications


Bring the composite on the BI platform

▪ You can upload local documents to BI platform

– You can map the back-end system after you

have uploaded the document to BI platform

– Only self-contained documents can be uploaded

to BI platform

▪ Remote Documents node allows to synchronize

(the complete document) with BI platform using the

context menu

Optimizing Applications and Dashboards with Reusable ComponentsComposites on BI platform


Depends on the scenario:

▪ Decompose complex applications into several composites

– Composites and the related application should be contained in the same LUMX document for better

transportation/organization

– If more than one person is working on different composites, then composites can be contained in different

LUMX documents for better authorization check (who can edit which parts)

▪ Reuse composites in multiple applications

– Applications and composites should be contained in a different LUMX document. Composites can be

contained in a separate LUMX file and can be reused in other applications

Optimizing Applications and Dashboards with Reusable ComponentsBest practices for composites


[email protected]

Thank you.


Unit 4: Adaptive Layout


SAP Lumira 2.0 Adaptive LayoutWhat are the takeaways of this unit?

▪ Get to know what is Adaptive Layout and the benefit

▪ How to define a Adaptive Layout

▪ How to use API “move components” to switch to different layout at application runtime


SAP Lumira 2.0 Adaptive LayoutOverview

Adaptive Layout

▪ New container supports different layouts for

small, medium, large and extra large screen sizes

▪ Ability to fully customize and optimize layout per

device using new script methods

Desktop Deployment Tablet Deployment Mobile Phone Deployment


Adaptive LayoutLumira 2.0 delivers a responsive layout with 2 concepts

Grid Layout

▪ Default Layout for Discovery & Designer

▪ Content position retained to maintain relation between components by scaling content within available real

estate

Adaptive Layout

▪ Configuration available only for Designer (Planned for Discovery in Future release)

▪ Content position is moved to maintain minimum size for visualization depending on available real estate


Adaptive LayoutOverview

The Adaptive Layout Container provides the possibility to create an responsive layout that can be

viewed on multiple devices.

e.g.

– Desktop

– Tablet

– Smart Phone


Adaptive LayoutViewport

The Adaptive Layout contains a series of

blocks, which have a defined colspan per

viewport.

What is a viewport?

▪ Available at design time

▪ A visible area of an Adaptive Layout

container.

▪ Size can be changed depends on the width

of the Adaptive Layout container.

▪ Can be manually set by context menu

largemedium

small

Extra large


The Adaptive Layout contains a series of blocks, which have a defined colspan per viewport.

The Adaptive Layout has always 12 colspan per row.

Adaptive LayoutColspan

If the 12 colspan

are full in a row,

the Adaptive

Layout component

will push blocks

underneath.

121110987654321

The spacing

set the vertical

and horizontal

spacing

between

blocks.

The viewport

will change

size

depending on

the width of

the Adaptive

Layout

container.


Adaptive LayoutBlocks

The Adaptive Layout contains a series of blocks, which have a defined colspan per viewport.

The Adaptive

Layout contains

a series of

blocks, which

have a defined

colspan per

viewport.

You can add

components into

these blocks to

build up an

application.

The Adaptive Layout

rearranges blocks,

according to the colspan

of the blocks and the

current viewport.

While designing your

application, define

the colspan of each

block for each

viewport.


Adaptive LayoutBlocks and colspans

▪ The component you drop onto the block

takes the height of existing blocks on

that row. If the 12 blocks are full in a

row, the Adaptive Layout component

will push blocks underneath.

▪ If you resize a block, only that block is

resized. The container will look at the

blocks in order and add them next to

each other. If a block requires a 13th

column, a new row will be added.


Adaptive LayoutDynamic layout at application runtime

▪ API APPLICATION.getUserAgent() returns the

current device (e.g. iPad, iPhone etc.)

▪ API move components can move the components

into different container components(Panel, Grid,

Pagebook etc.) at application runtime.

Move Map, Charts

to Pagebook

Desktop Layout

iPad

Layout


▪ With combination of the script getUserAgent and moveComponent, you have now the possibility

to define different layouts without duplicate the components.

Adaptive LayoutAdditional options via script getUserAgent & moveComponent

DESKTOP is the

default layout

MOBILE is the

special layout for

smart phone

All on

one page

Shows only the orange

& green tiles, no blue

tiles

Use the pagebook to

slide between the

green tiles


[email protected]

Thank you.


Unit 5: SAP Lumira Bookmark Concept


SAP Lumira Bookmark ConceptWhat are the takeaways of this unit?

▪ What is a bookmark?

▪ Comparison between bookmark concept of Design Studio 1.6 and Lumira 2.1

▪ New capabilities of Lumira 2.1 bookmark concept

▪ Some considerations regarding migration


SAP Lumira Bookmark ConceptWhat is a bookmark?

▪ Capture and save your personalized

view of your dashboard

▪ Find, filter, and load saved navigational

states of analytical data

▪ Share your saved view with other users

▪ Leverage BI platform permissions and

roles to control data access


SAP Lumira Bookmark ConceptDesign Studio 1.X bookmarks

Standard

▪ Capture a full snapshot of an application state

▪ Are dependant on application version

▪ Sharable via URL

Personalization

▪ Capture a full snapshot of an application state

▪ Personalized view loads on startup of a dashboard

▪ Only one personalized bookmark per user, per application

Fragment

▪ Capture a selected part of the application

▪ Are not dependant on application version


Portable Fragment

▪ Capture a selected part of the application

▪ Are not dependant on application version

▪ Transportable to other Design Studio dashboards


SAP Design Studio 1.2+ SAP Design Studio 1.4+


SAP Lumira Bookmark ConceptRestrictions of Design Studio 1.x bookmark concept

▪ It was not possible to bookmark just a data source (or any specific thing)

– The Standard and Personalization bookmarks bookmarked the whole app

– The Fragment and Portable Fragment bookmarks bookmarked an entire panel

▪ Any change to an app – even just correcting a text typo – invalidated all standard bookmarks and

personalization

▪ Any change to the container associated with a Fragment or Portable Fragment bookmark – even just

correcting a text typo – invalidates it

▪ Promotion was not possible with 1.x bookmarks


SAP Lumira Bookmark ConceptOverview

Reworked Bookmark Concept

▪ Designer configures what is captured in a

bookmark (e.g. selection of data sources,

global script variables, components)

▪ Increasing robustness of bookmarks

against application UI changes

▪ Bookmark configuration as a technical

component in design time

▪ Multiple bookmarks can be defined within

one application

▪ Promotion Management support of

bookmarks and folders

▪ Personal and global bookmarks are

supported


SAP Lumira Bookmark ConceptExample: Bookmark within Generic Analysis application

A good example of end-to-end usage of

bookmarking scenarios and features can be

found in the Generic Analysis applications.

▪ The user can save bookmarks for both

personal use and sharing

▪ The user can choose the folders that they are

stored on

▪ The user can consume bookmarks created by

themselves and (global) bookmarks created by

others

▪ The user can delete bookmarks


SAP Lumira Bookmark ConceptSome considerations regarding migration

▪ 1.6 bookmarks can’t be migrated to SAP Lumira 2.x bookmarks.

▪ 1.6 bookmarks (with 1.6 application format) can still run within the Local mode and SAP BI Platform mode

within SAP Lumira 2.x

▪ Once 1.x applications are migrated to SAP Lumira 2.x documents, then 1.x bookmarks are no longer valid.

You need to create bookmarks by using the SAP Lumira 2.x bookmark concept

▪ Details please refer to note https://launchpad.support.sap.com/#/notes/2538142

https://launchpad.support.sap.com/#/notes/2538142


[email protected]

Thank you.


Unit 6: Sharing Applications with

SAP BusinessObjects BI Platform


Sharing Applications with SAP BusinessObjects BI PlatformWhat are the takeaways of this unit?

▪ SAP Lumira documents LUMX format

▪ Local document vs. document on BI Platform

▪ Start SAP Lumira document vs. Start SAP Lumira application

▪ Download Lumira document from BI Platform to local area

▪ Upload local document on PC to BI Platform


Sharing Applications with SAP BusinessObjects BI PlatformCommon LUMX format for Discovery & Designer

Discovery

▪ Only opens stories of a Lumira document in edit mode

▪ Designer composites will be visible in Discovery,

excluding SDK custom components

Designer

▪ Discovery stories show as composites

▪ SAP Lumira documents mode for 2.x

▪ Documents are greyed out until you open them

App

Composite/Story


Sharing Applications with SAP BusinessObjects BI PlatformWorking with BI platform from Designer

▪ You can work with BI platform or local documents in

parallel if you start your Designer with SAP Lumira

documents mode on BI Platform

– Note: BI Platform documents are a local copy and

need to be synchronized with the BI platform to

update the original application!

▪ Local document can be uploaded to BI platform with

current limitations

– All composites must be contained within the same

LUMX file

– Back-end connections need to be adjusted after

upload to BI platform (only valid for SAP Lumira 2.0. With

SAP Lumira 2.1, this limitation has been removed)

– We recommend you to work directly on BI platform

to avoid the effort of adjustment later on

This is the current state of planning and may be changed by SAP at any time.


Sharing Applications with SAP BusinessObjects BI PlatformExecute documents and applications on BI platform and locally in SAP Lumira documents mode

Execute Document on BI Platform

▪ Executes default application (Discovery or

Designer app) of the Lumira document located

on BI platform – not the local copy

▪ Use URL parameter “&APP_TO_LAUNCH” to

start non-default applications on BI platform

Execute App on BI Platform

▪ Executes the opened app of the Lumira

document located on BI platform, not the local

copy or default app

▪ If the app doesn’t exist, an error occurs

Execute Locally

▪ Executes default app / opened app of the local copy of your BI platform document


[email protected]

Thank you.


Unit 7: Dynamic Creation of Components


Dynamic Creation of ComponentsWhat are the takeaways of this unit

▪ Understand the benefits of creating/deleting components at application run-time

▪ Get to know the overview concept of this functionality

▪ Tips and Tricks


Dynamic Creation of ComponentsScenarios/benefits

▪ No need to pre-define the number of

components/composites at application design time.

▪ Components/composites can be generated/deleted

at application runtime based on the result set.

▪ Typical Scenario: KPI Dashboard

– End user can add the KPI Tile at application

runtime

– Application layout will be adjusted accordingly


Dynamic Creation of ComponentsTechnical overview

Dynamic components/composites creation at runtime

▪ Create Components dynamically at runtime based

on the selection

▪ Copy property settings from one component to

another

Result Set Iteration

▪ Iterate through all cells in a result set of a data

source query

Other

▪ Copy all variable values from one data source to

another (or an array of other) data sources

▪ Dynamic creation and modification of property

binding Based on the selection of map, the composites are

generated at runtime


Dynamic Creation of ComponentsTechnical component

Technical Component

▪ COMPONENTS needs to be defined as the

technical component

Related API

▪ Create new components to any container in the

application at runtime

▪ Delete components from an application at runtime

▪ Add data sources to an application at runtime and

bind it


Dynamic Creation of ComponentsExamples

Lumira Designer 2.1 installation contains examples of

applications with dynamically generated components.

▪ SAP_DEMO_CITY_ANALYSIS

▪ SAP_DEMO_CITY_ANALYSIS_ADVANCED

Funciton „generateComponents“

var selections = DS_AGEGROUP.getDataSelections({"DS:15,DIM:id_48":"*"});

selections.forEach(function(selection, index) {

var block = COMPONENTS.createComponent(ComponentType.Block,

g_CreatedContainer);

COMPONENTS.copyProperties(BLOCK_COPY, block);

var chart =

COMPONENTS.createComponent(ComponentType.com_sap_ip_bi_VizFrame, block);

COMPONENTS.copyProperties(CHART_COPY, chart);

chart.setDataSource(DS_AGEGROUP);

chart.setDataSelection(selection);

});


Dynamic Creation of ComponentsTips and tricks

▪ You can create composites, as well as components.

– Demo Example SAP_DEMO_CITY_ANALYSIS_ADVANCED shows the usage of composites

– Demo Example SAP_DEMO_CITY_ANALYSIS shows the usage of charts

– Generated Composites must reside in the same document as the application.

▪ There is a new data source method for getting complex data selections “getDataSelections()”

– It can be used to create a list of selections, each filtered to a particular dimension member.

– SAP_DEMO_CITY_ANALYSIS and SAP_DEMO_CITY_ANALYSIS_ADVANCED both use this, getDataSelections() gets

a list of selections by neighborhood, and the charts are then generated per neighborhood. You can use JSON string with

* to get the complete result set including totals, with ? to get the result set exclude totals.

▪ Not all properties are exposed to the script API.

– Which means if you want specific values on these properties, you will need a template component of the same type

already in the application, from which you can copy your properties

▪ The cells inside the grid layout are not selectable via script.

– This means that you can’t select them to add content dynamically. Please consider using the adaptive layout, instead.


[email protected]

Thank you.


Unit 8: Commentaries


CommentariesWhat are the takeaways of this unit?

▪ Understand the commentary scenarios that SAP Lumira 2.1 covers

▪ Get to know the features and functions of commentary

▪ Learn some facts


CommentariesOverview

Comments in Designer only

▪ Application-based commentary and data

context / data cell-based commentary are both

supported

▪ Private commentary and public commentary

▪ Integrated with commenting infrastructure on BI

platform

▪ Comment as new technical component


CommentariesTechnical component

▪ COMMENTS as technical component needs to

be added in the application design time

▪ The functionality provided by Comments allows

users to create/delete/modify comments in SAP

Lumira applications

▪ Comments across all applications within one

SAP Lumira document (.lumx file) can be

shared using the BI Commentary service on the

BI platform

▪ Comments can be created in local mode for

testing purposes, but NOT using the BI

Commentary service on the BI platform in this

case


CommentariesComments types

▪ Different Comments Types:

▪ For the entire application

▪ For the applied filters of a specific list of

dimensions

▪ For a cell in a query: create comments on

specific data cells

▪ For a dimension: create comments on a

specific dimension

▪ For a dimension member: create

comments on a specific dimension

member

1

2

3

4

5

1

2

345

Sample application with header, filter bar, and table; comments enabled at

different levels


CommentariesCreate comments

Using API “Comments.create”

▪ content (String)

▪ context: as string, JSON object, or from context

menu selection of a crosstab

▪ contextType: DATA, MEMBER, DIMENSION,

CONTEXT and NONE.

▪ dataSource

▪ isPublic


CommentariesCreate comments: context

▪ You can create a context for use in creating or

querying in the following ways:

▪ as a JSON object

▪ as a string

▪ from crosstab / context menu selection

▪ from crosstab / context menu selection with

background filters

2

3 4 5

12

345

2

3 4 5

2 2

1

3

3 4 5


CommentariesUpdate/delete/query comments

Update commentary

▪ Only content can be updated based on the

comment ID

Delete commentary

▪ Only content can be deleted based on the

comment ID

Query commentary

▪ Get comments for all applications within one

LUMX document

▪ Get comments by ID

▪ Get a filtered list of comments

Update Comments

Delete Comments


CommentariesDisplay comments

Display comments e.g. with dialog or panel

▪ You can use FEED LIST as component

Display comments in crosstab

▪ You need to set “Comments Visible” property

to true

Export comments with PDF file

▪ Set “Comments Visible” property within

technical component definition to true

▪ Application or data context-based

commentary is exported with PDF file, but

crosstab-based commentary cannot be

exported


CommentariesSome facts

▪ The public and private setting is purely a filtering mechanism for SAP Lumira users, and is not linked to

any rights on the platform

▪ Users who have rights to delete comments can delete both private and public comments

▪ SAP Lumira users can create comments for SAP Lumira applications and share those comments across

all applications only in the same SAP Lumira document (.lumx file)


[email protected]

Thank you.


Unit 9: Converting Design Studio 1.6 Applications

to SAP Lumira 2.x Documents


Converting Design Studio 1.6 Applications to SAP Lumira 2.x DocumentsWhat are the takeaways of this unit?

▪ Understand different conversion options/scenarios

▪ Get to know the workflow of conversion

▪ Learn about the side-effects after conversion


Converting Design Studio 1.6 Applications to SAP Lumira 2.x DocumentsOverview

Keep existing applications in 1.6 format (.biapp)*,

edit, save, & run applications in a compatibility

mode. Based either on SAPUI5.commons or

SAPUI5.m library. No new 2.0 features available,

no interoperability with DiscoverySystem

Upgrade

Design Studio 1.6 SAP Lumira 2.0

Option 1: Keep*

/Legacy Mode

Edit & Save

Applications in 2.0 format (.lumx). Based entirely

on SAPUI5.m library. Make use of new 2.0

features. Interoperability with Discovery

Option 2: Create

New / SAP Lumira

Documents Mode

Application Conversion

* Applications still using legacy SAP HANA JDBC connections need adaptations, and

their bookmarks will become invalid. Refer to SAP Note 2475223 for details

https://i7p.wdf.sap.corp/sap/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3234373532323326


Converting Design Studio 1.6 Applications to SAP Lumira 2.x DocumentsConversion main steps

1. Perform a conversion into m mode on

the BI platform or local modes of Lumira

Designer (the legacy/compatible

modes). This is the main part of the 2.x

conversion.

2. Export the application (still in the

legacy/compatible modes of Designer)

3. Re-start Lumira Designer in SAP Lumira

Documents mode and import the export

file from step 2 in a new or existing SAP

Lumira document

1

2

3


Converting Design Studio 1.6 Applications to SAP Lumira 2.x DocumentsExpected adjustment after conversion

▪ Update the stylesheet: SAPUI5 m library uses different style classes to SAPUI5 commons library. If you want

to emulate SAPUI5 commons library styles in converted applications to minimize layout adjustments, please

refer to blog: https://blogs.sap.com/2017/11/03/design-studio-fix-layout-after-migration-to-sapui5-m-mode/

▪ Control the layout (size and position) of components (adjustments may be required)

▪ Control converted charts. Most of the chart properties are automatically converted. There are some

exceptions. Please refer to SAP Note 2538142

▪ 1.x bookmarks and scripts work with SAP Lumira 2.0 legacy/compatible mode, but after application

conversion to LUMX format, they are no longer valid. You need to re-create those bookmarks using the

SAP Lumira 2.x bookmark framework

▪ The Split Cell Container and the Fragment Gallery components and their relate templates "Data Discovery

and Visualization" and "Online Composition“ are no longer available in Lumira Designer 2.x. With

SAP Lumira 2.x, these self-service-related use cases are covered by Lumira Discovery

▪ The old APPLICATION.export() script function has been deprecated. Existing scripts related to this function

still work after conversion to 2.x. However, this function will not show up in the 2.x script editor. New export

functionality in an application should be added using the new Export CSV, Export Excel, and Export PDF

technical components

https://blogs.sap.com/2017/11/03/design-studio-fix-layout-after-migration-to-sapui5-m-mode/



Converting Design Studio 1.6 Applications to SAP Lumira 2.x DocumentsRelated important links

▪ Design Studio 1.6 to SAP Lumira 2.x Conversion Note: 2538142

▪ Documentation about conversion topic:

https://help.sap.com/viewer/4f58d91f03e441b68d3187e94be27df2/2.1.0.0/en-

US/7502343ec1d444748d4a38040199223b.html

▪ Lumira Designer 2.0 – HANA Connections through HTP/InA Provider – usage restrictions: 2512478

▪ Lumira 2.0 Release note: 2462799

▪ Adjust custom style sheet: https://blogs.sap.com/2017/11/03/design-studio-fix-layout-after-migration-to-

sapui5-m-mode/

▪ Automatic Migration of SDK extensions: https://blogs.sap.com/2018/01/09/automatic-migration-of-design-

studio-1.x-sdk-extensions-to-lumira-designer-2.x/


https://help.sap.com/viewer/4f58d91f03e441b68d3187e94be27df2/2.1.0.0/en-US/7502343ec1d444748d4a38040199223b.html



https://blogs.sap.com/2017/11/03/design-studio-fix-layout-after-migration-to-sapui5-m-mode/

https://blogs.sap.com/2018/01/09/automatic-migration-of-design-studio-1.x-sdk-extensions-to-lumira-designer-2.x/


[email protected]

Thank you.

Week 3: Build BI Applications Unit 1 ... - Free SAP Training

Documents

Transcript of Week 3: Build BI Applications Unit 1 ... - Free SAP Training