- This topic has 0 replies, 1 voice, and was last updated 12 years, 8 months ago by .
Viewing 1 post (of 1 total)
Viewing 1 post (of 1 total)
- You must be logged in to reply to this topic.
eaDocX
High quality smart documents - fast
eaSheets
Spreadsheet tools for EA modelers
ea Revision Manager
Round-trip model updates direct from document reviews
Model Expert
AI enhanced quality validation & verification
Portfolio Manager
Plan and collaborate real-time across projects
Sparx in the Cloud
Model EA in your browser
eaDocX
High quality smart documents - fast
eaSheets
Spreadsheet tools for EA modelers
ea Revision Manager
Round-trip model updates direct from document reviews
Model Expert
AI enhanced quality validation & verification
Portfolio Manager
Plan and collaborate real-time across projects
Sparx in the Cloud
Model EA in your browser
Home › Forums › eaDocX queries › Use Case Formatting in 3.3
Home › Forums › eaDocX queries › Use Case Formatting in 3.3
I liked the structured scenario in table format. I don’t want separate headings for each path for each use case, and I don’t want them appearing in the Table of Contents. I now have to insert manual pages breaks to put all these additional headings on the same page as their text, which is a pain.
Also, the Basic Path for all use cases inserts a paragraph before the number in the Position field, which I then need to manually remove. Again this is time consuming cleanup work.
Download eaTeamWorks today for free for life features, plus no obligation, 30-day trials of all the products: eaDocX, Revision Manager, eaSheets, Model Expert and PortfolioManager. Discover for yourself why eaTeamWorks is the world’s best-selling Enterprise Architect extension.
Download