The goal for this release was to extend the scope of the capabilities of configuration with Nuxeo Studio - and to ensure the usability of Nuxeo Studio to meet your integration projects.

We are happy with the results and are looking forward to getting your feedback! You can now implement document workflows, add custom traceability in any automation chain, let the user download files you created in chains, leverage the vocabulary labels to automatically build title of documents or update whatever metadata.
Furthermore, starting from the soon-to-be released Nuxeo DM 5.3.2, every automation chain you do in Nuxeo Studio will be exposed as a REST webservice - and Nuxeo Studio allows you to filter the access to those webservices.
Finally we did a lot regarding the usability and industrialization of the Nuxeo Studio development process: Versioning control of your configuration project, project version tagging, configuration project history, integration with Maven...

For testing this release, I used the scenario of tender management: implementing features such as worklow validation for tender pieces, publishing of the tender, downloading of all the published tender pieces of documents at one time, filling audit table for statics... Even though this is the third release I've worked on, I am impressed and surprised of how quickly you get the configuration done! Many thanks to the Nuxeo Studio team, which is already on track for the 1.4 shot, with exciting new features - can't wait to tell you more about it, stay tuned!

While the official release note is available - release note contains full details -we provide some key highlights and items to note here:

Main new operations:


  • Create task: You can now create and assign tasks to users from an operation chain. The "create task" operation is very configurable: you can choose which date, which comment, which directive you want, and also the assignment behavior. You can also compute, in the automation chain, the list of persons you want to assign the task too. Last but not least, you can bind automation chains to accept or reject events, thus designing a complete document workflow process.


  • Get users and groups: This new operation resolves all the users and groups having a given permission on a document. This is very useful, in conjunction with the previous "Create task" operation.


  • Get Principal emails: This operation returns emails of users having a given permission on a document. Can be used in conjunction with the "Send email" operation to send custom notifications.


  • Log Event in Audit: Thanks to this operation, you can now feed audit trail with custom events. If you provide a particular validation chain, you can add this operation in the end so that you add an entry in the document history, to log the execution of this particular chain.


  • Download file: This user interface operation enables you to provide buttons whose effect is to download a file in the end, that file containing a specific document, or a zip of a document selection, or a pdf transformation, or whatever you need!



Rest binding for Automation chains


Operations and automation chains are now bound to a REST API. As a direct result, you can use Nuxeo Studio to implement a custom REST API for you project - with not even one line of java code! See About the automation rest service for more information on using those webservices.


Better usability of Nuxeo Studio in integration projects



  • Projects are now under source control system: We integrated Git so that it is possible to commit configuration states, restore previous configuration states, tag specific versions of your project, be able to realize difference between versions and see history of the configuration. You will now be able to control what you sent in qualification, what is in development, etc... Also, it will make it easier to work as a team around a Nuxeo Studio project, as you can easily follow what happens.


  • Nuxeo Studio now integrates with Maven. If your project needs side eclipse development in addition to your Nuxeo Studio configuration, you can declare the Nuxeo Studio plugin as a dependency of your global development project, using Maven:


    <dependency>
    <groupId>nuxeo-studio</groupId>
    <artifactId>myproject</artifactId>
    <version>1.0</version>
    </dependency>
    </code>


    The "1.0" version corresponds to a tag on your Nuxeo Studio project.
    When building your project, Maven will automatically download from the Nuxeo Online Services platform your customization.


  • You can leverage System properties, for instance, to differentiate values depending on whether it is a dev, qualification or production platform. Nuxeo EP allows system properties values, which are properties defined in "properties files" in the config folder of your Nuxeo instance. A sample property file is the "notification.properties" where you store the url of your server to include it in email notifications. Now all those properties are loaded in Content automation context, and thus can be used in scripting instructions.



Various improvement/fixes:


Filter elements by path, make the "summary tab" visible for folderish types, make the "create documents " appear, be able to translate a vocabulary ID in its label (thanks to a scripting function), and make it possible to configure the fixed part of the advanced search...


Useful links about Studio: