Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
A while back I set myself the challenge of building an Analytic App that brought together
a number of scripting elements; primarily as an exercise in understanding script interactions
and chains of events.

As you start creating ever more complex Apps for customers, you quickly realise that
each script / function in isolation is fairly easy to develop.

However things rapidly get more complicated when you have to string everything together, pre-empt
user journey's & interactions within the app and consider timings - e.g. data loading/filtering and so on.

Elements I wanted to use included:

-  Timers
-  Arrays
-  Script Functions
-  Variables
-  Layout & Relative position settings
-  Dynamic visibility

The outcome of the exercise was this:

The finished App consists of circa:

43 panels
28 script variables
24 script functions
45 shapes
11 timers


I guess the real point this highlights is that when scoping and designing an Analytic Application with a customer, the initial ask may appear fairly simple.

It's not until you start coding and working through inputs and outcomes of each block of code that the simple looking end result belies the complexity required to achieve this.


An exercise like this has really helped me to better estimate the development time required for an Analytic Application, which in turn results in a more realistic project plan and ultimately a happier customer.


If there any specific bits of code you'd like me to share, please comment below
(there's too much to put it all in a single blog post)


As always help from the SAP community can be found here:
SAP Analytics Cloud Designer Q&A


Blog part 2 is here:  High level code overview
Labels in this area