Releases: oroinc/platform
4.1.0-rc2
Updated dev.locks
Release Notes
List of fixed issues and improvements
- Improved email sync performance
- Fixed edit recurring event exception on activity list triggers error
- Fixed upgrade from 1.12 to 2.0 version due to Data audit migration
- Fixed upgrade from 1.12 to 2.0 version due to Translations migration
- Fixed Menu settings could be changed by editing menu settings of another org
- Fixed incorrect behavior of displaying recurrent events after deleting one from the chain
- Fixed exception on emails global search
Release Notes
List of fixed issues and improvements
- Fixed notice is occurred on each navigation action
- Fixed incorrect handling of multi-select type fields on any view page
- Fixed impossible to install Oro products
- Fixed Business Units may be removed with mass delete
- Fixed async import processor fails if file was removed
- Fixed PHP error during setup Chart Designer in Report manager
- Fixed a lot of duplicate messages for update email owner associations
- Fixed export functionality
- Fixed system Email Mailbox doesn't convert to Lead
- Updated Job Execution documentation in the Oro Book
- Added complex index to data audit table
- Fixed error with namespace after upgrade app from 1.12 to 2.0
- Fixed Calendar Events created via Outlook Add-in are forbidden for creator
- Fixed resetting grid filters after changing their current state
- Fixed 500 Internal Server Error when creating user via API
- Fixed Incorrect behavior of ESC button during the inline editing of date fields
- Fixed error when reloading grid after ACL changes
- Fixed Email feature disabling works incorrectly for organization
2.1.0
In this release of OroPlatform we’ve focused on improvements to workflow capabilities, parallelization of import & export jobs, and documentation of all our API resources.
Workflow capabilities
Workflow variables
Variables are configurable workflow attributes that can receive their values from external sources, or provide a default value specified by the administrator in workflow configuration at the UI. Workflow variables can be of different types, ranging from simple scalars to entity instances.
The most straightforward use case of variables is make previously hardcoded parameters in transition and step conditions configurable by the user. If you have a workflow that only allows a transition T if some attribute A of entity B doesn’t exceed the value X, turn X into a variable—so then this threshold can be easily changed from the UI when needed. You can also pass the variable value from other sources, or, in our example, make X different depending on which user is working with the entity.
Reuse existing entity forms in workflow transitions
Developers may now easily reuse existing CRUD forms of various entities in workflow definitions. This saves effort and simplifies maintenance—if the edit form is changed later, all workflows that reuse it will also change accordingly.
Start a workflow without entity record
A workflow can now be started by an event trigger even if no workflow entity record exists yet—allowing you to utilize workflows for background entity creation.
UI for transition destination configuration
Transition destination, i.e. the page the user will be redirected to after they submit the transition form displayed as a separate page, can now be configured in the workflow management UI.
Parallelization of import & export jobs
Import and export jobs are now parallelized between RabbitMQ consumers. This allowed us to greatly reduce execution times for large files: hundreds of thousands of records can now be imported within mere hours, and exported in about 15 minutes or even quicker.
Use external storage for I/E files
In order to reduce load on Oro application server, an external service such as Gaufrette can be used for storage and processing of import & export files.
Web API
Documentation of all system API resources
We have documented all API resources of both OroCRM and OroPlatform so you can clearly understand what is the purpose of each resource, its parameters, and understand the details of the returned value. This will help you to use our API in the proper way and create optimal integrations with other applications.
Batch request and response for REST API
We have created actions for batch API requests and responses: get_list, update_list, and delete_list. These requests are asynchronously processed via MessageQueue.
They will serve as a cornerstone to more efficient integrations and data synchronization jobs that we will ship in future releases.
Other fixes and improvements
Entity management
Unidirectional relations can now be created via UI
Layouts
Debug data collector for layout actions
All layout actions that can’t be performed are now shown in profiler.
Performance
ContentProviderManager is now loaded lazily to improve performance
A file cache has been added to LocalizatonManager
Improved views initialization
Release Notes
List of fixed issues and improvements
- Fixed unexpected connections to DB server
- Fixed Scroll and clicking doesn't work on "Manage filters" of "Add Context Entity" grid popup
- Fixed Configuration fields with enabled option 'Use default' available for edit
- Fixed Selectors are being available after saving the settings despite the related checkboxes
- Fixed Wrong email settings (login/password) passed to user configuration
- Fixed Default Datagrid filter type produces js error
- Fixed Submit form of activity might "Nesting level too deep" fatal error in in_array function
- Renamed HasElements and NoElements from oro_workflow.expression to oro_workflow.condition
- Fixed Broken all select controls in embedded grids
- Fixed mistake in error message when email was not delivered
- Fixed when user deletes multi-select options, excessive comma is still displayed
- Fixed mistake in error message when deleting 1 marketing list record
- Fuixd Add some message that clearly informs that user that he needs to specify at least one recipient while creating Email Notification Rule
- Fixed incorrect validation for Name field while creating new entity
Release Notes
List of fixed issues and improvements
- Optimized unexpected connections to DB server
- Fixed Installation instructions produce a non-working installation
- Fixed Emails from system mailbox are not displayed in My Emails
- Fixed Consumer fails on export-import step
- Fixed "Recent emails" widget produces fatal
- Fixed Message queue consumer does not use refreshed doctrine metadata cache
- Fixed Default Datagrid filter type produces JS error
- Fixed Titles columns of first imported file carry over to following imported files
- Fixed Get rid of creation of new entities in get operations
- Fixed Notification rules are lost after migration to 2.0 version
- Fixed Viewing Custom Report with chart on a mobile device goes into a loop
- Fixed Submit form of activity might "Nesting level too deep" fatal error in in_array function
- Fixed Impossible to display workflow transition with comments field
- Fixed Impossible to select relation field in workflow transition attributes
- Fixed Configuration edit page is refreshed on after server validation of form is failed
- Fixed Grid export works incorrectly with empty columns that having same names
- Fixed Task information dialog doesn’t display html
- Fixed Mistake in error message when email was not delivered
- Fixed When user deletes multi-select options, excessive comma is still displayed
- Fixed Incorrect error message when importing wrong file format
- Fixed Incorrect workflow items migration from 1.12 to 2.0
- Fixed Incorrect Reminders Namespaces migration from 1.12 to 2.0
- Fixed Incorrect Data Audit class namespaces migration from 1.12 to 2.0
- Fixed Incorrect migration of Navigation items from 1.12 to 2.0
- Fixed Cannot choose organization when creating new user if there are few organizations in the system
Release Notes
List of fixed issues and improvements
- Fixed update schema for custom entity without fields
- Fixed upload Translation File does not work on languages management
- Fixed incorrect Email Messages Id and UID usage in IMAP integration
- Fixed Tag records namespaces after migration to 2.0 version
- Fixed web installer fails on wrong DB configuration
- Fixed wrong email settings (login/password) passed to user configuration
- Fixed Cron scheduled workflow transitions are not working
- Fixed not accessible all girds with workflows
- Fixed possible break of on calendar widget
- Fixed notification rules are lost after migration to 2.0 version
- Fixed deadlocks causing queries during consumer work
- Fixed Embedded forms does not work after migration to 2.0
- Fixed Incorrect workflow items migration from 1.12 to 2.0
Release Notes
List of fixed issues and improvements
- Fixed corrupted installation on replicated MySQL server
- Added handling for SwiftMailer SMTP transport exception
- Fixed Deleted Extended Entity causes Cache Warmup crash.
- Fixed custom field is not synchronized for entities with Redis configuration.
- Fixed configure system mail box configuration
- Removed unused oro_calendar.exception.form.type
- Fixed Update from 1.9.3 to 2.0.1 is broken
Release Notes
List of fixed issues and improvements
- Fixed Corrupted installation on replicated MySQL server
- Fixed "(%sign%)" instead of base currency symbol in the "Change history"
- Fixed incorrect display import forms errors
- Fixed Deleted Extended Entity causes Cache Warmup crash
- Fixed Emails and Thread Emails are displayed in duplicate
- Fixed Custom field is not synchronized with Redis cache
- Fixed Impossible to configure system mail box for some shared hostings
- Fixed Broken functionality of configurable export
- Fixed outdated documentation in OroWorkflowBundle
- Fixed Cron scheduled workflow transitions are not working
- Fixed System mailbox thread disappears
- Fixed Update from 1.9.3 to 2.0.1 is broken
- Fixed Pin doesn't delete when entity has been deleted
- Fixed Invalid interruption of AMQP(RabbitMQ) transport
Release Notes
List of fixed issues and improvements
- Fixed Emails and Thread Emails are displayed in duplicate
- Fixed System mailbox thread disappears