Book a Demo

Author Topic: Embedded element's connector in generated document  (Read 4228 times)

Jiří Hegr

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Embedded element's connector in generated document
« on: August 31, 2011, 10:53:39 pm »
Hello all!
Let say I have a diagram with two blocks, every block has its own port (embedded element) and between these two ports there is a connection (control flow for example).
My question is, how can I add the control flow into RTF document? In a template for that document there is a possibility to add elements, connectors between elements, embedded elements (ports for example). But I can't see the way how to show properties of links between embedded elements.
Could anybody help and show the right procedure?
Thanks,

Jura

kepNCI

  • EA User
  • **
  • Posts: 127
  • Karma: +1/-0
    • View Profile
Re: Embedded element's connector in generated docu
« Reply #1 on: August 23, 2014, 12:17:26 am »
Apparently there was no replies to Jura's Aug 2011 posting and now I have the exact same question...

How does one create a report template that can display the connection (and attributes) between two nodes' ports (embedded elements) like you can with connections between two nodes?

I am assuming you cannot which rather defeats the purpose of ports.

Karl

kepNCI

  • EA User
  • **
  • Posts: 127
  • Karma: +1/-0
    • View Profile
Re: Embedded element's connector in generated docu
« Reply #2 on: September 04, 2014, 12:54:21 am »
Thanks to Dermot (Sparx Support) there is a way to report embedded element connections.

Turn on embedded elements in the template section, but do not place any text/fields in the template.  That is the template would look like:

embedded elements>
<embedded elements

Upon seeing that there are no fields for embedded elements, the generator will default to what ever you have for the element, including the child sections, such as connections and attributes.

If you place anything within the embedded elements, the default is not taken and you are on your own, thus limited to the fields that can be selected under embedded elements.  A feature request has been made to allow the same child sections for embedded elements as you get for elements, thus providing more control over the report output.