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; } } }

Analyze Traces in a Report

medini_1050222804

Hello,

I try to build a report for our functional safety concept.

To get a good traceability I create a link between a safetygoal and the malfunction or failure which leads to violation of the goal.

By creating the safety report I try to analyze this very trace, but the "Computed Column" which trys to geht the traced elements by @self.getObject().mediniGetTracedElements(Metamodel.safetyModel.Malfunction).get(0); breaks at execution. So I think it´s not possible to use this function in BIRT reporting. Is there any other way to get traced elements and save it as entry in a Data Set?

Sincerely

Jakob Kein

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024169437

Jakob,

difficult to say, but please check this article, last statements: https://medini.freshdesk.com/support/discussions/topics/1000092094

If you use OCL data sets you must ensure that caching s disabled, otherwise you get strange exceptions during reporting.

Jan

All comments

medini_1024169437

Hello Jakob,

do you have more details on "breaks at execution"? Which error do you get?

I assume that "Metamodel" is no present in BIRT Java Script. It depends on the medini version you use, we stepwise align BIRT scripting with

our own profiling and Metamodel was something introduced in 19.4 (aka 2019 R2).

An alternative is described in https://medini.freshdesk.com/support/discussions/topics/1000092412 - it somewhat explains that

you can put all the traversal and scripting into a derived property in medini in limit the computed column to just access that derived

property.

Jan

medini_1050222804

I use Medini Version 19.2.

This is the Computed Column I´m trying to integrate for example:

This results in this exception:

In another post I saw you doing an OCL-Query which results in a whole sequence of the traced elements, but I didn´t understand how to implement this.

This was your example for some System Design Elements:

medini_1024169437

Hello Jakob,

yeah, 19.2 is "too old", Metamodel is not available in BIRT Scripting in that version. You have to switch to 19.4.

Hm, the other OCL snippet has a different background I think. Idea is to filter already in the OCL query. Since BIRt does ot care whether a queyr returns a single objec or a colelction of objects I simply "misused" (or just used) the Collection API to filter a single object (the self). To do so I converted it to a Sequence, hen used the nice "select" operation.

Jan

medini_1050222804

Okay, I understand:

Is there any way to do it like in the thread you sent?

I understand the process, but I don´t know how to implement a derived profile property which returns all traced malfunctions, like:

var size = self.mediniGetTracedElements(Metamodel.safetyModel.Malfunction).size();

var Malfunctions = [];

for(var i = 0; i < size; i++){

//Save all objects of type malfunction which are traced to the SafetyGoalg

}

//Derived Proifle Property = Set of found malfunctions

medini_1050222804

I would be glad if you could provide a little code snippet for the derive profile property as an example for me?

Thanks in advance

Jakob Kein

medini_1024169437

Well, you are already quite close, so could simply take the computed column from BIRT and put it into the derived property with a little adaptation:

self.mediniGetTracedElements(Metamodel.safetyModel.Malfunction).get(0)

Maybe it needs a check whether there IS a traced MF or not.

In BIRT you just access the derived property instead of navigating again

var mf = row["@self"].getObject().getProfilePropertyValue("your_property").get(0);
// maybe access the name?
mf.name;

Hope that clarifies it.

Jan

medini_1050222804

Hi Jan,

thank you for your reply. This is good, but there is just a small piece missing in my opinion.

The attribute should reference to all objects, even if there is more than one object traced.

With ….get(0) I think there will only be one reference stored, am I wrong?

medini_1050222804

If I use your snippet, I get this as result:

Do you know any solution for that?

medini_1024169437

Sure Jakob, drop the get(0) to get all of them.

I checked the issue and it seems that the Metamodel singleton was missing for JS properties in 19.2 and was added in 19.3, I am sorry to tell.

Regards

Jan

medini_1050222804

Okay, thanks for the reply and finding a reason for my issue.

Regards

Jakob

medini_1024169437

Jakob,

you can use OCL in medini instead, that should work also for 19.2 so

self.mediniGetTracedElements(safetyModel::Malfunction)

Jan

medini_1050222804

Hello Jan,

I think you meant to put this in a computed column of my SafetyGoal Dataset, isn´t it?

thanks for your effort, but I think there is no possibility to get the traced elements for any kind of safety goal in MA 19.2.

medini_1024169437

No, this OCL statement is meant to be put into a derived property in medini only. Then access the derived property from the computed column in BIRT as described above.

Jan

medini_1050222804

Great, it works.

Thanks so much!!

Jakob

medini_1050222804

Hello Jan,

I try to annotate some checklist Item to a Hazardous Event by trace.

The trace gets evaluated by a derived profile property. like shown below:

It works and includes all the traced checklistitems to the derived property.

Now when it comes to reporting, I´m trying to set a computed column to output the content of this derived profile porperty. But when I implement this column I get the following exceptions:

Operation 1:

row["@self"].getObject().getProfilePropertyValue("variante");

Result for every entry:

[]

Operation 2:

row["@self"].getObject().getProfilePropertyValue("variante").get(0);

Resulting Exception:

Do you know any solution, or is it just not possible to analyze profileproperties of kind checklist item?

medini_1050222804

Little update:

To make it easier for BIRT to get the propertyvalue I changed the derived attribute.

No it contains the name of the traced checklist item. In my opinion that should be a string type.

Now I can try what I want in the computed column:

If I try: row["@self"].getObject().getProfilePropertyValue("variante")

The results at "Preview results" stay like "[]"

and I get an exception at generating the report.

If I try: row["@self"].getObject().getProfilePropertyValue("variante").get(0);

I get an exception at prewieving the results.

medini_1024169437

Jakob,

difficult to say, but please check this article, last statements: https://medini.freshdesk.com/support/discussions/topics/1000092094

If you use OCL data sets you must ensure that caching s disabled, otherwise you get strange exceptions during reporting.

Jan

medini_1050222804

The caching was the issue.

Well done, thank you very much