Entries by Lydia Ma

Perform Conditional Formatting

It is very often that you would like to emphases particular details in the document which is generated from your model. Thanks to the fully customizable templates in Doc. Composer, you can achieve this by perform conditional formatting based on particular information in your model. In this article we will show you how to define […]

Defining template for columns in fill-in doc.

Starting from version 14.1 user can specify template for each column when generating Fill-in Doc. This give user more flexibility on constructing tables in Fill-in Doc without creating their own table templates. When defining table in Doc. Base user can specify template in column using ${TEMPLATE notation. Consider you have the following table in your Doc. Base […]

Sorting Elements According to their Location in Diagram

When output diagram elements to document via Doc. Composer, by default elements are sorted according to their creation order in the diagram. The sort order can be controlled by define sorting parameters in Doc. Composer templates, including to sort the elements according to their location in your diagram. In this article we will demonstrate how […]

Retrieve Sprints and Associated User Stories

Visual Paradigm support agile development process via UeXceler, which you can break down your work into user stories and organize and priorities the development work with sprints. Starting from version 14.0 build 20170320av you can retrieve the user stories from sprints using Doc. Composer. We will walk you through the details in this article.

Create Document having Mixed Page Orientation

The Build from Scratch mode in Doc. Composer provide a page like editor to create document for the models. It allow user to create the content page by page. The size of the page and orientation directly affect how much content can be shown in the document. In some situation you may want to have a different […]

User Story scenarios

User story is one of the very important component for users who capture requirements with Visual Paradigm. Each user story features a set of properties for you to describe the different aspect of a user problem or requirement. A property is called scenario. Each scenario involves a set of steps, recording the preferred system behavior in accomplishing that specific user story.

Accessing Model Hierarchy Recursively

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 […]