Book a Demo

Author Topic: What does it mean? Specify ReportAuthor, …by adding tagged values to the gen...  (Read 5736 times)

PeterHeintz

  • EA Practitioner
  • ***
  • Posts: 1001
  • Karma: +59/-18
    • View Profile
On the history page for V12.1 http://www.sparxsystems.com/products/ea/history.html#1224
I found following:
Specify ReportAuthor, ReportTitle, ReportName, ReportVersion, ReportStatus and ReportAlias by adding tagged values to the generated package

But what does it mean?
Using package attributes like ReportAuthor, ReportTitle, ReportName, ReportVersion, ReportStatus and ReportAlias as report constants was already there in Vxx <V12.1.

Does it mean that I can now specify my own tagged values as reporting constants, and if so how do I use them in a document template?

Best regards,

Peter Heintz

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
The difference is that in a virtual document package the tagged values can be used, where before you had to fill in the alias, author, version etc.. on the package itself.

Geert

PeterHeintz

  • EA Practitioner
  • ***
  • Posts: 1001
  • Karma: +59/-18
    • View Profile
Greet, which tagged values?
Tagged values I define in the virtual document package myself?
Can I define and use a tagged value of “mySpecialTag” and use it e.g. in headers and footers?
Best regards,

Peter Heintz

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
No, not tagged values you define yourself. They are automatically there when you create a virtual document from the toolbox.

Geert

PeterHeintz

  • EA Practitioner
  • ***
  • Posts: 1001
  • Karma: +59/-18
    • View Profile
This is what I assumed, but I had some hope.
I still have the problem of having some meta data I need to put on cover page, header, footer which are on package level but I cannot cover with reporting constants.
Any idea on that, rather than duplication templates?
Best regards,

Peter Heintz

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
No, not really, except for a feature request to Sparx :-\

Geert

PeterHeintz

  • EA Practitioner
  • ***
  • Posts: 1001
  • Karma: +59/-18
    • View Profile
I have posted a feature request several months ago.
The simple solution from my perspective would be to access tagged values as reporting constants of the root package in the same way as possible in the package processing within the templates.
Best regards,

Peter Heintz