Products

Home Forums eaDocX queries angle brackets cause loss of content

Home Forums eaDocX queries angle brackets cause loss of content

Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • #8002
    Frank Ertl
    Participant

    Hi,

    we have the following content in the notes of a usecase:

    Versandkontext = „//, “, wobei die ermittelte Konfiguration darstellt.

    Unfortunately it got rendered as

    Versandkontext = „//, “, wobei die ermittelte SMS-Konfiguration darstellt

    Any idea how to fix this?

    Regards,
    Frank

    #8003
    eadocX Support
    Participant

    eaDocX thinks that all <> characters are part of HTML tags, so will try to process them.
    There are some places, such as in the notes fields of elements, where we treat <> characters correctly: what element type and attribute contains this data ? Maybe we can pre-process this like notes fields.

    #8004
    Frank Ertl
    Participant

    As I wrote in my post: it is the notes field of an usecase-element.

    What surprises me is the fact that the first view angle brackets are processed:
    //
    but not the rest of them.

    #8005
    Frank Ertl
    Participant

    Hi guys,

    I know I’m a little bit impatient 😉 , but we got a deadline the next few days for delivery of the document. 🙁
    So I just wanted to ask if you got a little bit of information, maybe a workaround we could use?

    Regards Frank

    #8006
    eadocX Support
    Participant

    Simplest immediate solution is to replace the “<" characters with "<" which eaDocX will not process.

    #8007
    Frank Ertl
    Participant

    Sorry, but this does not work:

    [code]Versandkontext = „<BIN>/<FIID>/<PRIN>, <Konstellation>“, wobei <Konstellation> die ermittelte SMS-Konfiguration darstellt[/code]

    in the notes of our usecase becomes:

    [code]Versandkontext = „<BIN>/<FIID>/<PRIN>, <Konstellation>“, wobei <Konstellation> die ermittelte SMS-Konfiguration darstellt[/code]

    in MS Word.

    In other words: that “<” gets not processed is absolutely correct, but it also won’t get replaced by “<". That is no solution for our problem. Regards, Frank

    #8008
    eadocX Support
    Participant

    OK – I have just tried this in the about-to-be-released V4, and it all looks fine.
    BUT
    I don’t think we changed anything in this area, so I don’t see why it doesn’t work in V3.
    Can I confirm exactly where this data is located – notes field of an element? But what kind of element? I’m trying to reproduce the issue…

    #8009
    Frank Ertl
    Participant

    Hi,

    the element is still the same as in my first and third post… 😉

    It is an usecase.

    Regards,
    Frank

    #8010
    eadocX Support
    Participant

    Hi Frank,
    Just so I’m clear, this text is in the notes field of the UC?

    #8011
    Frank Ertl
    Participant

    Yes, it is. I’ll attach a screenshot.

    #8012
    eadocX Support
    Participant

    I forgot to ask earlier – which eaDocX version are you using ?

    #8013
    Frank Ertl
    Participant

    We’re using 3.5.5.0

    #8014
    Frank Ertl
    Participant

    Push… 🙂

Viewing 13 posts - 1 through 13 (of 13 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