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

proxy: navigate from failure mode to it's DC worksheet equivalent

medini_1036016653

Dear Jan and community,

is there a proxy to navigate from a failure mode (Metamodel.safetyModel.FailureMode) to it's entry in a DC worksheet? The documentation describes the reverse path: "ComponentEntry#element".

I require this for a script I'm working on, but couldn't figure it out myself yet. The script works on the system model with parts/ports and failure modes and now I want to touch the derived DC worksheet (FMEDA).

Thank you!

Peter

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024169437

Peter,

I think this article: https://medini.freshdesk.com/support/discussions/topics/1000093558

explains it very well. Please have a look, it shows two options that you have here.

Happy Scripting

Jan

All comments

medini_1024169437

Peter,

I think this article: https://medini.freshdesk.com/support/discussions/topics/1000093558

explains it very well. Please have a look, it shows two options that you have here.

Happy Scripting

Jan

medini_1036016653

Dear Jan,

perfect. Option 2 seems the way forward. Option 1 would not generically work for my use case, as I have possibly multiple DC worksheets and want to ensure I'm modifying the correct one. Consequently by using the finder I would have to additionaly filter by name.

The scripting documentation does not tell us about ".mediniGetOpposites()", only the metamodel document does so in a hidden OCL example.

Best regards

Peter

medini_1024169437

Thanks Peter for the hint,

we will improve the documentation.

Jan

medini_1036016653

You're very welcome. I noticed a couple of other minors. I'll open another topic about it.

medini_1036016653

Ah, please explain the parameter that funtion takes. "element" as a parameter worked for me, but at a quick glance I couldn't tell why :-)

medini_1036016653

Jan, could you please alaborate why one has to use "element" as a parameter for "mediniGetOpposites()"? Thank you!

medini_1024169437

Hi Peter,

sorry, I missed your previous question. Well, the metamodel for FMEA and DC basically looks like this:

So the worksheet contains lots of proxy elements of various kinds that refer back to the original SysML model elements.

The reference that is used here is called "element". If you now want to navigate back from the element to the FMEA/DC proxies you use the name of that reference in "mediniGetOpposites" or in any of the finder filters.

Hope that explains it.

Jan