Working with Master View
When your project is simple, you are able to express all of the design ideas with just a few diagrams. The diagrams are simple and self-explanatory. Each of them represents a distinct design idea and there is no overlapping between diagrams.
When you are dealing with a complex project, you may need to draw multiple diagrams to represent different contexts. You need to borrow shapes from a diagram to make them appear in other diagrams (i.e. contexts). In fact, this is extremely common when modeling with class diagram and business process diagram. Take UML class diagram as an example, there may be a domain diagram that presents all the entity classes and, another diagram that presents the associations and dependencies between a specific controller class and its related entity classes. So in this case, both diagrams contain the same set of entity classes.
Instead of re-creating those classes again and again in different diagrams, Visual Paradigm allows you to “re-use” them. Through simple copy and paste (Ctrl-C and Ctrl-V), you can easily copy a shape from one diagram to another. Each shape is formally known as a “view”. So with this, you can create multiple views for a model element in representing different contexts. Changes made on a shape are all synchronized to other instances that appear in other diagrams without extra effort. This is great, but there is a drawback though.
ID is a very useful property for a model elements. Having an unique ID for your model elements not just can ease the communication between your team but also help to structure your model in a more systematic way. 
The find feature allows you to search for specific words or sentences within text in the description editor. Finding starts from the beginning of the description, regardless of the position of text cursor. The first occurrence of text that matches with the entered search text will be highlighted. You can move to the next occurrence by clicking on the Next button. You can perform finding in all the RTF description editors, such as the description editor in specification window.
There are two common misunderstanding about use case modeling or 
For every model element, there is a description property that allows you to describe detailed information about individual element, so that readers can understand the intended use, intended behavior and other important information. For example, specific implementation guideline can be written in a UML class or 
When you copy and paste formatted text into a description editor in 
When you are documenting your model, you may come across the situation where you want to make a reference to certain diagram in the project to help you explain an idea or to give reader supplementary information they may find useful. For example, you may want to add into the description of a 
Sometimes, you may want to give a shape a long name. If the name is so long that it reaches the shape border, it will automatically wrapped. If you dislike the auto wrapping behavior, you can add line breaks to appropriate position yourself. In this article you will learn how to add a line break when editing a shape’s name inline.