Fred shows the version of the document as metadata value and in the version history list of the document.
This will be fully supported in Fred 1.3
There is conceptually a minor issue from the user-perspective: let's say we have a document in Alfresco, version 1.0. We can choose "Edit Offline" from the context menu, a working copy is created on the user's hard drive. From the user-perspective, this is document 1.1 (or 2.0) but the metadata/template shows 1.0. From the repository-perspective, this document is still version 1.0 as long as it is on the user's hard drive and not checked into Alfresco again.
This depends on your setup, but probably the http request is going to time out and Fred won't be able to show you the contents of this folder. Fetching a thousand objects (with all metadata) takes about 30 seconds (depends on your server hardware and data dictionary model). That's about the default timeout value.
We are working on a two-stage process to resolve this issue where the content will be presented fast and additional information will be provided in a second step.
If you need all your office documents transformed, this would typically be accomplished with setting up (folder)rules in Alfresco.
We're looking into a "Convert to PDF" function in a context menu, so you could create a PDF from an Office document in Fred.
Currently there are 2 types of column sets:
1. document-type-column-sets: they contain the property-columns relevant for their document type (shared, because the dictionary model is shared)
2. user-defined-column-sets: the user can create and save his own sets (individual)
We're thinking about a way to define corporate-wide column-sets, that would be shared. This is not implemented yet.
The right click context menu of every document/folder in Fred has a "Show in Browser" item. This will open your default browser and show you the relevant item. If you use this in Fred, somewhere in the Share folder structure, your browser will be pointed to the share interface.
As the classical folder structure can be addressed through the share interface, we can point the “Show in browser” for the full folder structure to the share interface.
Not a problem at all, as long as you inherit from cm:content or cm:folder.
This is configurable in the Settings panel of Fred.
This is not supported in Fred 1.2. We are planning this for one of the next releases. Any project requirement are welcomed.
Workflow is not yet addressed in Fred. But is it one of the next domains we can cover. Initially we will present the action related to workflow.
Fred works with any Alfresco authentication system, when the user provides his own username/password in Fred. Integrated windows authentication is running with Windows XP+NTLM at customers. Other combinations need untesting.
Lotus notes support is on the radar but not yet planned on the Fred roadmap.
The setup executable contains a silent modus, just add the option /S. The silent installer won't check if .NET 3.5 is available or that Fred is currently running.
Back to Fred main page