Release Notes

List of fixes and improvements

• Fixed broken date time widget after creating Opportunity with new Contact through dialog
• Fixed impossible to Save as default Grid View
• Fixed Not found entity "Magento Customer" errors during Magento sync
• Fixed wrong migration for loading roles for Task entity

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 PHP Notice: Array to string conversion on Magento order view page
• Fixed Incorrect default filter status for enums
• Fixed double submitting Embedded forms
• Fixed upgrade of tenants with large amount of Sales data
• Fixed Leads export functionality

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
• Fixed unsecured information in Magento check error message
• Fixed RFM parameters saving triggers errors

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 incorrect Magento API requests during attempts
• Fixed Magento Order Sync action does not sync order information
• Fixed field level ACL doesn't affect the Workflows Transitions
• Fixed duplicated threads on Account view
• Fixed Load page performance degradation
• Fixed unexpected slow HTML Sanitiser
• Refactored get email body text
• Fixed B2B customer, address removal by CSV import update
• Fixed B2B customer import, State full name, association
• Fixed relative referenced dependency prevents override
• Fixed Emails are not coming through icon once Synced- Yahoo

Release Notes

List of improvements and fixes:

• Fixed Customer entity short format usage
• Cards on the Board view have different heights

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
• Magento order Sync data leads to run full channel synchronization
• 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'
• Fatal is occurred on Magento Customers page with restricted Integration entity
• Fatal is occurred during Magento Orders import
• Unenable to removed address from B2B customer
• Can`t set default group for guest customer

Release Notes

In this release of OroCRM we have focused on improvements to Sales pipeline in its entirety from Lead to Opportunity management. We have also significantly upgraded Role management capabilities and UX and added numerous improvements to almost every feature of OroCRM. Due to advancements in Oro Platform, application performance has also improved significantly.

Sales pipeline management

Clear naming

B2B Channel type and B2B Customer were renamed to Sales Channel and Business Customer respectively to give the end user more clarity about their purpose.

Direct sales pipeline management without Sales Process entity

To streamline sales management UX we have deprecated Sales Processes and removed from the default Sales channel setup.

Instead, the Sales representative can now manage Leads and Opportunities directly, from their respective view pages, or even from entity grids via inline editing. Both entities' statuses are available for direct manipulations (see below), although in case of Opportunity some statuses might be restricted by a workflow.

Migration note: Sales Processes are removed from the default setup only in fresh 1.10 installs of OroCRM. If you upgrade from 1.9.x version they will remain active and none of your data will change until you explicitly decide to turn them off. To do so, simply remove the Sales Process entity from your Sales channel setup. Then activate the Opportunity Management flow if you want to use it, or leave it inactive if you prefer the full freedom option (more on this below).

Note that even if you decide to stick with Sales Processes, all UX improvements for Lead and Opportunity management will be available. However, we strongly recommend to move away from them, as they will be completely discontinued and eliminated in future versions of OroCRM.

Lead management improvements

Open Leads as a default grid view

We've created a new Open Leads grid view and have made it default for Leads grid. The reason for this change was to focus the Sales rep on leads that require processing instead of already processed leads. All Leads view remains available out of the box.

Quickly create Lead in a single form

This feature allows the Sales rep to quickly create a Lead with any bit of information they have at their disposal. First name and Last name are no longer required, and Lead name remains the only mandatory field—this applies to both manual lead creation and to CSV import.

Lead creation and edit forms were also redesigned to better structure lead information.

Multiple emails, phones, and addresses for a Lead

Now Leads can be created with multiple email addresses, phone numbers, and postal addresses similarly to Contacts, giving Sales representatives more versatility and flexibility in lead management.

Manage Lead status directly

As stated above, Lead status can now be edited and changed by the user, allowing them to quickly mark a Lead as qualified or disqualified.

The administrator can adjust the list of statuses and their order in Entity configuration. Note that three default statuses cannot be removed, but can be renamed.

Disqualify Lead action

To speed up the lead management we've added Disqualify action to the lead view page. This action changes the Lead status without additional dialogs, saving the Sales rep a few clicks.

Convert Lead to Opportunity action

This is a new action that allows the Sales rep to quickly create an Opportunity and, if necessary, an Account and/or Contact along the way. All records are created within a single form that is pre-filled with the Lead data:

• Opportunity name is taken form the Lead name.
• An Account name is taken from Company name. The system will search for matching Account or Business customer, and will create new if the search was unsuccessful.
• Contact field will be pre-filled if the Lead is related to a Contact. Otherwise, the new Contact will be created along with the Opportunity, and instead of Contact selector, the form will contain a "New Contact Information" sub-form, so the Sales rep may review the new contact data and adjust it if necessary. All contact information will be taken from corresponding Lead fields.

Continue with Lead activities at the Opportunity page

To ensure that no conversation context and history is lost after you qualify a Lead to Opportunity, all activities recorded towards the Lead are also associated with the Opportunity created from it. The old activities remain associated with the Lead as well, but all new activities recorded towards the Opportunity after it has been created won't appear on the Lead view.

Opportunity management

Quickly create Opportunity in a single form with no popups

We have improved Create Opportunity form so it can be filled in quicker and in more convenient way, saving up a great deal of Sales rep's time.

To do so, we've allowed to create a related Contact and an Account and Business Customer pair by simply typing in their desired names into respective controls. A list of matching values will still appear, but with an option to create a new record. Note that Account field represents a combined relation to an Account via Business Customer, so both records will be created at once. Matching values will also be searched for across both entities. (If Business Customer name is different from Account name, it will be displayed in parentheses.)

Note that the new controls still allow you to create a related customer or contact record in a popup via + button if you want to enter all their data—typing in the name is not mandatory, but rather a quick and convenient option.

The form was also redesigned to better structure and present Opportunity information

• All text fields—Customer need, Proposed solution, and Additional comments—were converted to rich text.
• Close date was renamed Expected Close Date so it can be used for revenue forecasting.

Manage Opportunity status directly and tie it to Probability

As with Leads, Opportunity status is also available for direct manipulations on Edit forms and in grids. However, to further improve Sales rep user experience, we also added the ability to connect it to Probability field, so that it will change accordingly to a predetermined default value. This is the default list of statuses and their related probabilities:

Status	Probability
Open	0%
Identification & Alignment	10%
Needs Analysis	20%
Solution Development	50%
Negotiation	80%
Closed Won	100%
Closed Lost	0%

The probability will change along with the status in create and edit forms, workflow transition forms, and even when the status is changed inline in the grid. The user will still be able to manually change the probability if they want to, but please note that in this case the default values will no longer be applied after status change. If a certain status has no default probability value, the probability will remain unchanged after this status is applied.

System administrator can change the list of statuses and their related probabilities in CRM > Sales Pipeline > Opportunity section of System and Organization configuration. (The list of statuses can only be managed at the system level.) Please note that three statuses—Open, Closed Won, and Closed Lost—cannot be removed, although they can be renamed; assigned probabilities for Closed Won and Closed Lost statuses are also fixed.

Two options for Opportunity management: workflow or full freedom

We want to provide our users with as much flexibility in opportunity management as possible, and to achieve that in 1.10 release we have supplied two options.

Full freedom option is turned on by default. In this case, all Opportunity fields are exposed for editing, so Sales reps may mark an opportunity closed as won by simply editing its status in the grid. This option allows the most flexibility and convenience in data modification. However, this also means data integrity is not enforced, and the Sales rep bears full responsibility of avoiding mistakes such as open opportunity with the close reason and close revenue. We recommend this option to smaller businesses that don't have a lot of opportunities or a lot of sales representatives, as in this case advantages of added convenience will overweight the possible mistakes in the data.

Workflow can be turned on by the administrator. Our default workflow ("Opportunity Management Flow") consists of three steps: Open, Won, and Lost. When the workflow is active, it applies restrictions to opportunity edits; however, these restrictions are less severe than ones imposed by the Sales Process workflow, when Opportunity couldn't be edited at all. The restrictions are as follows:

• In Open step neither Closed Won nor Closed Lost statuses can be selected. Close reason and Close revenue fields are also blocked. This applies to both Create and Edit forms.
• In Won and Lost steps Account, Status, Probability, Budget amount, and Expected Close Date are also blocked in addition to Close Revenue and Close Reason.

The workflow option is designed to maintain a certain degree of flexibility in opportunity management while also ensuring the integrity of sales data. We recommend this option for larger organizations with big amount of opportunities in the pipeline in which case data consistency is more of an issue.

Please note, that when you enable a workflow over existing opportunities, you will have to start it for every record manually via special Start workflow transition. This only makes practical sense for open opportunities.

More out-of-the-box grid views for Opportunity

Similarly to Lead management, we've added a bunch of new grid views and changed the default to Open Opportunities. The rationale of this change was the same: to focus Sales reps on the work to be done instead of already completed work. Here are views we've added:

• Open Oppo...

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 unenable to removed address from B2B customer
• Fixed mass deletion for huge data

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