Products

Home › Forums › eaDocX queries › Including an element’s tagged values in document

Home › Forums › eaDocX queries › Including an element’s tagged values in document

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • 9 September 2015 at 12:22 pm #8260
    Mike Lucas
    Participant

    Hi

    I think I must be missing something really obvious, but I can’t figure out how to include a full list of an element’s Tagged Values when generating documentation.

    The specific issue I’m having is that I have defined some Nodes, each having their own list of attributes (IP Address, RAM, Disk size etc), to represent server types. I’m then creating specific instances of these server types which will have values associated with the classifier’s attributes.

    I have used Tagged Values within the Node definitions because I noticed that Attributes doesn’t appear in the list of sub-elements for the Nodes profile, but now I can’t find how to include a full list of Tagged Values either. I need to include these Attributes / Tagged Values for both the server types and their instances. If there’s a way of doing this using Attributes rather than Tagged Values that would work too.

    Any guidance would be appreciated.

    Thanks

    Mike

    9 September 2015 at 2:09 pm #8261
    eadocX Support
    Participant

    Hi Mike,
    eaDocX will let you print TVs either as cells in a table or as paragraphs. For tables, there will be a drop-down of the TVs, same for Inline elements.
    We get the list of TVs by looking in real-time at your model, and finding out which TVs actually exist: if one is defined e.g. in an MDG, but never used, then it won’t appear. On the basis that there aren’t any for ANY element.
    If your TV list is missing one, then it may be that there is no element in your model which uses that TV.
    There isn’t a single command to say ‘add all my TVs’, mainly because nobody has every asked for it.
    AS for the Nodes bit, i’m seriously thinking about allowing ANY kind of EA element to have attributes/operations, as the EA meta-model seems to allow it, even in places where it makes little sense, and people keep pointing-out places – like this – where it’s useful. I’ll add Attributes for Nodes in the next release.

  • Author
    Posts
Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.

Compare licence prices

Choose the licence that’s right for you and your team

Prices

Download a free trial

Download eaTeamWorks today for several free for life features, plus no obligation, 30-day trials of all the products: eaDocX, ea Revision Manager, eaSheets, Model Expert and PortfolioManager. Discover for yourself why we sell the world’s best-selling Enterprise Architect extension.

Download