Releases: oroinc/platform
Release Notes
List of fixes and improvements
- Added possibility to extend optional-validation-handler on form level
- Fixed IMAP Storage warning
- Added handling for doctrine exceptions in job execution
- Fixed check rules of finding email origins to be synchronized
- Added handling of hanged email origins
- Fixed handling of wrong folders or email messages from outlook.office365.com
- Fixed incorrect grid display of custom views
- Fixed slow download languages on some environments
- Improved search reindex performence
- Added progress for search reindex command
- Fixed "Connect to MailChimp" button is not shown for custom entity
- Added truncate email body to SQL instead of do it on php side
- Fixed The email folder is disabled on some temporary issues with IMAP connection
- Added Scalable Business unit selector
- Fixed Email reply does not work in case system MailBox is configured
Release Notes
List of fixes and improvements
- Disabled dynamic Web Tracking by the default
- Added possibility to clear email attachments for 1.9 version of the OroPlatform
- Added JMS Job Queue Errors logging via monolog
- Added "Except" filtering query for option set fields in data views
- Fixed update Client Secret in IMAP OAuth configuration
- Fixed broken inline editing for 'relation' and 'multi-relation'
- Fixed the email folder is disabled on some temporary issues with IMAP connection
- Fixed PHP segfault during authorization with Opcache
- Fixed parse time string with extra spaces during email sync
- Fixed impossible to Save as default Grid View
- Fixed XSS vulnerability in the enum grid column
- Fixed Email XSS vulnerabilities
- Fixed General templates are not available for Maintenance Notifications
- Fixed error while syncing emails with emoji (UTF8mb4)
- Fixed UI dropdowns issues in inline editing
- Fixed untranslated jsmessages when using not "en" locale parameter
- Fixed Magento Import does not work with minimal 512Mb required memory
- Fixed search result is'not cleared in Add Widget if use IE control
- Fixed Extend field creation. Added missing validation on Storage Type
Release Notes
List of fixes and improvements
- Added limit for attachment size within IMAP/EWS emails
- Fixed Broken labels for grid-related actions and UI controls
- Fixed Slow queries after login
- Fixed Inline editing impacts grid performance
- Fixed Incorrect behavior of inline editing menu selection
- Moved phones and emails from relationships to attributes
- Updated monolog/monolog package version at least to 1.17
- Restored phone cell functionality
- Fixed target path after login
- Fixed Datagrid header broken for some pages
- Fixed Month view in Calendar does not display end time.
- Fixed Incorrect migrations for missing fields System Calendar
- Fixed issues related to text-util.js
- fixed ecxeption on email templates form
- Fixed Incorrect default filter status for enums
- Fixed double submitting Embedded forms
Release Notes
List of fixes and improvements
- Fixed creating and editing event for system calendar doesn't work
- Fixed could not share new grid
- Fixed A plural alias for "Extend\Entity\EV_Prod_Inventory_Status entity not found
- Added additional action buttons to the role view page
- Enabled ping request in websocket
- Fixed error is occurred during tracking events processing
Release Notes
List of fixes and improvements
- Fixed broken labels for grid-related actions and UI controls
- Fixed A plural alias for "Extend\Entity\EV_Prod_Inventory_Status" entity not found
- Added possibility to paste HTML content into email templates
Release Notes
List of fixes and improvements
• fixed OroCRM loading fails with non UTF-8 characters in emails
• Improved performance of My Emails grid with default 100 records per page
• fixed of Symfony 2.8.10 bug
• Added support comma for Call duration
• Added default translations to select2 extend
• Fixed Incorrect table to class map in EntityMetadataHelper
• Datagrid rendering improvements
• Added force Resync parameter for IMAP synchronization command
• Fixed filter does not work if two or more conditions are applied…
• Fixed JmsJob queue slow opening
• Fixed status filter breaks sorting for saved Grid view
• Fixed fullcalendar AMD module name
• Enabled field level ACL for new API for POST and PATCH
• Fixed error of migration ConvertPhoneNumberInPhone during upgrade to last version
• Fixed not possible to create lead via REST API
• Fixed field level ACL doesn't affect the Workflows Transitions
• Fixed Load page performance degradation
• Fixed unexpected slow HTML Sanitiser
• Refactored get email body text
• Fixed relative referenced dependency prevents override
• Fixed Emails are not coming through icon once Synced- Yahoo
Release Notes
List of improvements and fixes:
- fixed SQL error on Dashboard page
- fixed Email is not marked as primary during the creation process
- fixed Call Duration (lettering) becomes red when it has a wrong value
- fixed Incorrect processing muliparts emails with mixed content
- fixed Email body sync is hung
- fixed Email Validation Fails
- fixed Unable to login via username because of conflicting primary email of other user
- fixed PHP errors during IMAP sync
- fixed Integrity constraint violation during emails sync
- fixed Filter does not work if two or more conditions are applied to the same field
Release Notes
The most significant change in Oro Platform 1.10 is the new web API. We have developed very powerful Action concept. And finally, we kept pace with the new developments by adding support of PHP 7 and Symfony 2.8.
New web API
In course of 1.10 release we have developed a completely new automated Oro Platform API that is based on entity metadata. This means that after you create an entity, all of its fields and relations become immediately available via API—so you can get their contents, create new records, and update and delete existing records immediately.
The new API is based on JSON API specifications. It supports all standard HTTP methods for a RESTful service:
GETPOSTPATCHDELETE
Both GET and DELETE methods support massive operations with options for filtering and sorting the set of records. GET also supports field configuration, so you can limit the request with the specific set of fields. API methods for sub-relations are supported too. This means that you are able to manipulate the exact record(s) from the collection of related entities—e.g. only the specific contact of an account.
Documentation for all API methods is (mostly) automatically generated. It can be accessed via the sandbox at http://YourOroPlatformAppURL/api/doc/rest_json_api.
The new API is disabled by default for backwards compatibility reasons. You have to enable it explicitly for every new entity.
The old API is deprecated, but will still be available for at least the next two release cycles to give you the time to transition to the new API. We recommend doing it as soon as possible, as none of the new features support the old API.
Actions
Actions are configurable sets of operations to be executed by the system. Every action is a combination of three components:
- A trigger—an event that determines what starts an action. Triggers can be UI buttons, entity-related events, or time-related events.
- A data selection query that determines a dataset to which action will be applied.
- A function that in turn is a combination of elementary operations with system entities. Functions may also include conditions, call another functions, and ask the user to supply necessary data via forms.
The definition of an Action is very similar to workflow transition, and indeed they have the same roots. However, Actions are more powerful and versatile—they can be launched and executed not only by the user, but also automatically by the system. The most significant advantage of Actions over custom "buttons" is that the entire Action definition is stored in the .yml config file and requires no PHP code. This means that in the future Actions can be fully configured from the UI.
So far, Actions exist only by themselves and can be utilized to perform "individual" tasks. Available Action examples in Oro applications are conversion of Lead to Opportunity in OroCRM (the UI-triggered action), or auto-expiration of a Quote in OroCommerce (the time-triggered action). In the future, however, we plan to allow to reuse Actions as workflow transitions, thus giving them even more versatility.
PHP 7 compatibility, PHP 5.4 discontinued
Since the release of PHP 7 numerous application tests indicated that upgrade to this version not only helps streamline application development but also brings in significant performance gains in page response times and memory consumption. This release opens these benefits to the entire Oro Community by introducing compatibility of Oro Platform with PHP 7.
To make it possible to write code that is portable between PHP 5 and PHP 7 we've added new symfony/polyfill-php70 dependency. We also decided to discontinue support for the older PHP 5.4 version. The 5.4 version will remain supported in older versions (1.9.x and below) during their current life cycle, but is not supported from this release onwards.
Symfony 2.8 support
In this release we have also upgraded the Oro Platform to support the LTS version of Symfony – 2.8.
Application unbundling
We continue our effort to unbundle our Oro applicatins and introduce various functional bundles as part of the platform. In this release, both TaskBundle and CallsBundle were moved to separate packages that are now available on their own.
CLI notifications for users
System administrator can now send notifications to all application users via command line interface or from the UI. This feature is useful for notifications about planned shutdown for maintenance or other system-wide announcements.
Release Notes
List of improvements and fixes:
- Email ACL does not work
- Properly process broken email via IMAP protocol
- Cleanup unexpected data from akeneo batches tables
- Selector fields have broken layout
- Changed IAMP sync command to create separate job for each origin
- Cannot send emails from "Recently used" list
- To add abbreviation for overseas military addresses
- Open action of Select2 dropdown does not close other dropdowns
- Make asynchronous Sync Emails processing
- Calendar stuck when event was deleted
- Reset filter after switching from 'Is Empty'
Release Notes
List of improvements and fixes:
- Added scalable Business unit and Owner selector to improved filters performance
- Added organization component in organization structure
- Fixed "Choice" inline edditing in grid
- Fixed duplicated emails for the Google Integration
- Fixed mass deletion for huge data
- Removed unexpected Grid pager from export to csv
- Removed not optimized counts of unread emails after Login
- Fixed emails bodies loading during Email Widgets initializing