nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Get Probability of Event with ProbabilityModel (scriptedProbabilityModel) at Birt Report

medini_1051428514

Hi,

At the Birt Report, I am trying to reach the probability value of events which has scriptedProbabilityModel (js).

Previous tries show:

- in scripting environment, I can see the numerical probability at console view, by

console.log(event.probability)

- in the birt report environment, "event.probability" returns "NaN" for the events with javascript probability model (scriptedProbabilityModel)

When I check the class of the NaN value, it gives de.ikv.medini.util.core.MediniNumberUtil$1

How to reach the numerical probability value of the events with scriptedProbabilityModel? If possible, could you give an example code snippet?

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024169437

Hi Ayhan,

I think that's not a problem of the BIRT report design, I assume you have something like this when you switched to custom probability using JS:

So basically NaN as the probability. I figured out that the function exp is actually not defined in the global scope but only in Math so the default script is false.

If you have now any sysml element with a failure rate (lambda) associated to the event, and fixed the JS expression, it works:

Happy Reporting

Jan

All comments

medini_1024169437

Hi Ayhan,

I think that's not a problem of the BIRT report design, I assume you have something like this when you switched to custom probability using JS:

So basically NaN as the probability. I figured out that the function exp is actually not defined in the global scope but only in Math so the default script is false.

If you have now any sysml element with a failure rate (lambda) associated to the event, and fixed the JS expression, it works:

Happy Reporting

Jan

medini_1051428514

Hi Jan,

Yes, the script was including something invalid in global scope:

I was using directly references to the corresponding failure mode's custom profile value:

event.represents. ... .user_dangerous_undetected

Now, I am using the getProfilePropertyValue to get the profile value:

event.represents. ... .getProfilePropertyValue("user_dangerous_undetected")

which is valid in global scope.

Thank you Jan.

medini_1024169437

Ayhan,

are you sure this is the right thread for this answer? There should be no difference between those two calls ...

Happy Scripting

Jan

medini_1051428514

Yes, if I am not wrong, they behave differently when reporting (version 2020R2), unlike scripting at ui.

Here is an example project. A example report is available in config/report.

I have created a custom profile "user_dangerous_undetected" for FMEA failure entry, which is derived from a system model component failure mode which is represented
by the FTA event.

medini_1024169437

Ah, right, I almost forgot that we are in the reporting forum, not the scripting one, haha.

BIRT comes with its own JS engine 8actually the same) but it has not our API extensions in it so from there you can't access profile props directly, true.

Jan