SAP

Author

Fabien Aubert

Fabien Aubert

Fabien is a product manager in the SAC analytics designer team. Fabien has over 20 years of experience in Business Intelligence, starting back when he worked at Business Objects. More recently, he held roles such as Lumira Product Owner and Design Studio/Lumira Designer Product manager. He is based in Paris and in his spare time he enjoys traveling, hiking and running.

Keep in touch

Subscribe for the latest news, updates, tips and more delivered right to your inbox.

Subscribe to updates

Category

Learning

Connect with us

Analytics designer provides a software development environment that enables application designers or developers to reuse SAP Analytics Cloud widgets and other functionalities to build different kinds of analytic applications.

Interactions between different widgets, pages, and analytic applications are implemented with script functionalities (including planning, machine learning, and so on) – at design time. End users will then be consuming these analytic applications – at runtime.

Analytics Designer is built around core story components to keep them synchronized as you go forward. Analytics designer and Story have different entry points but share much in common:

  • Analytics designer is deeply integrated into SAP Analytics Cloud.
  • Analytics designer and story share data connectivity and User Interface artifacts.
  • It ensures a consistent user experience for application and story consumers.
  • It inherits infrastructure and lifecycle management of SAP Analytics Cloud.

 

Prerequisites

Required Access

Read access: the user of an analytic application needs a read access to open the application at runtime.

Full access: the application author who creates or edits the application needs a Create, Read, Update and Delete access (CRUD). The CRUD permissions are part the standard role Application Creator or can be assigned to any other role.

The folder where the application is stored passes on its access settings. For example, when an application is saved in a public folder, all users get Read access by default.

Required Roles

All standard Business Intelligence roles have a read access to consume analytic applications.

The ability to create, update, and delete is part of an extra standard role Application Creator.

 

Required Licenses

All SAP Analytics Cloud licenses include the creation and consumption of analytic applications. For planning applications, please note the following:

  • If you only need read access to existing planning models and create private versions only, you can use the SAP Analytics Cloud for business intelligence license.
  • If you need to create public versions and use all planning features, the SAP Analytics Cloud for planning, standard edition is required.
  • If you need to create or update a planning model for your planning application, the SAP Analytics Cloud for planning, professional edition license is required. 

Modes

There are three modes in analytic applications:

  • Edit mode This is a design time mode. It allows you to edit applications. CRUD access is necessary. The application opens in edit mode by default if you have CRUD access.
  • Present mode This is a runtime mode. It allows you to execute applications. Read access is necessary. The application opens in present mode by default if you run an it from edit mode.
  • View mode This is a runtime mode. It allows you to execute applications. Read access is necessary. The application opens in view mode by default if you have read access.
Opening a Mode with the URL

A typical application URL looks as follows and contains a mode, for example:

https://xxxx/sap/fpa/ui/tenants/abc123/app.html#,mode=present;view_id=appBuilding;appID=xyz78

In edit mode, the URL contains mode=edit. In present mode, the URL contains mode=present. In view mode, the URL contains mode=view. In embed mode, the URL contains mode=embed. An analytical application opened in embed mode hides the toolbar. The analytic application opens in present mode by default when running the application from the design time.

To change the mode:

  • Modify the URL directly or using the navigation options in the user interface.
  • Click the Fullscreen button in the toolbar. This action changes the URL from mode=present to mode=view.
Switching Between Present and View Mode

You can switch between present and view mode by clicking the Display Fullscreen button in the toolbar. You will notice that the URL will change. Instead of mode=present, the URL contains now mode=view.

Toolbar in Edit Mode

As in Stories there is a toolbar on top of the application which contains the features. Some options are only active once you have saved the application, otherwise they are greyed out.

  • File contains the options like Application Details, Save and Save As, Copy, Duplicate, Paste and Share.
  • For Analytics Designer you have 2 views which are exclusively for applications and ON by default: The Outline and the Info Panel, which contains the error list and the reference list.
  • Insert allows you to insert chart, table and all other available widgets.
  • With Tools you can do chart scaling and create conditional formatting.
  • Data contains refresh data and edit prompts.
  • Designer opens the builder and styling panel.
  • Run Analytics Application opens the application in another browser tab in present mode. Present mode means, that the toolbar is visible only at hover. But it can be toggled to View mode with a static toolbar by clicking on Fullscreen button in the toolbar.
Toolbar in View Mode

In view mode as well as in present mode the toolbar contains a limited set of features.

  • Data allows you to refresh data and edit prompts.
  • Plan contains publish data, version management, version history, value lock management, predictive forecast and allocate values.
  • Display Fullscreen will change the mode to present mode by showing the toolbar only at hover.

 

Designing Elements

For analytic applications there is a strict differentiation between design time and runtime. A few
trained users create applications by using the design time elements, while many end users accessing and navigating the final application only at runtime. The following are the available designing elements.

Canvas

The Canvas is a flexible space where you can explore and present your data. Applications have only one canvas. Scripting allows you to build numerous navigation options in your app.

Widgets and Filters

In Analytics Designer, a Widget is a user interface element that can be inserted and is visible on the canvas.

Filter line widget instead. The Filter line widget mimics the story filter and can be placed on the application canvas. Assign a data bound source widget, such as a table or a chart, as source widget. Target widgets can be assigned via scripting to apply the selected filters to several widgets.

To learn more about widgets, see the related chapter.

Data Sources and Models

In SAP Analytics Cloud, the widgets table, chart and R widget are data bound. They have their own data source, even if the same SAP Analytics Cloud model is connected. There is no shared data source concept. For example, you need to apply filters to each widget when you script in analytics designer for this reason

Managing Your Analytic Application

Transporting an Analytic Application

You can import and export analytic applications from and to other SAP Analytics Cloud tenants. You can choose to export with data and other options.

Note: Custom widgets that are used in an analytic application are also exported with the analytic application.

Note: The software release Wave versions of SAP Analytics Cloud installed on the source and target tenants need to be either the same Wave version or just one Wave version different.

Sharing an Analytic Application

Analytics designer has its own access. As the owner of an analytic application, you can share individual analytic applications with others and grant access to these applications.

Bookmarking Your Analytic Application

Bookmark lets an application user capture the current state of an analytic application after certain operations such as filtering or changing hierarchy level.

Create Bookmark Component

To capture a bookmark of an analytic application, one needs to add a bookmark component at design time. A bookmark version and widgets to be bookmarked can be defined in the side panel of this component.

Save Bookmark

Write analytic designer scripts to save a bookmark. At runtime, the analytic application user can capture the latest application state via API.

BookmarkSet_1.save("application bookmark", true, true);

Translating Your Analytic Application

Translation is useful for multilingual use cases. An analytic application be displayed in different languages in:

  • The text of a widget
  • The widget tooltip if applicable
  • The description of the analytic application

To turn on translation of an analytic application for the first time, the application developer must open the Analytic Application Details dialog and switch on Mark for translation.

The current language will become the source language of this document. If users switch to another language, the document will be shown only in view mode.

Commenting in Your Analytic Application

Besides directly creating or removing comments in an analytic application as in a story, as an application designer, you can add, view, delete comments, and so on, via scripting (available for commenting by data point in planning models only).

Exporting Your Analytic Application to PDF

Analytic Applications allow users to export an application as a PDF file when running the application.

Create an Export to PDF Component

To export an application as a PDF, an Export to PDF component should be added when designing an application.

This was quick overview of the new SAP Analytics Cloud, Analytics Designer capacity. For more information, please see the official SAP Analytics Cloud Help documentation

SAP Analytics Cloud earns a top ranking from BARC

See how SAP Analytics Cloud performed in the world’s largest survey of Business Intelligence software users.