Thursday, March 24, 2011

Released LogicalDOC Outlook AddIn v1.0

The version 1.0 of the LogicalDOC Outlook AddIn is now available!

Today, many commercial and operational communications transit to and from organizations via email.
To improve the knowledge of these informations and business processes is necessary to make these informations available so they are accessible and usable without having to rewrite or duplicate each time.

Using this plugin you can store your emails in logicaldoc for sharing  and make the informations contained in them more accessible via the logicaldoc full-text search future.

Emails are saved in the original Outlook .msg format, so you can then download them from logicaldoc and view them in Outlook, attachments are also saved along with the email.

The second feature of the plugin is to save the attachments.
In some cases, in fact the relevant information is not the mail, but in the documents it carries.
Therefore it is unnecessary to save the whole email, while it is very useful the possibility to save the associated files.

The last feature in this first release is the ability to select directly from LogicalDOC, thanks to a simple function of browsing, one or more documents to be attached to an outgoing email.
This way you can send documents directly from Outlook, without having to access in advance and download documents locally.

LogicalDOC Outlook Addin is an optional plug-in available for the commercial editions of the software starting from version 6.0.2

For more information see the Outlook AddIn page on the website of the product.

LogicalDOC Menu

Configuration: default folder for email archiving

Result of importing email

Open Attachments browser
LogicalDOC Attachments browser
Bookmark and Share

Wednesday, March 2, 2011

Why we choose GWT

LogicalDOC moved from a traditional user interface based on scripting technology like JSP/JSF to the modern and powerful GWT framework coming from Google. Up to now, we are proud to offer the Document Management System with the more advanced user interface available today.
This new approach allowed us to drastically reduce the code for the presentation layer and limit the knowledge needed to develop, since we dropped a lot of complex enterprise technologies to start to develop in pure Java language.

LogicalDOC 6.0 GWT GUI (click to enlarge)

When the experience counts

It doesn't matter how good is your product, the only thing your users will look is the user interface. After all each electronic artifact exists to serve human people business processes. So the way in which your users interact with your system is the most important aspect and you have to take care about your users experience.
A graphical user interface based on GWT (Google Web Toolkit) technologies will assure you these following goals:
  • High response times, since all the GUI is executed in the client side
  • High experience, equal to a traditional desktop systems
  • Compatibility with all used browsers
The best thing that GWT will do for you is to completely decouple the presentation layer (completely executed in the client) from the business and data layers (completely executed in the server)

GWT role in an Enterprise Application

Approaching the development of an enterprise-class application like LogicalDOC, involves the development of a large number of similar widget and forms for data manipulation. These elements are presentation layer components, and here are two general approaches to develop them:
  1. Creating of separate classes which represents visual component for each form.
  2. Creating universal visual components and widgets that can be composed together
If you try to follow the first way you probably will have a lot of code to produce and a lot of development time. You may agree that the correct approach is the first one and GWT simply adopts the Object Oriented paradigm allowing you to reuse components and take benefit from concept like inheritance and polymorphism.
So when building a user interface with GWT, it is possible to use generic components, significantly reducing the resources for the development of the presentation layer. In addition since GWT is pure Java you will not be required to use senior development resources, you just develop in standard Java.
Bookmark and Share