<< Click to Display Table of Contents >> Navigation:  White Papers > Workflow with Vault and PlantTools > Making modifications

Now we have a look how modifications to the PlantTools configuration files are handled. This description includes also adding new configuration files.

First make sure you have the 4 files from the "Related Files" folder in your local project copy and that you unpacked the zip file with "PT_Unpack.bat".

As an example we will modify the settings for the Bolt Calculation in PlantExpressTools. We start PlantProjectSetup from PlantExpressTools' PlantProjectManager.

We go to the "Bolt Calculation Setup" node and then check "Activate Bolt Calculation".

Then enables various settings.

At the end of "Bolt Catalog" we click on the "Copy" icon which copies the Bolt Catalog into the project.

We see the location of the bolt catalog under the ACPlantTools folder.

Also the xml file has been modified.

As long as the zip file and the PT_Files.txt are checked in, you cannot make modifications. So we check them out.

The batch files won't change so we checkout only the two files.

Now they are checked out.

If a file is checked out the Read-Only checkbox is unchecked.

Files which are checked in are Read-Only. This is why we need to check them out to make modifications.

Now we update the PT_Files.txt files from the "Related Files" folder.

Now we have a longer list.

We replace the folder name with ".." again.

Now we run the PT_Pack batch file to update the zip file.

We see the Command Prompt during this process.

If we look in the zip file we see the BoltCatalog.db, which is the bolt catalog database.

If we refresh the Project Manager we see the change symbol for our two files.

Now we can check them in for our colleagues.

Just the two.

Now they are checked in.

Update for other Users

The other users of course need those changes too. They see the red icon in Project Manager which indicated that there is a newer version available on Vault.

Since there is no Refresh function in Plant 3D to get the latest version we delete the outdated files from the "Related Files" folder.

Not only the two batch files exist.

In Project Manager we see the icon indicating that the files are not locally available and can be checked out.

We check out.

Select the two files.

Now the new versions are on our local project copy.

We check them in again so others can check them out too.

The same two files.

With Vault Professional

We can do this a bit more elegantly with Vault Professional.

Same situation with the outdated files.

We start Vault Professional.

We see that there is Revision "A" available for the two files. Ignore the two batch files. The Revision increase is due to writing this documentation.

Use "Get..." from the "Related Files" folder.

Click on OK.

Now you choose "Yes To All" to override all files in your local project copy.

Now the icon shows, that you have the files up-to-date in your local project copy.