Book a Demo

Author Topic: Numbering in RTF Notes EA 7.1  (Read 3522 times)

philchudley

  • EA User
  • **
  • Posts: 750
  • Karma: +22/-0
  • EA Consultant / Trainer - Sparx Europe
    • View Profile
Numbering in RTF Notes EA 7.1
« on: February 08, 2008, 02:41:09 am »
In the new RTF enabled notes feature, if a numbered list is used, then it cannot be interrupted with non-numbered lines and then the list continued. For example, here is a simple Use Case scenario using the numbered list. This scenario (copied from EA 7.1) indicates where alternate paths may exist:

1)The use case begins when the Customer adds an item to the cart
2)[ALTERNATE] Create Cart
3)[DATA] productCode
4)[DATA] quanity
5)System creates an Item using the product code and quantity
6)System checks the quanity on hand using the product code and quantity
7)System adds the item to the cart
8)[ALTERNATE] Insufficient stock
9)Use Case ends

If I remove the line numbering from the lines with [ALTERNATE] and [DATA], the result is

1)The use case begins when the Customer adds an item to the cart
[ALTERNATE] Create Cart
[DATA] productCode
[DATA] quanity
1)System creates an Item using the product code and quantity
2)System checks the quanity on hand using the product code and quantity
3)System adds the item to the cart
[ALTERNATE] Insufficient stock
1)Use Case ends

What I would like to happen is:

1)The use case begins when the Customer adds an item to the cart
[ALTERNATE] Create Cart
[DATA] productCode
[DATA] quanity
2)System creates an Item using the product code and quantity
3)System checks the quanity on hand using the product code and quantity
4)System adds the item to the cart
[ALTERNATE] Insufficient stock
5)Use Case ends

That is "Continue Numbering"
Models are great!
Correct models are even greater!

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Numbering in RTF Notes EA 7.1
« Reply #1 on: February 08, 2008, 03:29:48 am »
So, for now you might have to extract the included use case to an included use case...
No, you can't have it!