Book a Demo

Author Topic: Level Numbering  (Read 3069 times)

SteveL0001

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Level Numbering
« on: February 17, 2010, 01:44:23 am »
How do I setup level numbering in a project so that numbering increments with each package in the project. For instance, I want package 1 to start with 1.0 and all elements under that to be 1.1, 1.1, etc. Package 2 to start with 2.0, etc. It is not clear how level numbering is set at the project level. I see documentation on how to modify a template for a report.

marcelloh

  • EA User
  • **
  • Posts: 192
  • Karma: +0/-0
    • View Profile
Re: Level Numbering
« Reply #1 on: February 17, 2010, 02:45:52 am »
I wish you all the best on getting the numbering correct. This is and has been a buggy implementation, with unpredictable result.
See in the forum, because there is many proza written about it.
(For me: without any serious result, so I gave up.)

Hint - play with:
paragraph > list numbering
paragraph > increase level
with heading 1, 2, 3 etc.

That should give you something to look at.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Level Numbering
« Reply #2 on: February 17, 2010, 09:01:41 am »
Unless I'm mistaken marcelloh, the question has nothing to do with rtf reports.  It's about the level numbering feature that exists in the project browser, and can be included in reports, displayed in the relationship matrix etc.

Unfortunately, although I thought you could do it at a project level, I can't find that anywhere.

marcelloh

  • EA User
  • **
  • Posts: 192
  • Karma: +0/-0
    • View Profile
Re: Level Numbering
« Reply #3 on: February 17, 2010, 05:08:11 pm »
@Simon: You could be right.

@Steve: I don't use this "Auto-numbering" feature. Used in in the past, and it never seem to fit my needs. So I number by hand.
It gives me more freedom.

Like my main packages for my use cases are separated into Themes.
Each theme has a number, like 01 Administration.
A use case package below that, would get 01-01 Example One

I also have a main package with screens.
Also with thema's, like 01 Administration
A screen below that, S01-01 Screen One

But the disadvantage is, that it can be inconsistent. Some of my collegues try to be inconsistent some times, just to see if I spot that :-)