cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

PROFILING ScriptInterpreter: Validate Script

Former Member
0 Likes
661

Hi,

I am trying to improve performance in our current dashboard.

The option PROFILING=X is really helpful.

Now I find very often the step ScriptInterpreter: Validate Script.

The script TX_PROD.OnClick() only contains some lines, but is calling other scripts.

In each navigation step (in the dashboard) this script validation takes between 500ms and 2000ms.

What is this step exactly doing?

How can the time for this step be reduced?

Are there some specific settings in the dashboard, that I miss?

Some specs:

Design Studio 1.5 (SP0)

Dashboard is running on BO Platform

Connection to SAP BW 7.3

Some explanations and tips/tricks are very welcome.

Regards

Steve

Accepted Solutions (0)

Answers (3)

Answers (3)

0 Likes

Hello,

I have the same annoying problem:(

Former Member
0 Likes

Hello,

just to bring this topic up again.

Are there any news about this script validation?

At the moment there are always a lot of seconds spent in validating the script each time a dashboard is started or some action (script) is started.

Is there an option to store an already validated version of the dashboard?

Any parameters to influence this behaviours?

Many thanks for your input.

Regards

Steve

Former Member
0 Likes

Hi Steve

I hope you would have gone through these important links relating to profiling, for your reference -

Apart this ,Could you share the scripts that you have written in the onClick event of the button.

Thanks

Former Member
0 Likes

Hi,

I read and applied (if possible) the first blog.

The second link I will study now.

The .onClick script is pretty simple:

navDetailType = "time";     //indicates the selected navigation   Time --> display charts

navTimeType = "mnt";       // --> display periodic values

SCRIPT_MENU.onDetailTypeSelect(navDetailType);

The script SCRIPT_MENU.onDetailTypeSelect sets visibility and CSS classes of different items depending on the navDetailType. (some if/elseif)

TXTxxx.setVisible(xxx)          //some text elements

PANELxxx.setVisible(xxx)     //some panels to show or hide crosstab or charts

TXTxxx.setCSSClass(xxx)     //indicates 'buttons' as (not) selected

For my understanding it is not too complex.

Regards

Steve