← Back to Index

7.1 Release Notes

For Developers

Constraints

Nuxeo Core Repository now accepts the definition of XSD constraints on document properties. Those constraints can be for example number and text formats, text length, a list of accepted values, a numeric range. They are based on XML Schema facets. A sample constraint for expressing the fact the field value should be an email would be:

    
<xs:element name="email">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:pattern value="[a-z0-9!#$%&'*+/=?^_`{|}~-]+(?:\.[a-z0-9!#$%&'*+/=?^_`{|}~-]+)*@(?:[a-z0-9](?:[a-z0-9-]*[a-z0-9])?\.)+[a-z0-9](?:[a-z0-9-]*[a-z0-9])?*" />
    </xs:restriction>
  </xs:simpleType>
</xs:element>

  

Once constraints are defined, validation can be enabled/disabled at different level by means of the extension point activations of the org.nuxeo.ecm.core.api.DocumentValidationService component. Nuxeo Studio will allow constraints definition in the future.

Field Reference

A reference system has been added. It allows to define a field (usually a string field) as a reference to an other object. A resolver is used to be able to load the referenced object when needed. Here is the way to define a constraint:

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
           xmlns:ref="http://www.nuxeo.org/ecm/schemas/core/external-references/"
           xmlns:nxs="http://www.nuxeo.org/ecm/schemas/example"
           targetNamespace="http://www.nuxeo.org/ecm/schemas/example">
  <xs:element name="favorite">
    <xs:simpleType>
      <xs:restriction base="xs:string" ref:resolver="documentResolver" ref:store="id" />
    </xs:simpleType>
  </xs:element>
</xs:schema>

And here is a way to get the referenced object.

DocumentModel referenced = document.getObjectResolver("schema:favorite").fetch(DocumentModel.class);

CMIS 1.1 Secondary Types Support

Dynamical facets are now exposed as CMIS secondary types.

Workflow Module Improvements

A lot of work has been done on the workflow module for improving graph readability: designer in Nuxeo Studio now benefits from grid snapping for positionning the nodes. It is also possible to edit the position of the transitions, while in the past it was 100% controled by Studio. This is specifically interesting in situations where there are many transitions coming out from one node, with looping, etc. We also changed the look and feel, with rounded corners and new set of colors. We hope you will like it! Finally, we changed the position of the "exclusive node" checkbox, it is now displayed in the Transition tab, for more consistency.

File Metadata Read-Write

A new module in the Nuxeo Platform (nuxeo-platform-binary-metadata)is dedicated to reading and writing metadata on files, like Office metadata, XMP metadata, EXIF, PDF, etc. This new addon provides a configurable service that makes it very easy to map metadata of the files to metadata of the document, and let Nuxeo Platform maintain this mapping when the data is updated. The service also providers several helpers and operations to use it in different manners. You can read the documentation to discover more of this great new platform feature.

Computed Picture Views

The Picture Views definition, i.e. the list of resolutions/format that are systematically computed when uploading a Picture, is no more hardcoded. It is now easy to add new views to a picture, depending on the document type, the user properties, etc. We wrote a how-to to let you discover how to contribute your own views.

Aliases for Automation Operations

It is now possible to rename an operation without breaking the compatibility using the alias system.

MVEL Expressions Debugging

MVEL expressions are now evaluated in automation traces while only the object name was appearing before. This makes it easier to debug some complex chains.

Page Provider Name is Part of the Content View State

The serialized state of a content view now holds the page provider name, which can be useful for building and running the query associated to a given content view in a client application.

Command Line Converter and Converter Operation

A command line converter has been added to the platform. This converter allows to reference a declared command line (contributed to the command line extension point) for doing a conversion. An operation has also been added so as to call any converter and convey parameters. That way, in two contributions you can very easily operate advanced transformations from Automation.

PDF Signing Operation

A new operation makes it possible to sign a PDF directly from an Automation chain. This operation is part of the nuxeo-platform-digital-signature module.

Tagging Operations

A set of operations has been added for being able to tag or remove tags on a document.

New Branding

The Branding feature in Studio has been simplified to customize easily the new colors of Nuxeo Platform 6.0+.

InfoView Action Category and Other New UI Elements

Some new UI elements were added in 6.0 and are now available in Studio for configuration, like the INFO_VIEW actions category (the popup from the Search tab) and some new widgets that are used on that view.