In this release of OroCRM we improved our integration with OroCommerce by integrating sales opportunities and quotes.
In this release, we have started integrating CRM pipeline management and forecasting tools—i.e. Leads and Opportunities, and Commerce sales fulfilment tools—RFQs, Quotes, and Orders. Please note that this is just the first step that will be followed with deeper integration in subsequent releases.
We have created a new Opportunity management workflow that allows sales reps to create quotes directly from the Opportunity view. All quotes that were created within a specific opportunity will be displayed in a corresponding section on its view. The sales rep can manage quotes from this grid in the same way they can manage them from quotes grid—i.e. edit, delete, or expire a quote.
This function will only be available if the opportunity is related to a Commerce customer; otherwise, the workflow will behave exactly like the standard Opportunity management flow that existed in previous versions.
We have split old Business Sales Channel statistics widget into two: Lead statistics and Opportunity statistics. This change allowed us to enhance the resulting widgets with advanced filtering capabilities that were introduced for the Forecast widget in 1.10. Quick filters by territory were also added.
In order to allow users who either do not have permissions to edit a report, or do not want to edit the report but still need to see the up-to-date results, report builder now allows to:
The admin can now specify the maximum number of records in a segment. This can be useful if you need to choose only the top X records from a segment, e.g. only the top 100 of your customers by their lifetime sales value.
If you have sufficient permissions, you can easily add events for other users at Calendar view.
In this release of OroCRM we focused primarily on improvements of our Sales pipeline. We improved multi-channel versatility of Opportunities as a general sales tracking tool by making them available for all types of customers. We also made possible to record sales in multiple currencies by adding multi-currency support to Enterprise Edition.
On the more down-to-earth level we introduced a portfolio of safety minded features that will allow administrators to secure access to the system with the variety of tools. Workflow capabilities got a major expansion—multiple parallel workflows are now a reality.
Finally, in the anticipation of upcoming growth of Oro product family, we have prepared OroCRM to seamlessly integrate with OroCommerce when it is released later in January.
Leads and Opportunities became the first application of the new OroPlatform feature management capability. Enabling or disabling them in your instance no longer requires manipulations with the Sales channel—from now on it is as easy as checking a box in the system configuration. When enabled, each feature will bring in not just the menu item with the grid of records, but also all the necessary paraphernalia: workflows, reports, dashboard widgets, etc.
Note that Sales channel remains available in the system, but now its functions are reduced to enabling Business Customers and controlling their grouping at the Account view. Also, Channel relation is no longer considered necessary for both Leads and Opportunities and will not appear in new 2.0 installations. If you migrate from 1.10/1.12 EE, the field and relation will remain but will be converted into extended relation, so you can easily remove it in entity management.
We have made Opportunities truly universal sales tracking tool by removing the restriction of a mandatory Business customer relation. From now on, Opportunities can be related to any customer type—Magento customers, Commerce customers, or any other type of customers that might be introduced by third-party extensions.
Opportunities can also be related directly to Accounts. This is the most basic and most natural setup of OroCRM if you don’t need to track multi-channel sales, or just want to keep things simple. And you can always enable the additional complexity of multiple customer channels later when the need arises.
The functionality of Account lookup control at Opportunity create/edit form has changed accordingly:
Note to developers: Please read the Sales Customer Relations section in our documentation to learn how to introduce your own customer types that will properly work with Opportunities.
Known issues:
You can relate your sales opportunities to any customer now, so it is only natural that you will be able to see the full history of deals with the particular customer at their view. And, staying true to our 360° Account view promise, we’ve added the complete list of all related Opportunities to the Account view as well.
The final point in growing ubiquity and convenience of Opportunity management is the ability to create it from any customer view, or from Account view. The action is available under More Actions dropdown, and the Account field will be prefilled with the Account or customer you’re creating it from.
This feature allows the sales reps to check the history of the deals with the particular account directly on the Opportunity view, so the crucial pieces of past wisdom and experience that might make the difference between a successful sale and the failed one become more readily available.
This feature is optional and can be turned on or off in the Opportunity section of CRM configuration. It’s enabled by default.
Recurring calendar events are no longer read-only—now you can create and edit them straight in the OroCRM calendar. Multiple recurrence patterns are supported; all events in the series can be managed on their own, creating exceptions when necessary; Outlook integration has full support for events created and edited in OroCRM.
We have also expanded functionality of invitations—now you can invite everyone to your events, not just OroCRM users. Invitation is done by email address, and an external invitee will also receive a RSVP notification—obviously, without the link to OroCRM’s calendar.
Task status is now clearly displayed on its row in the activity list, letting you to know what’s going on at a glance. And you can start or stop the task progress, or mark it as complete straight from the row actions—all task workflow transitions are just one click away, so you no longer have to navigate back and forth between the task and its context record.
Task contexts are now displayed in the Tasks grid, allowing you to quickly identify what this particular task was about. All contexts are clickable, so you can easily navigate to them.
Tags can now be grouped in taxonomies, and every taxonomy can be assigned with a distinctive color, to let you clearly identify different group of tags that might serve different purposes.
This feature has been contributed by our community member Samuel Denis-D'Ortun (@sadortun) – thank you!
Marketing-related features, such as Marketing lists, Campaigns, and Web Tracking can now be turned on and off in system configuration.
Marketing-related OroCRM bundles: MarketingListBundle, CampaignBundle, and TrackingBundle have been combined in a separate package that was moved to its own repository. The package is included into OroCRM by default, but can be removed if necessary. Note that our marketing extensions—MailChimp and dotmailer integrations, and Abandoned Cart Campaign extension are dependent on this package, so they won’t work if it’s been removed from the application.
In this release of OroCRM we focused primarily on improvements of our Sales pipeline. We improved multi-channel versatility of Opportunities as a general sales tracking tool by making them available for all types of customers. We also made possible to record sales in multiple currencies by adding multi-currency support to Enterprise Edition.
On the more down-to-earth level we introduced a portfolio of safety minded features that will allow administrators to secure access to the system with the variety of tools. Workflow capabilities got a major expansion—multiple parallel workflows are now a reality.
Finally, in the anticipation of upcoming growth of Oro product family, we have prepared OroCRM to seamlessly integrate with OroCommerce when it is released later in January.
Leads and Opportunities became the first application of the new OroPlatform feature management capability. Enabling or disabling them in your instance no longer requires manipulations with the Sales channel—from now on it is as easy as checking a box in the system configuration. When enabled, each feature will bring in not just the menu item with the grid of records, but also all the necessary paraphernalia: workflows, reports, dashboard widgets, etc.
Note that Sales channel remains available in the system, but now its functions are reduced to enabling Business Customers and controlling their grouping at the Account view. Also, Channel relation is no longer considered necessary for both Leads and Opportunities and will not appear in new 2.0 installations. If you migrate from 1.10/1.12 EE, the field and relation will remain but will be converted into extended relation, so you can easily remove it in entity management.
We have made Opportunities truly universal sales tracking tool by removing the restriction of a mandatory Business customer relation. From now on, Opportunities can be related to any customer type—Magento customers, Commerce customers, or any other type of customers that might be introduced by third-party extensions.
Opportunities can also be related directly to Accounts. This is the most basic and most natural setup of OroCRM if you don’t need to track multi-channel sales, or just want to keep things simple. And you can always enable the additional complexity of multiple customer channels later when the need arises.
The functionality of Account lookup control at Opportunity create/edit form has changed accordingly:
Note to developers: Please read the Sales Customer Relations section in our documentation to learn how to introduce your own customer types that will properly work with Opportunities.
Known issues:
You can relate your sales opportunities to any customer now, so it is only natural that you will be able to see the full history of deals with the particular customer at their view. And, staying true to our 360° Account view promise, we’ve added the complete list of all related Opportunities to the Account view as well.
The final point in growing ubiquity and convenience of Opportunity management is the ability to create it from any customer view, or from Account view. The action is available under More Actions dropdown, and the Account field will be prefilled with the Account or customer you’re creating it from.
This feature allows the sales reps to check the history of the deals with the particular account directly on the Opportunity view, so the crucial pieces of past wisdom and experience that might make the difference between a successful sale and the failed one become more readily available.
This feature is optional and can be turned on or off in the Opportunity section of CRM configuration. It’s enabled by default.
The integration with OroCommerce will provide seamless experience as both applications will work as a single one. All combinations are supported—it will be possible to install OroCommerce over existing OroCRM instance; add OroCRM to existing OroCommerce instance if you were using its beta; or finally install both applications as a single package.
Either way, integration between OroCRM and OroCommerce will yield you a single application with a combined menu and shared organization backbone: users, business units, roles, and organizations if you’re an Enterprise customer.
When OroCommerce is integrated with OroCRM, Commerce customers are treated in the same way as other customers—Magento or Business. Their data and business transactions are displayed at the Account view, and their activities are added to the Account’s activity list. Finally, the LTSV metric will be calculated for Commerce customers based on the orders placed, and
When a customer is created or edited at backend, the Account can be specified directly. When a new customer is self-registering at frontend, a new Account of the same name will be created automatically, so addition of CRM to Commerce won’t affect customer experience.
If you install CRM over existing Commerce instance, new Accounts will be automatically created for all existing customers. Note that you can specify the strategy of Account creation under System configuration > Integrations > CRM and Commerce. Two options exist: create a single account for the entire customer hierarchy, or create a separate account for every customer regardless of their parent-child relations with other customers. You can change this option at any time, and customers will be re-related to accounts accordingly.
As already explained above, CRM Opportunities can now be related to any customer type, including Commerce customers. This allows Commerce sales representatives to track their ongoing deals and forecast future revenues for all sales that are or will be conducted via the Commerce website by relating the Opportunity to the respective Commerce customer record.
This feature allows administrators to impose mandatory complexity demands to users’ passwords. It is possible to configure the following restrictions:
As part of this feature we’ve introduced two sets of user statuses to better reflect the current state of the user’s account.
Status for state of the user account. This is a system status that determines general validity of the user’s account and usually corresponds to state of user’s employment within an organization. It has two options: Enabled (used to be Active) and Disabled (formerly Inactive) and can be manipulated directly at User edit page or via Enable User/Disable User actions.
Authentication status provides information of the validity and applicability of user’s login credentials. In Community Edition it has two options: Active and Password reset, and in Enterprise Edition a third Locked option is added. This status cannot be manipulated directly and is changed as a result of administrator’s or user’s own actions, such as resetting the password or getting locked after unsuccessful logins.
This feature allows external developers or administrators to log into system under someone else’s account using oro:user:impersonate console command. Impersonation is the best way to examine the system behavior when you’re trying to reproduce an issue reported by the user.
All changes made by impersonated users are marked accordingly in the Data audit, allowing you to clearly identify possible abuse of this feature.
Workflows got a major revision in this version of OroCRM.
We have lifted one of the most basic restrictions for our workflows, allowing you to have multiple active workflows for the same entity at the same time. The use cases for multiple workflows are endless: alternative sales workflows that the sales representative can choose when they decide how to deal with an opportunity; parallel sales follow-up and order fulfillment workflows for a placed order; you name it.
As it is now possible to have multiple active workflows on the same record, we had to redesign the workflow widget, so it can display states and let you run transitions of multiple workflows at once.
Two or more workflows can be marked as mutually exclusive so once one workflow from the exclusive group is started, others can no longer be run. This feature serves the use case of multiple alternative flows, e.g. sales flows: You have many to choose from, but once you’ve made your choice, you no longer need the alternatives.
Please note: so far, this feature can only be utilized by developers.
Multiple active workflows for different tasks is a great function, but it brings additional complexity which many of the system users won’t really need. For example, if you have a sales follow-up flow and a support flow for your Magento order, chances are, the support representative don’t even need to know about the sales rep’s work, and the sales rep could be aware about the state of problem resolution, but should not intervene into it.
In order to fine-tune user’s access to workflows we have added workflow permissions to Role management interface, allowing you to configure:
Application menu can now be managed and configured from the UI. You can adjust the menu for the entire application, or create personal menus for every user if you want to.
Filters on data views (grids and the Kanban board) can now be hidden to save screen space. Click the funnel button in grid controls to toggle them on and off. Note that applied filters will still be visible above the grid, so you can identify which records you’re supposed to see.
Import and export of data will no longer block you from using the system—it will now be performed in the background, so you can continue working even when you are importing very large files with millions of records. Once the file is imported or exported, you will receive an email notification with report on import results or a link to download the exported file.
All email-related functionality can now be easily disabled if you are not using it and don’t want it to get in the way. A simple checkbox under System > Configuration > Email configuration will disable My emails page, user and system mailboxes, email activities, email-related widgets, and all email-related settings in both user and system/organization configuration. You can turn off emails for the entire system, or a specific organization.
Note that this feature does not affect transactional emails, such as notifications about password reset, or invites to calendar events. Email notifications will stay in place, and email templates will still be available for editing. Email marketing campaigns also won’t be affected.
SMTP provider for transactional, marketing, and other emails sent from OroCRM can now be configured explicitly in email configuration. You can choose a popular provider, such as Mailgun or Sendgrid, or set up your custom server.
System SMTP provider will also be used for outgoing user emails if their personal mailboxes weren’t configured. However, when set up, user’s mailbox SMTP settings will override the system SMTP provider.
You can now create rich HTML templates in OroCRM by simply pasting the HTML code prepared by designer into template editor. To make sure no tags are stripped, turn off HTML purifier in Email configuration settings for your system or organization.
Email attachment size can now be limited in the system configuration (set to 50 MB by default) to reduce DB growth and adverse effects on application performance.
Recurring calendar events are no longer read-only—now you can create and edit them straight in the OroCRM calendar. Multiple recurrence patterns are supported; all events in the series can be managed on their own, creating exceptions when necessary; Outlook integration has full support for events created and edited in OroCRM.
We have also expanded functionality of invitations—now you can invite everyone to your events, not just OroCRM users. Invitation is done by email address, and an external invitee will also receive a RSVP notification—obviously, without the link to OroCRM’s calendar.
Task status is now clearly displayed on its row in the activity list, letting you to know what’s going on at a glance. And you can start or stop the task progress, or mark it as complete straight from the row actions—all task workflow transitions are just one click away, so you no longer have to navigate back and forth between the task and its context record.
Task contexts are now displayed in the Tasks grid, allowing you to quickly identify what this particular task was about. All contexts are clickable, so you can easily navigate to them.
Tags can now be grouped in taxonomies, and every taxonomy can be assigned with a distinctive color, to let you clearly identify different group of tags that might serve different purposes.
This feature has been contributed by our community member Samuel Denis-D'Ortun (@sadortun) – thank you!
Marketing-related features, such as Marketing lists, Campaigns, and Web Tracking can now be turned on and off in system configuration.
Marketing-related OroCRM bundles: MarketingListBundle, CampaignBundle, and TrackingBundle have been combined in a separate package that was moved to its own repository. The package is included into OroCRM by default, but can be removed if necessary. Note that our marketing extensions—MailChimp and dotmailer integrations, and Abandoned Cart Campaign extension are dependent on this package, so they won’t work if it’s been removed from the application.
• 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
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.
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.
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.
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.
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.
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.
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.
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.
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:
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.
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
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.
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:
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.
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:
Kanban Board is a special data view for Opportunities that allows Sales reps to move an opportunity through the pipeline by simply dragging its card between status columns.
Kanban Board appears as a set of columns that match Opportunity statuses. Every Opportunity record is represented by a card that contains its name, budget, probability, related Account, owner, and created at date. Opportunity name is clickable and leads to the view page; and the top right corner of a card contains the three-dot action control where other record actions such as Edit and Delete can be found.
The board can be filtered and sorted by any field except for the status. Only the top 5 cards are displayed in every column by default; more (again, up to 5 cards in each column) will be loaded when you scroll the board down. The number of loaded cards and the total number of cards is displayed on top of the board.
Kanban Board is available only when Opportunity entity has no active workflow (the "full freedom" option). In this case, a switch between grid and board views will appear next to grid controls. When you switch between grid and board views all filters and sorting remain applied. The board view can be saved in the same way the grid view is saved; view type will be shown as an icon next to the its name in the list of data views.
We've developed Kanban Board as the universal data view that can be applied to any entity, but for start have turned it on only for Opportunities. More will follow in the future releases!
To ease the task of looking for the necessary dashboard widgets in the ever-growing list we've added instant search to the Add Widget dialog. Simply start typing the name of the widget you're looking for and the widget list will be filtered to match your entry.
We're also highlighting the widgets you already have on the dashboard.
We redesigned and standardized the ownership filter and expanded it to most out-of-the box widgets. The control now allows to filter data in widget by individual owners, whole teams (business units), or entire user roles.
Another great addition is the ability to filter by the current user or their team—this option allows the administrator to set up a single team dashboard where every user will see their own data.
We've also redesigned and standardized the date range filter in widgets. It now allows you to simply choose a convenient reporting period, such as "today," "this week," or "this quarter," choose if you want to compare to the previous period, and be done with it! The option for a custom range also remains available in the list.
This filter makes widget configuration as versatile as our segmentation—indeed, we've built our entire filtering tool into widget config! Click on Advanced Filter to expand it, and then drag and drop the filtering query of any complexity. Filter opportunities by naming convention or by budget size; apply filters to the number of contact attempts, or to the state of residency of the related contact—whatever are borders of your sales pipeline, you now can filter it out and follow it in the widget!
Please note that this filter is available in the Forecast widget only. We will expand it to other widgets in the future releases.
To match the grown number of opportunity statuses and to make it capable of handling many more we've decided to make bars in this widget horizontal. In addition to that, we've made possible to exclude unnecessary statuses from the chart, and to display data in either total budget of opportunities, or their count.
Similarly to the previous widget, the list of lead sources being displayed in this widget can now be truncated—however, they're not hidden entirely but combined under Other pie slice, so the percentage remains correct (you should always have the whole pie!). Opportunities with no leads, or with no lead source are also accounted for. And this widget can also be configured to display data calculated from total count of opportunities or from their combined budgets.
These are two simple widgets that display a list of lead or opportunity records for quick access. By default both display only open items that are owned by the current user, but can be configured to display any necessary data.
A long-requested feature by our community and customers alike is finally available in OroCRM! Now every user will be able to custom-tailor the application to their own taste by overriding system and organization configuration in the following areas:
Please note that parts of email configuration—mailbox setup and personal signature—were moved from Edit User page.
User configuration page can be accessed via button on the user view page or via My Configuration item in the My User menu.
Field-level ACL is the biggest improvement to our ACL engine to date. It works exactly like you expect, allowing the administrator to control user access (Create, View, Edit) to certain entity fields.
With this feature administrators will be able to configure access to Opportunities in such a way so that sales representatives will be able to see their co-workers' opportunities without the budget, status, or probability fields. Such limitation of access both helps to protect sensitive data and increase sense of competition.
To manage ACL on the field level the administrator has to turn it on in the respective entity configuration first. Within this release field-level ACL will be available out of the box for Account and Opportunity entities only, but we will add support for more entities in the future.
We would like to thank our community members Trustify (@trustify) and Ivan Shakuta (@ishakuta) who have contributed significantly to the development of this feature.
Role view page has been added to the system to give both administrators and non-administrators a way to read capabilities of a certain role without having to edit it (and risking making undesired changes).
Clone option for roles will save OroCRM administrators a great deal of time and effort when they need to create a new role—instead of starting from a clean slate they would be able to reuse an existing role and only make the necessary adjustments.
As the number of entities and system capabilities in OroCRM grows, so does the Role management page. To reduce the effort required for role management and maintenance we have developed a new UX for the Edit Role page.
The most noticeable improvement in the new UX is the functional separation of entities and capabilities. Four main domains—Account management, Sales, Marketing, and System capabilities create clear structure for all ACL items and helps the administrator to check if permissions for a certain role indeed match functions of its user.
The new UX is also scalable for unlimited number of actions that are introduced with this release on the platform level. Access level for every entity action can now be configured within a single row. All action permissions for a single entity can be set to the same value with a single "mass" action, allowign the administrator to save time, especially in situations where access has to be disabled completely.
This Save button option will come in handy when you want to create multiple records in succession—it will save you a lot of time by eliminating the need to go back and forth between grid and record views.
All numeric values can now be filtered by a range query, i.e. between X and Y or not between X and Y. All other filter options are now spelled out in plain words instead of mathematical operators for better legibility.
Contents of an entity grid can now be exported to Excel file (.xlsx) in addition to standard CSV export. Please note that it applies to Export Grid functionality only, not the generic entity export.
We want to thank our community member Sufijen Bani (@sbani) who had contributed the PR for this feature.
While not directly related to Sales rep experience, this feature nevertheless will save a lot of time and effort for anyone whose job requires making and logging a lot of calls. Call duration can now be typed in in a human-friendly format, such as 1h 2m or 12m 45s. Fractions are also permitted, e.g. 1.5m will be correctly processed as 1 minute 30 seconds.
You can now preview images attached to either entity records or emails directly in the application, eliminating the need to download them first. Click on the image to open a gallery where you can view all images attached to this particular entity record or email thread. The gallery also allows you to zoom the image in or out, download the image, or print it.
In the same way we allow to manage Lead and Opportunity status directly, we've exposed Task status for direct manipulations in case the workflow is turned off, giving you the "full freedom" task management option if you prefer it.
Email threads accessed from My Emails page will now have pagination controls for quick navigation between threads, similarly to other entities.
My Calendar can now display recurring events. Although they cannot be managed from the UI just yet, they will be properly rendered when synced with an external source, such as Outlook.
Calendar events can now display guests that are not OroCRM users. Although such guests cannot be managed from the UI just yet, they will be properly rendered when synced with an external source, such as Outlook.
Similarly to changes in Lead requirements, we've eased the list of mandatory Contact fields. Now a Contact can be created with just one of the following fields:
Similarly to Accounts, you can now merge up to 5 contacts into a single record. The user interface is the same: select the desired contacts in the grid with checkboxes, then click Merge button in the list of mass actions, and finally specify the master record and choose output values or merge strategy for every attribute.
In addition to full deactivation of Magento channel that hides its data from UI completely, we now allow to deactivate only the integration—in this case the data will remain accessible (e.g. as an archive) but will no longer be synced with the Magento store. When the integration is re-activated, the data is fully re-synced according to the sync strategy.
If Magento web tracking is turned on, you will now find a handy tracking data widget on both Magento Customer and Account views. The widget displays a timeline of recorded events (page visits, items added to cart, and checkouts entered) and a list of metrics such as total site visits, days since the last visit, most viewed page, and so on.
This is a new widget for eCommerce dashboard that displays
How can I help you explore Laravel packages today?