Discover upcoming and recent changes in Nuxeo Studio.
Actions menu in Designer will be renamed as
Buttons, and the related options as follows:
Button: Choose this option to create a button using configuration only.
Custom Button: Choose it to create your own button element using code for extensive capabilities.
Icons will change too to reflect the options more clearly.
+ button in Designer will be refreshed at the same time, to be more explicit:
- Tooltips are shown on the option you choose,
- When only two options are available, clicking the
+button directly leads you to the one that is the simplest to use.
Studio Designer will show contextual help on click so that you can copy/paste code samples and click on documentation links.
- Aggregates for a page provider will provide default values, for instance on the date format.
- Contextual help will be improved to guide you on options that had no previous explanation, be simpler to understand otherwise and provide samples.
- Quick filter name will be shown in the user interface when no translation has been defined for it.
Compatibility for Nuxeo Studio with Polymer 3 to keep our technical stack up to date.
More information about upcoming changes is available in our bug tracking tool.
It is possible to define aggregates on the sub-fields for a blob property. It can be used to provide search options to find files of a specific type, or based on the file size for example.
range aggregate types in combination with the
length property for the file size, the
terms aggregate with the
mime-type property for the file type.
These options work with any blob property, multivalued ones as well.
- In workflows, resolution actions is renamed as task buttons (NXS-5084).
- In workflows, "exclusive node" is renamed as "Follow only first true transition" (NXS-5085).
When creating a Create, Edit or Import layout, the title field is automatically set as required to keep consistency with the default Web UI behavior.
When creating a layout for a workflow task, fewer properties are generated to avoid information duplication with the one exposed in Web UI.
file:contentsub-fields are exposed when defining an aggregate: to configure searches on file size or file MIME type for instance.
ecm:ancestorIdis exposed in both predicates and aggregates: can be used as an alternative to
ecm:pathwhen you know the document id instead.
BETWEENoperator is exposed in predicates for dates, float and integer numbers.
More information about released changes and fixed bugs is available in our bug tracking tool.
|May/June 2019||More consistent layouts, new options in page provider screen.|
|April 2019||Support to select all schemas in page providers, improved support for workflow graph definition.|
|March 2019||Easier search configuration, override Web UI default configuration, select your default theme in a click.|
|February 2019||Introducing the Layout Blocks and Git Status bar as well as an easier folderish documents configuration.|
|January 2019||Studio Designer interface improvements.|
|December 2018||Faster layouts configuration.|
|November 2018||Firefox support for Studio Designer, performance improvements, drag and drop schema properties in Studio Designer and information about your subscription status.|
|October 2018||Develop faster with Git access and Quick Switcher, JSF to Web UI migration early access release.|
|September 2018||Introducing Git access for Studio Designer.|
|June 2018||Application definition supports private package selection, introducing token management for enhanced security.|
|May 2018||Selecting dependencies makes their content automatically available for use in Studio. There are several other usability improvements in Studio Designer that make life easier.|
|April 2018||This release makes it easier to create a document type when using Web UI.|
|April 2018||You can now configure your project as a real application containing dependencies on any public addon without having to make a dedicated custom bundle. This release also brings improvements to our Maven integration.|
|March 2018||A REST API to trigger Studio releases, a revamped editor for page providers results and the ability to declare constraints for workflow variables and node variables.|
Feel free to let us know how we could make Studio better for you!