When try to output your project with large diagram using Project Publisher you may found it looks blurry. This is because by default Project Publisher will limit the size of the generated diagram image to maximum 4096 x 4096 px. If your diagram is larger than this size then the exported image will being scaled thus making the content looks blurry. To override this default setting:
Starting from version 14.1 you can report the changes between revisions of your project via Doc. Composer. In this article we will demonstrate how to output the changes of your project between the specified revisions in tabular form.
Doc. Composer templates allow user to customize how the model data being generated into documents. For standalone users or team collaboration users with proper permission he can freely make change or create customize templates. In case the template become outdated and wrongly created he can then remove it from repository. In this article we will show you how to remove the Doc. Composer templates in the repository. Read more
Doc. Composer provides an extremely customizable way to query the details of model elements and out put them into Word, PDF and HTML documents. In this article we will teach you how to customize the document templates to output the details of a relationship model. Read more
Trying to create custom document template on Class Diagram to output its containing classes and its members but none of the class member being rendered…
No class member being rendered to document
I would like to make change to the Doc. Composer templates but received error complaining on the permission.
Complain on lack of permission to edit Doc. Composer templates
This is caused by you didn’t have sufficient permission enabled in your VPository. To solve this problem: Read more
When you want to build a new document for your project, use Doc. Composer’s ‘Build from Scratch’ mode.
If you want to insert project details (e.g. images, element details) into an existing Word document, use Doc. Composer’s ‘Fill-in Doc’ mode.
Doc. Composer features two modes – Build from Scratch and Fill-in Doc. Typically, a project documentation or report is a combination of background information like project goal, scope and constraints, and design details like use case details, database design, process design, etc. The Fill-in Doc mode of Doc. Composer is designed to help you “fill-in” the design details of your documentation.
Although Doc. Composer comes with a complete set of built-in element templates, you may still want to customize or even to write your own templates for maximizing the efficiency of document design. You can accomplish this by writing and programming your own element templates.
When working with a nested model, you may want to access and printout the details of elements within a hierarchy recursively. Since the level of model can be unlimited, it is hard to write a custom element template with a chunk of code repeated a certain number of time, not to mention this way of coding will make the template messy and hard to maintain. To solve this problem you can form a recursive template call by applying the concept of template referencing. If you are a programmer, the idea is exactly the same as a recursive method call in programming. All you need to do is to add the element in the appropriate place in the template, to instruct the template engine to process the same template, forming a self-loop. We will walk you through the details in this article.
