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

Hidden & Unhidden SafetyMechanism in DC Worksheet

medini_1056767075

Hi,

Is there any way to know if an lmpf or spfSafetyMechanism is hidden or not in the DC Worksheet via scripting?

Here is an example:

I would like to obtain ONLY the spfSafetyMechanisms that is checked (SUP_PC...) as shown. When I use the following line of code:

console.log(failureModes[n].element.spfSafetyMechanisms);

a list of all of the spfSafetyMechanisms objects are shown (including the hidden ones) and there is no attribute which is related to it being hidden or not as their boolean-type attributes are the same.

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1023909254

Hi John Paul,

if filtering is applied to the safety mechanisms associated with a DC failure mode, the list of active safety mechanisms is contained in a different list, you would find it in

failureModes[n].spfSafetyMechanisms

So in your script you need first to check whether this list is empty - if that is true you use

<code>failureModes[n].element.spfSafetyMechanisms</code>

and otherwise

<code>failureModes[n].spfSafetyMechanisms</code>

Best regards,

Eckhardt

All comments

medini_1023909254

Hi John Paul,

if filtering is applied to the safety mechanisms associated with a DC failure mode, the list of active safety mechanisms is contained in a different list, you would find it in

failureModes[n].spfSafetyMechanisms

So in your script you need first to check whether this list is empty - if that is true you use

<code>failureModes[n].element.spfSafetyMechanisms</code>

and otherwise

<code>failureModes[n].spfSafetyMechanisms</code>

Best regards,

Eckhardt

medini_1056767075

Hi Eckhardt,

I tried that as mentioned above. However, other Safety Mechanisms that are hidden are also shown.

medini_1023909254

Hi John Paul,

that is strange ....

Can you try the following:

 if(failureModes[n].allSpfSafetyMechanismsApplicable){
 // no filter for SPF
 console.log(failureModes[n].element.spfSafetyMechanisms);
 }
 else {
 // Filter on SPF
 console.log(failureModes[n].spfSafetyMechanisms);
 }
 if(failureModes[n].allLmpfSafetyMechanismsApplicable){
 // No Filter on LF
 console.log(failureModes[n].element.mpfSafetyMechanisms);
 }
 else {
 //Filter on LF
 console.log(failureModes[n].lmpfSafetyMechanisms);
 }

Best regards, Eckhardt

medini_1056767075

Oh wait, your first code (without element) works:

<code>failureModes[n].element.spfSafetyMechanisms</code>

Thank you, Eckhardt.

medini_1063023713

Thank you Eckhardt! :-)

medini_1064751991

Following up on this topic, I have found that the spfSafetyMechanisms and lmpfSafetyMechanisms sometimes doesn't capture the current list in the FMEDA worksheet UI. For example, I have my FMEDa entry as such -

Looking at the underlying variable using the "Diagnose" feature, the lmpfSafetymechanism list is empty -

Now if I hide and unhide the safety mechanism in the FMEDA worksheet -

It shows up in the attribute under the Diagnose feature

Is this is bug or am I missing something?

Setup:

Medini 2021R2.1.
Show only SMs edited in this worksheet is enabled before editing the worksheet.

medini_1063023713

Hi Rahul,

I think this is due to the fact that allLmpfSafetyMechanismsApplicable is true (default value of <not set>) in the first case and false in the second case.

So basically in the first case, the mpfSafetyMechanisms is not a property of dc but of its element while in the second case it is a property of dc.

By doing your hide/unhide operation, you basically changed the behavior of allLmpfSafetyMechanismsApplicable

This is the code I use in my script to retrieve them:

//user_sm_mpf
if (self.allLmpfSafetyMechanismsApplicable){
var tmp_sm_ref=self.element.mpfSafetyMechanisms;}
else {tmp_sm_ref=self.mpfSafetyMechanisms;
}

Regards,

Romain

medini_1064751991

Ok that is very helpful. Thank you so much Romain!