Renaming Projects


So I have recently renamed a project in VP from X to Y and it worked a treat; it updated the name both within the server and the name within VP. However the directory name within the workspace is still referencing the old name of X (As Im using a mac the directory is as follows: Library/Application Support/VisualParadigm/ws).

What I’d expect to see is: Library/Application Support/VisualParadigm/ws/B
However what is being returned is: Library/Application Support/VisualParadigm/ws/A

I have created a whole new workspace thinking it could be config related or something is cached but this doesn’t seem to be the case.

Why wouldn’t the name of the directory also change?

Hi GregS,

Thank you for your post. Currently, the renaming of a project changes only the display name but not the name of the folder in which the project file is stored. We believed this would not affect users’ experience and the functionality of the product. May I know why you need the folder name to be changed as well?

Best regards,

Jick Yeung

Hi @Jick

I just think for consistency purposes renaming everything would be the better option rather than just partially updating.

Scenario: Let’s say I renamed project X to be called Y like in my original question. However a year later I need to create a new project in the server and the name of that project is called X. What would happen when you check this new project out locally, would the folder name of the new project be called X1? As X folder already exists as this wasn’t updated originally.

Hi GregS,

There are chances that some resources, both managed by Visual Paradigm or third parties, are accessing the project through absolute paths. That’s why we tend to keep it. I will forward your suggestion to our team for further studying. If there is any news, I will let you know.

Have a nice weekend

Best regards,
Jick Yeung

Hi @Jick ,

So we also use absolute paths within our team. We basically store a list of projects in our server in a MySQL table and then have a node script which takes all those projects and runs VP using the mechanism; just so we can programmatically scrap model elements from the project and store the data. eg;
cd "/Applications/Visual" && sh -project "/Users/username/Library/Application Support/VisualParadigm/ws/teamwork_client/projects/X/X.vpp" -pluginid com.dpdgroup.plugin.cron -pluginargs "scriptName"

Because I renamed the project, I know that the name in the MySQL table won’t match up to the name in the VP server. The MySQL table will contain a project name called X but the actual name in the server is called Y.

From my perspective the reason why I asked this question was just because it seems a little inconsistent. If I were to have someone new join my team or take over my role or if I simply forgot about renaming the project, they wouldn’t have a clue about why they are different. Therefore I’ve had to put a note in our table just to make it clear.