Under Consideration
Element properties of connectors are not displayed at the web (version 2.4)
Beside a text/label I'm putting som nice descriptions to my connectors. However when publishing the model to the Web i can't click on the connector and see the description. I see the description for other elements, however not for the connectors. Is it something that i'm doing wrong?
Dear Sten,
Descriptions for connectors are not actually included in documentation (when configuring elements to include, connectors are not listed).
While it may be useful to jot notes about a general description, these are not as frequent to want-to-show for users reading the process documentation.
However, we will move this subject as an improvement idea.
Best regards,
Dear Sten,
Descriptions for connectors are not actually included in documentation (when configuring elements to include, connectors are not listed).
While it may be useful to jot notes about a general description, these are not as frequent to want-to-show for users reading the process documentation.
However, we will move this subject as an improvement idea.
Best regards,
I have the same need !I don´t need the name, but the description is very important.
Have the same demand from my projects. It would further improve consistency of the tool, if Connectors would be treated same as other model components wrt documentation.
Georg
Agree. Sometimes there is an extensive description on moves between Tasks or Events explaining prerequisite conditions for the move. I guess it should be the same as done for Tasks/Events - separate list of connectors:
Icon: Event_A --connector_1--> Event_B
Name: Name of the connector
Description: textual description of the connector - e.g. conditions, actors, expected results
PLEASE realize that - a user can either add it to the document (by choosing in the publishing master) or not - but in some cases it's really needed.
Hi there...
How can I export and document attribute about flows? both message and sequence?
Is there any news about that? Or some workaround?
Comments have been locked on this page!