Book a Demo

Author Topic: Extension Points for a Use Case  (Read 3189 times)

PiotrS

  • EA User
  • **
  • Posts: 20
  • Karma: +0/-0
    • View Profile
Extension Points for a Use Case
« on: April 25, 2014, 07:58:19 pm »
Hi,
I have problem with reading value of extension points set for the Use Case.  :-[
It is two ways to read this value. First in API from Element.ExtensionPoints ("Optional extension points for a Use Case as a comma-separated list.") and secound from object from t_object.PDATA1 ("For UseCase: #EXP#=<ep>; semi-colon separated list of Extension Points <ep>").  8-)
Sometimes these values are different. The value from Element.ExtensionPoints is uncorrect, shorter then from PDATA1.  :o
Are there any limits (values of EP, length all/separate EP) to the definition of extension points in these source place?

PiotrS

  • EA User
  • **
  • Posts: 20
  • Karma: +0/-0
    • View Profile
Re: Extension Points for a Use Case
« Reply #1 on: April 26, 2014, 12:06:40 am »
Quote
Hi,
I have problem with reading value of extension points set for the Use Case.  :-[
It is two ways to read this value. First in API from Element.ExtensionPoints ("Optional extension points for a Use Case as a comma-separated list.") and secound from object from t_object.PDATA1 ("For UseCase: #EXP#=<ep>; semi-colon separated list of Extension Points <ep>").  8-)
Sometimes these values are different. The value from Element.ExtensionPoints is uncorrect, shorter then from PDATA1.  :o
Are there any limits (values of EP, length all/separate EP) to the definition of extension points in these source place?

I made some tests.. 256 chars is the limit for length of t_object.PDATA1.

It is only 256 chars for all sentence, separators ("#EXP#=" and ";") and values of extension points for a Use Case defined in UI. But this limit is not controled in UI (!), can we defined more then this limit. And from this I have problem.

The value in Element.ExtensionPoints included the values from t_object.PDATA1 without separators ("#EXP#=" and ";"), stored as comma-separated list values.
If in UI, user defined uncorect values (limit or more then limit), it is difficulte to find problem.
In t_object.PDATA1 is stored only 256 charecters sentence (value from UI is cut without any information).
In Element.ExtensionPoints not included the last EXP from t_object.PDATA1.

If t_object.PDATA1 has 256 characters in whole sentence without ";" on the end, the last EXP from t_object.PDATA1 "disappears", is not added to Element.ExtensionPoints but still stored in t_object.PDATA1 and shown in UI.
And from this, sometimes are differentes, and I think it is bug in UI of EA.