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

Dynamic Constraint Output gets cut off

Maria Tischer

Hi all,

I have a Problem with the display of the output of one of my dynamic constraints. The constraint creates a list of all requirements used in the FMEDA sheet, to check if all specified ones have been used.
This is the snippet that creates the set:

let MessageArg1:String = self.oclAsType(dc::DCComponentEntry)->closure(children.oclAsType(dc::DCComponentEntry))->collect(e|e.failureModes.oclAsType(dc::DCFailureModeEntry).getProfilePropertyValue('user_element_measure'))->asOrderedSet() in
    false

The generated output seems to be too long and is not displayed completely in the validation window. Is it possible to somehow add some newlines in between the entries of a set and would that even work with the medini output? I am a bit lost on how to do this with OCL.

Find more posts tagged with

Accepted answers

Jan Mauersberger

Hi Maria, I played a bit with your OCL and I can think of 2 low hanging solutions. Number 1 is to just show the requirements ID and not the full string. My solution:

inv:

let MessageArg1:String = self.oclAsType(dc::DCComponentEntry)

	->closure(children.oclAsType(dc::DCComponentEntry))

	->collect(e|e.failureModes.oclAsType(dc::DCFailureModeEntry).getProfilePropertyValue('user_element_measure'))

	-- use identifier, not full object string

	->collect(r | r.oclAsType(safetygoals::SafetyRequirement).identifier)

	->asOrderedSet() in


false

Second idea was to just reduce the string size if it exceeds a certain length like this:

inv:

let MessageArg1:String = self.oclAsType(dc::DCComponentEntry)

	->closure(children.oclAsType(dc::DCComponentEntry))

	->collect(e|e.failureModes.oclAsType(dc::DCFailureModeEntry).getProfilePropertyValue('user_element_measure'))

	-- just use the requirement name

	->collect(r | r.oclAsType(safetygoals::SafetyRequirement).name)

	-- reduce to 10 chars max

	->collect(s | s.oclAsType(String).substring(1, 10.min(s.oclAsType(String).size())))

	->asOrderedSet() in


false

Surely not ideal and for sure other options exist but this should be a good quick solution.

Regards

Jan

All comments

Jan Mauersberger

Hi Maria,

so `user_element_measure` is a reference property to a requirement, is that correct? And currently you see all the labels/names of the requirements?

Just asking to reproducing this nicely.

Jan

Maria Tischer

Hi Jan,

Yes user_element_measure is the reference to a requirement. I can see the names of the Requirements but if there are too many the output set is cut off at the end. For example, it would display something like "…,Requirement_10, Requirement_11, Req" where the last visible name is clearly cut off and everything behind is completely missing.

-Maria

Jan Mauersberger

Hi Maria, I played a bit with your OCL and I can think of 2 low hanging solutions. Number 1 is to just show the requirements ID and not the full string. My solution:

inv:

let MessageArg1:String = self.oclAsType(dc::DCComponentEntry)

	->closure(children.oclAsType(dc::DCComponentEntry))

	->collect(e|e.failureModes.oclAsType(dc::DCFailureModeEntry).getProfilePropertyValue('user_element_measure'))

	-- use identifier, not full object string

	->collect(r | r.oclAsType(safetygoals::SafetyRequirement).identifier)

	->asOrderedSet() in


false

Second idea was to just reduce the string size if it exceeds a certain length like this:

inv:

let MessageArg1:String = self.oclAsType(dc::DCComponentEntry)

	->closure(children.oclAsType(dc::DCComponentEntry))

	->collect(e|e.failureModes.oclAsType(dc::DCFailureModeEntry).getProfilePropertyValue('user_element_measure'))

	-- just use the requirement name

	->collect(r | r.oclAsType(safetygoals::SafetyRequirement).name)

	-- reduce to 10 chars max

	->collect(s | s.oclAsType(String).substring(1, 10.min(s.oclAsType(String).size())))

	->asOrderedSet() in


false

Surely not ideal and for sure other options exist but this should be a good quick solution.

Regards

Jan

Maria Tischer

Hi Jan,
thank you for your help and the quick solution. I tested both and I think the first one works best for me.

Cheers,
Maria

Marian Kuban

Hi @Maria Tischer ,

If you just want to display the full message arg content you can pump the validation results into a Problems View. Alternative way to open Problems View is while in Model Browser→open menu → Show In → Problems View.

Trick is that you will be still able to navigate to the violated object (c::DCComponentEntry object).

let MessageArg1:String = self.oclAsType(dc::DCComponentEntry)
->closure(children.oclAsType(dc::DCComponentEntry))
->collect(e|e.failureModes.oclAsType(dc::DCFailureModeEntry).getProfilePropertyValue('user_element_measure'))
  -- indetifiers
  ->collect(r | r.oclAsType(safetygoals::SafetyRequirement).identifier)->asOrderedSet() 
in    
false

Note if you want a new line formatting concatenate every result with '\n'.

let MessageArg1:String = self.oclAsType(dc::DCComponentEntry)
->closure(children.oclAsType(dc::DCComponentEntry))
->collect(e|e.failureModes.oclAsType(dc::DCFailureModeEntry).getProfilePropertyValue('user_element_measure'))
 -- indetifier+ newline '\n'
  ->collect(r | r.oclAsType(safetygoals::SafetyRequirement).identifier+'\n')->asOrderedSet() 
in
false

The text rendered in the Validation or Problems view will not render it but if reported it will be applied correctly.
I n case of Validation result entry, a first encountered newline character simply 'cuts' and drops remainder of the text

On top you can even export the validation results into:

File : Validation View → Ope Problems View → export → xlsx/pdf/doc
Checklist: custom script i developed , "dumps" the validation results into a project inside as a checklist

PS: w.r.t 2 Currently the violate object is stored inside of the elated Artifact have on my to-do list to enhance the script i made the message and detect emf object references and add those objects into the checklist item

Marian