Yet another sorting question

This topic has 4 replies, 2 voices, and was last updated 7 years, 9 months ago by Mark Elson.

Viewing 5 posts - 1 through 5 (of 5 total)

Author

Posts
15 February 2017 at 9:12 am #8762

Mark Elson
Participant

Hi,

I have a hierarchy of requirements that I am exporting to a document. I’d use packages to organize the hierarchy but sometimes the hierarchy deepens in the middle of a set of requirement so I ended up using a parent requirement with children, e.g.

1 Package (exported as a heading)
1.1 Req1
1.2 Req2 (exported as a heading)
1.2.1 Req2.1
1.2.2 Req2.2
1.3 Req3
…
I don’t want all the detail that goes with requirements (id, verification method etc) to be exported for a parent requirement (1.2 Req 2 above) so I created a heading stereotype to apply to such requirements.

The trouble is that eaDocX then changes the sort order so that the stereotyped requirements appear at the end as below

1 Package (exported as a heading)
1.1 Req1
1.2 Req3
1.3 Req2 (exported as a heading – now after Req3)
1.3.1 Req2.1
1.3.2 Req2.2

which I don’t want to happen. I’ve tried the up-down arrow approach in EA (to set tpos) but that makes no difference. Is there a way to keep the sort order as it is in EA? There isn’t a common attribute that is being printed that I can use.

Thank you,

Mark

15 February 2017 at 9:35 am #8763

eadocX Support
Participant

The only way to stops this happening is to have a single profile for ‘Requirement’ elements.
What’s happening is that eaDocX groups together similar-formatted elements and prints them together. This usually looks neater. Especially hen they are printed in tables. I agree that when printing inline, it’s maybe redundant, but i’m sure there’s a reason why I left in the grouping idea for inline as well.
So, if you can, delete the formatting for the stereotypes, and all will be well. The EA sequence will be respected (remember, you may have to do the up/down trick to make sure EA saves the ordering sequence).

15 February 2017 at 9:58 am #8764

Mark Elson
Participant

That defeats what I am trying to do.

I had a single profile for requirements that prints description, id, verification method (the last two in a table) etc. I then changed the profile for a Requirement so that it only prints name and children (decription, id etc are non-applicable – it’s just a heading). If I don’t supply the heading stereotype I get a heading but then an empty id etc which looks messy (and elicits complaints).

15 February 2017 at 12:03 pm #8765

eadocX Support
Participant

But you can get rid of all the ‘null’ entries by making it a ‘Compact Document’ (document-level setting). This omits anything which has no value.
Have you tried that ?

16 February 2017 at 8:58 am #8766

Mark Elson
Participant

I have now but it doesn’t work because my requirement profile specifies some tagged values and traceability info which are output to a table under the description (now empty). Even if I delete the tagged values and there are no relationships attached, an empty table still appears (even with compact document=true).

I can see ordering/grouping by profile makes sense in a table but not in in-line text. It would be better to use the EA ordering and let the user control it.
Author

Posts

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

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