Home Forums eaDocX queries Minimising post-processing of eaXL outputs

Home Forums eaDocX queries Minimising post-processing of eaXL outputs

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
  • #7483
    Heather Wallace

    I love the flexibility of eaXL and make extensive use of it, for model updates, for analysis and for traceability tables for our published architecture documents But in order to provide usable outputs either to colleagues or for pasting into documents I always have to do the same post processing (and document the steps for other administrators):

    1. Ungroup all rows
    2. Expose and delete rows 1 and 3
    3. Expose and delete columns A and B, or A, B and C, depending upon the purpose of the output
    4. Change the cell colour and header colour and set borders
    5. Change the font (Arial 8pt in most cases for us)
    6. Set all cells to wrap text (happily, alignment is already top left)
    7. Set freeze panes to top row
    8. Filter out and delete rows for unwanted stereotypes
    9. Change column names for standard attributes (e.g. name -> System Function, parentName -> Function Grouping)

    For the stereotypes, is it possible to allow selection of Stereotypes, rather than just selection of Element Types?
    For the standard attributes, is it possible to allow users to specify the column name?

    For the rest, I understand that you need to have a consistent output to support the import process and reuse of the eaXL “template”, but I can imagine possible solutions that would help me and a host of other users:

    Option 1: populate a second tab for publication
    Option 2: offer the option of publication-only. In this case the generation process must first save the “template”, then save the output with a different filename.

    For either of these options, a menu of choices could be available, addressing items 1-7 above, with default settings and options where appropriate.

    Best regards,

    Heather Wallace

    Any thoughts on this one? Did it get missed?


    eadocX Support

    We didn’t miss it, so much as do something else: post-processing scripts for eaXL when importing.
    I agree that the idea is excellent, and if we sense there is more demand for it, we’ll do it..

    Guillaume Finance


    I second the need for post-processing scripts in eaXL. I’ve defined several Package Browser VBScripts to overcome some limitations of eaXL, and it would be very useful to execute them automatically after an import from Excel to EA.
    Even pre-processing could be useful (e.g. I have a “create dummy attributes” script that populates empty classes so that I can run an export all attributes to Excel).
    Having the option to associate each script either with the Excel to EA or EA to Excel + define a pre or post would be really good.

    Best regards,

    eadocX Support

    I think we’ve done this. Hidden in the ‘Searches’ tab in eaXL is a drop-down for ‘run script after import is complete’.
    Is this what you need ?

Viewing 5 posts - 1 through 5 (of 5 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


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.