We recently released Hotfix - API Lifecycle/Job Processor, which addresses two separate API related issues in Vault 2013. In both cases, the fixes are with Vault applications themselves, not with the SDK DLLs. So you don’t need to update any of your code and you don’t need to re-compile. Just apply the hotfix if you run into any of these issues and things should work.
Issue 1: If your extension hooks into change lifecycle events and adds a restriction, Vault Explorer shows a confusing error message. The operation is restricted, as expected, but the user sees the message “restrictedEntities Files Folders and CustomEntities are all empty.”
After applying the hotfix, users will see the standard Restrictions Found error dialog, which can be expanded to show messages from your extension.
Issue 2: When IExplorerUtil is used in a job handler extension, it will fail for all jobs after the first one. The underlying problem is that each job gets its own login and IExplorerUtil was remembering the security context. So IExplorerUtil would work for the first job but fail for all other jobs. The hotfix clears out any security details that IExplorerUtil may be remembering between jobs.
Subscribe