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

Renaming of BE to match the failure mode from represents relationship

medini_1004872874

Hi Jan

For my user I tried to implement a small script that is renaming the BE when failure modes defined through the "represents" relationship were themself renamed.

When collection events.represents list how to extract only the type of elements that are only FailureMode ? I tried with instance but have issue. What do you advice to use ?

Thanks a lot for your feedback.

Florent

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1024169437

Sure Florent,

here a small snippet that should do the job and explain how it could be done:

// find events have at least have something set
var events = finder.findByType(Metamodel.FTA.Event).butNot("represents", null);

alert("Found " + events.size() + " events that represent something");

// find events have at a failure set
events = finder.findByType(Metamodel.FTA.Event).butNot("represents", null).filter(function (event) {
	// Before 19.3
	return Metamodel.safetyModel.Failure.isInstance(event.represents);
	// in 19.3 you can write
	// return event.represents instanceof Metamodel.safetyModel.Failure;
});

alert("Found " + events.size() + " events that represent failures");

Happy Scripting

Jan

medini_1004872874

Hi Jan

thanks a lot for the hint. Finally using butNot is more simple. I succeed to do what I planned to do. Just one little remaining small issue for display.

If I do not use alert then I have the following results from the return value I guess.

It is a way to not display it ?

Florent

medini_1024169437

Hi Florent,

glad that is helped. The script engine returns the last evaluation result as overall script result.

To avoid that, just can for example put undefined at the end of the script:

...

// last script line
undefined;

Happy Scripting

Jan

medini_1004872874

One additional comment. The JavaScript code before 19.3 is still working in 19.3 ?

Florent

medini_1004872874

Perfekt....Concerning the Javascript code before 19.3..Would it work after too or I would have to update my script according to your proposal ?

Florent

medini_1024169437

Yes, it will also work with 19.3 and beyond.

The "instanceof" is just an additional feature with 19.3 so the code with "Prototype.isInstance" will work as well.

Jan

medini_1004872874

Hi Jan

One small update..Imaging that I have now catch the BEs which are representing failure modes or malfunctions.. If I want to keep the medini notation for BEs like [Parent] failure mode or [Parent] malfunction, can you just remind me how to access to function from malfunction and Sysml element from failure modes ?

by navigating opposite to failures ?

Florent

medini_1004872874

or .mediniGetContainer() ?

medini_1024169437

Yes, Florent that's true, just use failureMode.mediniGetContainer() any you should get the "failable" element.

Jan

medini_1024169437

Hi Florent,

just to add that there is currently a feature under development that keeps "Failure" and "Event" in sync so no need to script the event name sin the future.

Jan

medini_1004872874

ah ha...we gave you the idea..... ;o)

medini_1024169437

Indeed Florent, I think its an idea of you and others since quite a while :-)

Took us some time to get there.

Happy Scripting

Jan

medini_1004872874

In our script we have extended the script to events that represents safety mechanisms too..

medini_1024169437

Sure, Florent, we thought of that too, it will be included. So basically Failures, SysML Elements and Safety Mechanisms. Well, a bit off-topic here anyway ... :-)

Greetings Jan