powerVault v18

v18.0.19

14-12-2017

General

• Changed logging to have a single centralized configuration file and shared logging assembly in GAC

Fixed

• Highly increasing memory usage when calling Cmdlets very often (>100 times)

• Update-VaultFile / Update-VaultItem: When updating references (dependencies or attachments) and some references were already checked-out, then powerVault didn’t change any references and kept the file checked-out.

v18.0.17

24-08-2017

Fixed

• Get-VaultItem -Properties didn’t work for all item properties, for instance ‘Description (Item,CO)’, ‘Title (Item,CO)’, ‘Units’, ‘Number’…

v18.0.15

18-08-2017

Fixed

• Fixed typing mistake of special property Attachments on PsObject Comment

• Extended PsComment with support for comments that do not exist in vault

v18.0.12

17-07-2017

General

• Extended with following PsObjects: Folder, Custom Object, Change Order, Comment, Email

v18.0.10

24-05-2017

Features

• New cmdlet: Add-VaultJob

• Open VaultConnection now reuses existing connection when application is already connected to Vault

v18.0.8

21-04-2017

• Official Release

General

• Added support for Vault 2018

• Removed support for Vault 2014 & 2015R2

• Introduced extended [/logging`.

• Installed “powerVault 18.0 Logs” shortcut in start-menu section of powerVault

• Changed registry keys to “HKLM\Software\coolOrange s.r.l.\powerVault”: Location and Version

Fixed

• Add-VaultFile: issue that local file becomes locked when adding as new file to Vault.
  Therefore removing locale file was not always possible immediately after this cmdlet (only if Garbage Collection released file handle).

• Update-VaultFile: invalid log error-message “Failed to checkin the file” when -Comment parameter is used for released vault files.
  The file does not become checked-out and checked-in with the new comment any more, when file is locked.