Forum Replies Created
-
I contructed a simple test case and the problem seems related to element sorting when the list contains multiple stereotypes.
I created an object diagram, dropped 4 Class elements on the surface, and gave them Aliases of 001, 002, 003, 004
Alias 001, 003 => added Stereotype A
Alias 002, 004 => added Stereotype BDiagram and all elements in one package.
Created a simple report, based on the diagram and all contents.
Created a simple profile for Class elements, print inline, header of Alias and Name, added one atribute of Stereotype to print in an inline table. Set sorting to sort on Alias, A-Z.
Results print in 001, 003, 002, 004 order
OK, ran across another example today and spent time investigating. Just to see what would happen I flipped the sort order from A-Z and Z-A. The results were not what I expected, and this led me to realize that there are two different stereotypes involved in the elements we are sorting, and the sort is treating it like there are two groups of things to sort.
These are all Activities, with elements that are straight BPMN 2.0 Activities, and then other elements that are a custom MDG stereotype that extends the BPMN 2.0 Activities.
The reporting and sorting is defined at the Activity level in eaDocX, I treat them both the same in the report.
So in the last example we had 7 Activities, 3 plain BPMN and 4 custom MDG Activities.
Activity alias 001, 003, and 006 are plain
Activity alias 002, 004, 005, and 007 are customA-Z sort yields 001, 003, 006, 002, 004, 005, 007
Z-A sort yields 006, 003, 001, 007, 005, 004, 002This is also consistent with the other examples I have run across.
Let me know if you need more detail.
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