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

Traces from Item definition to external documents

medini_1005899080

Hi,

I am trying to get all traces from my "Item" to "external documents". I've tried it like this:

self.oclAsType(projectmodel::PJProxyModel).mediniGetTracedElements(projectmodel::PJExternalDocument).oclAsType(projectmodel::PJExternalDocument).name

or this:

self.mediniGetTracedElements(projectmodel::PJProxyModel)

but both is not working. I receive an empty result. (no error message)

what is here special?

Sven

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024169437

Hi Sven,

shouldn't that be rather:

self.mediniGetTracedElements(projectmodel::PJExternalDocument)

Jan

All comments

medini_1059007410

Hi Sven,

You've not been far away:

self.mediniGetTracedElements(projectmodel::PJExternalDocument).oclAsType(projectmodel::PJExternalDocument).name

The item is not a PJProxyModel, but this is the way it is linked into the project (like any other model). The actual item is of type "hazard::PlainItem", which you can see when either following from the proxy via "originalModel" to the item, or by using the "Resolve" button at the top right of the attributes view (it resolves such proxies).

Happy Scripting,

Nils

medini_1024169437

Hi Sven,

shouldn't that be rather:

self.mediniGetTracedElements(projectmodel::PJExternalDocument)

Jan

medini_1024169437

Sorry, Nils was faster...

medini_1005899080

Hi Jan,

self<span class="token punctuation">.</span><span class="token function">mediniGetTracedElements</span><span class="token punctuation">(</span>projectmodel<span class="token punctuation">:</span><span class="token punctuation">:</span>PJExternalDocument<span class="token punctuation">)</span>

this doesn't work:

medini_1024169437

Sven, I think that's just a problem of the OCL console, its does not does not know about the special PJProxyModel->originalModel semantics of our project model so it evaluates the OCL against the PJProxy (maybe that was the reason for your initial OCL). It should work inside the profile property though.

Jan