Answered

Bug Report - all properties text contained within the characters < > get deleted on save/OK. For example < all t

Bug Report - Extended properties text within the characters < > gets deleted on save/OK.

For example < all this text will get deleted by Bizagi >

Took me weeks to establish why all our file paths example and code notes were being lost.

It certainly was a time consuming fault to have to deal with. <text with here will vanish without saving>

Suggest a patch!!!! Or at least something in your user guides... things like this waste a lot of time!

Comments (5)

photo
0

Dear John,

According your description, you are talking about Bizagi Studio where < > are used for Xpath. The XPath standard is a easy-to-use language for finding information in an XML document and is helpful in carrying out complex tasks. Bizagi incorporated this concept into its language, enabling users to easily navigate and use the data model to accomplish different tasks. XPath as a navigation tool enables users to navigate the data model accessing attributes and relationships. The 'location path' of the desired attribute in the data model is always written between diamond brackets:< xpath route > We can access any entity, and its attributes, as long as we follow the hierarchy that is laid out in the Data Model. XPath expressions will always begin with the Process Entity as the first attribute and from there navigate the rest of the data model. Data model navigation is defined by the relationships which are represented by arrows in the data model.

Please give us an example that you need to write text between diamon brackets.

We look forward

photo
0

No Juan you are completely wrong in your response.

We are using the Modeler.. creating extended properties and writing text in to produce documentation.

Text (valuable documentation content) is being lost when the characters < and > are used in the text boxes.

Just letting you know about some bugs in your product

photo
1

Dear John,

Thank you very much for this information. I could reproduce this problem in our last release. We are going to escalate to our Product team. As soon we get news from there, we will notify you.

Regards

photo
1

Thanks Juan...

Happy to provide feedback.

Cheers

John

photo
1

Dear John,

We have solved this problem. Please apply the following FIX according the README file: https://bizagi.sharefile.com/d-seea17fe69bf48ec9

Best Regards