Version 3.4 new features include:
Plus other technical improvements throughout the system. See this video tour for an introduction:
In previous versions, users with modify permissions could set the 'Approved' flag on a file on check-in. Version 3.4 includes an additional new approval process that includes multi-user voting. A user can request an approval on a chosen file, and invite other users to vote on it; these users can vote, abstain, approve, reject etc. They can comment on the file and all of this is retained in the audit trail. It's a flexible system that can support many bespoke in-house approval processes. For more information please see this video tour:
In 3.4 we have extended the popular, customisable, diagram-based navigation system to allow you to create custom home pages for particular types of user based on e.g. their project permissions, user type or licence type. So you can tailor the view of the project to your users needs.
In addition you can now activate many project functions directly from the process diagram, so for instance you can put your choice of functionality directly on the the home page, easily accessible rather than having to work through the menu system.
The home page can also be selected based on any of the project's customisable 'Extended Properties', allowing methods to be tailored on-the-fly to implement, for example, a gated process.
Please See this video for more information:
Verison 3.4 includes more user interface choices:
For more information please see this video:
We have increased the automatic clean-up of temp files generated both by the windows app and the browser app.
The client system temp files (e.g. viewed MS Word files) and the local copies of template process images can be set to auto-delete on client exit. Previously, updating the local copies of template files following a method template update was a manual process.
The 'Options' form in the client app now has a 'Special Folders' tab that lists important folders used by client.
The browser app now deletes the indivudal user's temp files as they move between pages, rather than relying on the session exit events to trigger this, which has proved unreliable in practice. This improvement means that litter is not left on the web server. Note that, in a default installation, the app is limited in which files it can delete - as Windows Server forces an application reset if folders are deleted within the application path. However there is the option to store the temp folder in a location under a different IIS Virtual Directory, in which case folders can be deleted too.