Camelot-MC_white logo

SAP Analytics Cloud, Analytics Designer: Overview and Performance Optimization

Reading Time: 2 Min.

Share

A contemporary analytics ecosystem includes visualizations and storytelling, as well as insight sharing and predictive technologies. These features assist companies in managing today’s more unpredictable environment. The Analytics Designer is the key to customizing data-driven decision-making experiences for many SAP customers.

SAP’s Tailored Analytics Strategy

SAP gives users the option to implement Analytic Applications in varying levels of detail thanks to Analytics Designer. From simple dashboards to fully customizable and interactive analytical interfaces. Graphic elements can be modified and influenced with scripting; however, this requires more technical expertise and knowledge.

 Elements and widgets of the Analytic Application
Figure 1: Elements and widgets of the Analytic Application

 

If you are familiar with Analytics Designer positioning within the SAP portfolio, you may already know that it provides a JavaScript coding environment for developing and designing more sophisticated applications, including planning and predictive applications, in comparison to simple Stories alone.

Besides, the requirements imposed by a holistic corporate management are well reflected in the features of the Analytic Designer; Dashboards can be shared and viewed on mobile devices, the Digital Boardroom or in the Analytics Hub.

Data-driven dashboards have evolved from basic reporting objects to complex decision-making tools. Real-world dashboard designers are always striving for a combination of dynamic interactions, data granularity, and rapid performance that keeps users interested.

The Benefits of Debugging Analytics Designer Script

The purpose of debugging is not only to find out where the problems are occurring, but also to make tiny changes by finding out if a particular piece of code will work. While the code is being executed, you may also evaluate various variables simultaneously.

In most coding environments, Design Time Errors prevent the code from running. On the other hand, Runtime Errors may or may not crash your application.

Debugging in the browser
Figure 2: Debugging in the browser

 

While debugging the code, developers can not only identify potential issues but also determine the appropriate APIs.

Please refer to the current API reference manual from SAP.

What about Performance?

There is no doubt that performance is one of the most challenging aspects to combat. The end user’s performance is the result of many different factors. Some performance-related components are

  1. the end-user device’s power (laptop vs smartphone),
  2. Browser choice (SAP suggests using Google Chrome. Chrome’s developer tools are another benefit, since they are essential in this case to understand what is going on with our performance and the runtime)
  3. the end-user’s network connection to the SAC,
  4. the script logic and application design (for example, a large number of widgets and artifacts will limit the speed of the data transfer, and the runtime will most certainly degrade),
  5. linking your source system(s) to SAC and the chosen settings.

Before You Start Building Your Own Application…

1. Recognize your end consumers’ expectations

In certain circumstances, a performance speed of less than a minute may be acceptable, while in others, fewer than 10 seconds may be required.

2. Examine your customers’ navigation patterns

Specific functionality may be required only by a relatively small number of users.

3. Know the tools used to examine the modifications made in an application

How will you determine if you made a positive or a negative change?

4. Consider general performance guidelines

Despite being separate artifacts, the Story and Application follow the same performance optimization guidelines because they use the same runtime. In the end, the advice given may not necessarily lead to a highly efficient optimization, it all depends on the specific situation or the use case at hand.

The changes appearing to have the largest effect on performance optimization sometimes turn out to be a fallacy.

Technology is constantly changing but understanding why recommendations are made makes it easier to keep up with changes and guess whether new capabilities will enhance overall performance or not.

In the end, it doesn’t matter how nicely designed the dashboards are if the backend isn’t well structured, the dashboards won’t be able to handle the load and vice versa.

Latest Blog Posts