Answered

Formatted text artifacts are not published in Word

If I publish my diagrams as Word, all the formatted text artifacts are totally ignored and not published at all. This is a serious problem since they contains vital info about the process.

Comments (6)

photo
0

Dear Dario,

According your question, Bizagi takes the formatted text from extended attributes and artifact text.

Please send us an example where we can reproduce it,

Thank you in advance.

photo
0

The same behavior occurs when publishing for Web.

To recreate:

  • Open a new diagram.
  • Add a single pool.
  • Select "Formatted Text" object from the Artifacts menu
  • Save
  • Publish - select Word, PDF or Web (it doesn't matter)
  • In the Publish setup select the only available diagram, then select the only available process
  • The Formatted Text object does not appear as an available element that can be selected for publishing.

This is an important object to publish since it may contain critical ancillary process information.

photo
0

Dear Dion,

We have reproduced it and we have escalated to our product team. As soon we get news, we will write back.

Regards

photo
1

Dear Dion,

Our team has analyzed your issue. Here is the answer: Elements like Groups, Annotations, Formatted texts and headers are not published to Word, PDF and Web because they are elements in a graphic level. In fact, they cannot be set with further information that they show. If you need to add critical information to a process, then you need to add it through element properties.

Regards

photo
1

If these items cannot be published, what is the point of having them in the tool at all? They have no use to anyone but the person actually creating/working on the model. Are they just intended to capture temporary notes for work in progress?

photo
1

Dear Dion,

The artefact purpose of rich text is to give you the opportunity to include text (with format) directly into the picture in the diagram. Doing this, the 'artefact' and its text will be included when the diagram is exported.

If you would like to include text in documentation option, we recommend using an extended text attribute in a task, or in a 'pool'.

Regards