The new version 4.0 strengthens even more's qualities in intranets and extranets with its new functions in the Groupware and Workflow domains:

• A completely redeveloped function: vacation management
  (See Vacation requests in OVIDENTIA V4)
• A new function: Directories
  (See The function directories integrated in OVIDENTIA V4)
• The possibility to define complex workflow processes to validate published content (articles, comments, files) or vacation requests
  (See Validation WorkFlow: General Overview)
• An improved diary function:
  • Handling of recurrent events (with the possibility to modify/delete one occurrence or the complete set)
  • Possibility to choose the default view of the calendar (month, week, day)
  • Possibility to choose the default presentation of the view by week (lines or columns)
  • Simultaneous view of multiple agendas
  • Possibility to plan an event in multiple agendas at once
  • PM/AM mode, time scale
• Possibility to filter content by language (sections, categories, topics, articles, FAQ)
  (See Content filtering by language in OVIDENTIA V4)
• Choice between flat mode and hierarchical mode to view contributions to a forum
• Possibility to notify users that have read rights of the creation or modification of an article
• Possibility to notify users that have read rights of the upload of a new file or a new version of a file in a shared folder of the File Manager
• New File Manager independent from the notion "Group": it is now possible to create as many shared folders as needed while keeping the possibility to define for each of them the access rights you want to give them (download, upload, modification)
• Possibility to make new registered users of the portal automatically members of a given group
• Possibility to insert graphics in FAQ using the WYSIWYG editor
• Update to version 1.62 of php mailer
• Support for authenticated SMTP

OVIDENTIA V4.0.1 will be available on Monday March 31st 2003.

This technical status brings:

• An "experimental" version (one that you can experiment with) of OvML (Ovidentia Markup Language);
• Corrections for most of the bugs found after the release of version 4  earlier this month;
• Improved security of the product.

From Monday on a topic dedicated to OvML will be available that will allow  you to discover this new technology. Articles describing new functions and  illustrating usage examples will progressively extend the topic.

OvML still has an experimental status and can still be changed  drastically. Therefore we thank you in advance for every feedback you can  give us on your experiments so that we can look forward to the release of  a future stable version of OVIDENTIA with OvML.

If you are already familiar with OVIDENTIA , you probably are surprised by the look of the home page on this new version of the site published in accompaniment of the release of OVIDENTIA Version 4.

This page is the result of a first usage of a new technology inside OVIDENTIA : the OvML (for Ovidentia Markup Language).

And you can create content for yoursite in any language you like. And whatever the language in which your content is written, it will be available for each user that has the necessary access rights to see a given piece of content. And if you put some content in three different languages on anportal (or different portal sites sharing the same database), a visitor will see the content in the three languages.
The only solution available to separate content was a multi-site installation without shared databases.

From OVIDENTIA V4 on we add a new function: content filtering by language.

Presentation of the new "Vacation requests" function integrated in version 4.

An overview of the new "directories" function integrated in version 4 of

The validation WorkFlow (or approval process) integrated inallows you to configure the approval mechanism for published content in your portal in order to reflect the approval process in your organization.

This article brings you:

• The history of this mechanism in past Ovidentia versions
• General principle
• Basic functions to build a validation schema