ssossossosso

Release Notes

The Open-Source OroCRM for Commerce and the OroPlatform

OroPlatform 1.9.0-RC1

New features – Platform.

Inline editing in grids

This feature allows you to quickly process large amounts of data by editing record values inline in the grid.
Using the feature is simple: hover the mouse over a grid cell. If it is editable, it will be colored yellow and an “edit” icon will appear in its top right corner. Click this icon or double-click the cell itself to get into the Edit mode. In this mode, the cell you’re editing will turn into a field or control that is “soaring” above the grid with two Apply and Discard buttons on its right. Both the row and the column header of a cell you’re editing will be highlighted with yellow to help you identify the record and the attribute you’re editing.
If you press Enter, your edit will be applied and you will move to the next row. If you press Tab, you will move to the next editable cell on the right. Shift+Enter and Shift+Tab move you correspondingly upwards and leftwards.
The input is validated immediately, and if validation fails, the editing control won’t move you will see an error message (e.g. “This value is not a valid email address”).
Known issues: So far this feature is limited to grids of Accounts, Contacts, Leads, Opportunities, and Tasks in the default OroCRM setup.

Grid column management

Grid columns are no longer set in stone by configuration file; the user may now add or delete columns and change their order of appearance. To do so, click on the Table settings button—the list of all columns available will be displayed. Drag them up and down to reorder columns in the grid, check or uncheck to make them appear or disappear. Changes are applied on the fly, and after you have achieved the view you want, save it as a grid view to access it later.
Developers may configure which columns are available for the user, and make some columns mandatory to display (i.e. non-manageable).

New UX for Tags

In this release we have completely overhauled the look and feel of Tags, and made them universal.
Firstly, Tags are a separate entity feature, akin to activities, and should be enabled or disabled in the entity management—direct relations to the Tag entity are no more. Enabling tags will automatically add them to the edit & view forms of an entity, and will make the Tags column available in the entity grid. They can be enabled or disabled for every entity, including custom ones.
The user experience of tag manipulation has also been improved. Tags can now be edited inline everywhere—in grids and on the view pages, allowing users to tag read-only records such as Magento customers in one-way sync setups. We have also redesigned the look and feel of tags, and they look much, much better now.
In reports or segments, Tags column can be added as an entity “field”, allowing the user to list all the record tags in one row without grouping.
Known issue: Tags can no longer be manipulated on the Edit forms. We will address this in the future releases.

Automated REST API for GET requests

We have started to automate entity APIs in order to speed up platform development and improve the dev experience. After this release, all GET operations for all entities will be available via REST API straight out of the box, no extra development needed. In addition to availability of all entities for GET operations, the new API provides:

  • Application of User ACL to all resources
  • Possibility to control entity availability via API
  • Possibility to control entity fields and relations availability

The new API is based on JSON API implementation. The old API remains available with URLs unchanged (/api/rest/{version}/…). The new REST API URLs will start with /api/{version}/….

Performance improvements

We have addressed application performance in the variety of ways, and have earned improvements in page loading and app response times ranging from 10–15% up to 50%. In particular, we have addressed application scaling, optimized performance of entity configs and worked on base HTTP requests. Also, we have removed deprecate option sets.

Other improvements

  • Apply range filters for numerical fields in grids
  • Manage field tooltips from the UI
  • Override calendar-view.js in customizations