How to Share Report Composer Templates Effectively with VP Teamwork Server [Obsolete]
| This article is out-dated. For user on Visual Paradigm 12.1 or above please refer to How to Share Doc. Composer Templates with your Teammates for details about how to share your templates. |
Report Composer allows you to develop reports tailored to your company/industry requirements and standards. You can decide the project data to show in a report as well as to control the flow of content. You can decide the document component (e.g. table, plain paragraph, etc) to use as well as to “decorate” them with proper styles. All these can be achieved easily by writing your own templates, or by editing those pre-defined.
All Visual Paradigm modeling software come with a rich set of pre-defined Report Composer templates, fulfilling most of the fundamental reporting needs. Users can customize them for specialized reporting requirements. Moreover, templates can be shared across the team to maintain a common standard for reports produced by different team members.
In this article, we will see how to share report composer template effectively with Visual Paradigm Teamwork Server. In order to perform the steps outlined below, you need to have both the modeling software (VP-UML/Agilian/Logizian) and Teamwork Server Corporate Edition ready.
When your team is composed of people with different roles and authorities, you may want to have control over their actions in the modeling tool, to prevent them from making undesired changes. For example, while it is reasonable for a software architect to build class models, it is not reasonable for him to restructure any model developed, through the refactor feature. With VP Server, administrator is allowed configure the access rights of features for members or member groups. For example, by turning off the “
When Visual Paradigm release a new new version, it comes with many new and enhanced features. In order for a project file created in an old version to work smoothly in new version, it has to undergo a conversion process, which involve the checking and patching of project data. The conversion process is a one-off procedure done when you first open the project in new version. It may take a while to complete. So you can imagine if you are working as a team and your team have many, many projects, conversion can be a fairly daunting task.
It is often that you have quite a number of models being reused across projects. Duplicating those models across projects would lead to a management nightmare in which you will need to update all those models on all projects when you need to make changes on it. By creating reference projects in 