Releases: oroinc/platform
Release Notes
List of improvements and fixes:
- Login performance and OwnerTree cache issue. Fix performance of OwnerTreeProvider
- Unique key with no Name created
- Integrity constraint violation during IMAP synchronization
Release Notes
List of improvements and fixes:
- Integrity constraint violation during IMAP synchronization
- Delete confirmation continuously pops up
- Email processing create duplicates
- Calendar Event and Task Reminder Email Displaying Incorrect Time Zone
- Email-body sync getType error
Release Notes
List of improvements and fixes:
- Unexpected escaping of twig variables in Email Templates
- Impossible to use Country ISO fields for Reports
- Text-filter should work in Edge
- User view page loaded more than 30 seconds on large data
- Entity pagination not displayed after a selecting a record from grid
- Filter by Source in Leads is not working correctly
- Implement select2 controls on the editing Role page
- Big entity thru datagrid generates fatal error
- Exception is occurred during upgrade from old version
- Impossible send email from entity
- Detach dropdown to parent dialog instead body and dont use disposed element
- Use camelCase logic for extended fields
- Refactor My Emails grid to be usable with several thousands and more emails
- Apply default filters from config
- Deleted fields are available in Reports&Segments
- Fix problem with nested entity validation
- Wsse headers can be used twice
- Fix problem with IMAP sync for messages with subject longer than 500 symbols
- Impossible to add link into email signature
- List of BU doesn't displayed according ACL on the freshly added Forecast widget
- Lost data during import from CSV
- Conflict in *ToMany relations
- Duplicated entities' labels in Entity Manager
- Cannot configure any widgets on dashboard if the system language is French
1.10 Release plans
In this release of Oro Platform we will focus on development of new Web API. Workflow capabilities, role management experience, and general application performance will also receive attention.
New features
New Web API
JSON-based Web API that is automatically created based on entity metadata. The following methods are supported:
GETPOSTPATCHDELETE
Workflow capabilities
- Time trigger for workflow transitions
Role management
- Clone roles
Other features & improvements
- PHP7 support
- Symfony 2.8 support
- Behat functional tests
- Mass notifications to application users via CLI
- Embedded forms without iframe
- In-app image preview
- Clone action
- Save & new option on record creation
TBD
- Manage record attachments via API
- Multiple workflows for an entity
- Field level ACL configuration
- Refreshed role management UI
- Personal application configuration
- Integration with message queue (RabbitMQ)
Release Notes
List of improvements and fixes:
- Fixed performance issues related to User View page
- Fixed Integration sync finished with Lock timeout for organization table
- Fixed filter is not working when French locale is used
- Fixed Invalid backend datetime during attachment select
- Fixed no way to save the set of filters on grid
- Add ability to import Tags from CSV
- Add ability to filter by month and day without year
- ...and more
Release Notes
List of improvements and fixes:
- Removed possibility to generate an API key for other users of the system while logged in as a user that should not have permission to perform those actions.
- Fixed attachments of some special types that were not shown in comments
- Added possibility to export and import select fields using labels
- Fixed issue with date filters in reports/segments. Now possibility to use weeks, moths, years, days for date variables in reports and segments has user friendly UI.
- Removed dependency on symfony/icu
- Fixed incorrect validation messages in import dialog
- Added possibility to save set of filters in the grid view
- Fixed filter by custom multiselect fields in the grid
- Fixed missing "Update" button in some grid filters
- ...and more
Release Notes
List of improvements and fixed bugs:
- Updated packagist repository to secured URL
- Added possibility for creating entity through context property path
- Added polyfills for Math functions
- Added console command to set application url
- Added ability to import Tags from CSV
- Refactored email API Search query
- Fixed deletion of 100k emails
- Fixed performance of User view page
- Fixed button Add Context on the email view page
- Fixed contains operator for search in case PostgreSQL
- Fixed calendar notifications email templates
- Fixed User email templates
- Fixed inline select2 editor opens only one time in Firefox
- Fixed uniqueness of the Grid View name is verified globally
- Fixed Javascript error when trying to edit autoresponse rule for system mailbox
- Fixed checkboxes with short grids
- Restored table row selected color
- Fixed Impossible to add Gmail account to user
- Fixed filter when French locale is used
- Fixed email Invitation doesn't use value from Application URL configuration setting
- Fixed ManyToOne relation from Contact entity to Country…
- Fixed JSON type is supported starting PostgreSQL 9.2
Release Notes
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
Release Notes
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
Release Notes
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