Release Notes

Tasks

This feature allows you to create tasks and assign them to users. Tasks assigned to you can be easily accessed via built-in Task List sidebar widget that provides a list of your open tasks in chronological order, and highlighting the ones that are overdue.

Improved UI for launch of the Sales Process workflow

Workflows are an integral part of the OroCRM experience and of every Business Application. Prior to this release, workflow creation and configuration could only be done by developers using the configuration files. With this release we introduce the first generation GUI tool that allows you to create new Workflows and manage some of the features of custom workflows and reduces the dependency on developers. This version includes the following features:

• Access the list of all workflows that currently exist in the system. Note that "System" or built-in workflows cannot be edited, but can be cloned.
• Activate and deactivate workflows.
• Create a completely new workflow or clone and adjust an existing one.
• Specify steps of the workflow and their relative positions in the workflow
• Add transitions to the workflow

For workflow transitions, the following customization is possible:

• Specify transition form (popup or the whole page) and entity attributes that will appear on this form.
• Customize transition button: change its label, icon and style.
• Provide a warning message to the user.
  With future releases we will continue enhancing this feature and adding more functionality to allow a user to fully manage Workflows

Release Notes

Refactored Flexible Workflows

The idea is to simplify creation and management of the complex workflows that have more than one related entity (e.g. in B2B workflow these are Leads and Opportunities) by adding a restriction that a workflow can have only one main entity (e.g. new B2B workflow called Sales Activity). Note that the Sales Activity entity does not have any value by itself (it even cannot be created directly from the grid) and is meaningful only in the context of the workflow, when there's a connection to a Lead and/or an Opportunity.
Note that the functionality for this release is not complete: The workflow can only be started from the existing Lead or Opportunity which have to be created in advance. The complete vision for this workflow anticipates more elaborate form for starting transition that will allow users to start flow either with an existing Lead/Opportuinity record, or to create such entity on the fly.

Embedded forms

This feature allows developers to create embedded forms that can used in third-party websites in order to collect data directly into OroCRM and have workflows around the data collected. These forms can be set up to maintain the look & feel of a target website.
The package for embedded forms contains two examples of such forms: generic Contact Request form and a Magento Contact Request form that uses Magento CE CSS in its appearance. The latter form also has an OroCRM workflow attached to data records generated from it, serving as an example of the use case for embedded form data collection.

Account merging

Users will now be able to merge up to 5 account records at a time into one account, with a simple and easy-to-use GUI tool. This tool allows user to specify master record (i.e., the record where all other accounts will be merged to), and to choose the source for every attribute of the resulting record. For the relation attributes (like Contacts or Tags) a strategy – replace or append – can be specified.

Upgrading

We have added the ability to upgrade existing installations of OroCRM. To upgrade follow the instructions in upgrade.md file. This process will be automated in future releases.

Release Notes

Improved Workflow

Interaction with the workflow has been redesigned, providing more immediate access to workflow step transitions and view.
The entity that is part of the wokrflow (determined by workflowItem and workflowStep attributes) will no longer feature the "Workflow items" grid in the respective section of its view form, but will instead incorporate workflow step information directly to the entity view. This information includes display of the workflow progress – the current step, the preceding steps and the subsequent steps – and buttons for available transitions. This workflow information is displayed on top of the entity view, and the entity information is displayed below.
The workflow step can no longer be viewed on its own.

Improved Dashboard

This feature adds two funnel charts to our Dashboard: B2B flow chart and B2C flow chart, that relate, respectively, to Opportunity flow and Abandoned shopping cart flow.
The chart visualizes the overall progress of the respective workflow: the funnel shows what is the total value of entities that are in various steps of the workflow, and the outcome of the funnel shows the total value of entities that have reached the "final" step of the flow since the first day of the current quarter. E.g., for the B2B flow the chart will show as the funnel total budget amount of opportunities in "Qualify" step, then total budget amount of opportunities in "Develop" step, and as the outcome of the funnel there will be total budget amount of lost opportunities and total close amount of won opportunities.

Performance improvements

Magento integration performance has been improved in terms of both capacity and speed. Now it is possible to download up to 0.5M records in 13–15 hours

Other improvements

Synchronization of the channel can now be launched directly from the channel view.

The responsive cell design has been applied to Contact View screen. Now if the page is re-sized, the columns count will be reduced from 4 to 2, and then to 1, in order to keep columns not too narrow.

Release Notes

Magento data import: Customers, Shopping carts and Orders

Added possibility to import customers, shopping carts and orders from Magento stores. To import data user should create channel under System -> Channels and schedule data synchronization which will be performed in background. Imported data can be found in Customers -> Channels, Sales -> Orders -> Channels and Sales -> Shopping cart -> Channels.

Details of implementation can be found in \Oro\Bundle\IntegrationBundle.

B2C Sales Flow

Added B2C flow for imported Customers, Orders and Shopping carts:

Abandoned Shopping Cart Flow
This workflow is used to process shopping cart from external sources (e.g. from Magento) and to try to convert it to opportunity.

Order Follow Up Flow
This workflow is used to process external orders (e.g. from Magento) and contact customers for feedback.

Call view window

Window with all information about a call can be opened directly from call widget grids on new dashboard, contact, account and user view pages

Basic dashboards

Developers can create dashboards using configuration file dashboard.yml where in section “dashboards” a new instance can be declared with list of widgets declared in section “widgets”. Each bundle can provide its own dashboard.yml where a new dashboard can be added or change existing ones.

Example can be found in \OroCRM\Bundle\SalesBundle\Resources\config\dashboard.yml.

Added basic dashboards for OroCRM. OroCRM loads Quick Launchpad by default, and user has the ability to change it to a new Dashboard (widgets: calendar, recent emails, recent calls, last actions with accounts, last actions with contacts, opportunities by lead source chart, opportunities by state chart).

Release Notes

Reports creation wizard (Table reports)

"Table reports" are reports that allow a user to choose fields to show from target entity or related entities and set filters and conditions.
On “Manage Reports” page, a user can find the UI management for reports, where users can create, modify or delete reports. For now it is possible to choose an entity, select fields from chosen or related entity, set filter or sorting rules and describe filters logic.
On the next iteration of these feature we will add the ability for a user to apply grouping and aggregation functions on fields.

B2B Sales Flow adjustments

Improvements:

• "Save and qualify" button saves form and redirect to lead page with open qualification step form.
• Owner field is prefilled with current user or business unit.
• Close date is prefilled with current date
• Added account to Lead is not required
• Marked as required account on opportunity
• “Reopen”, “Close as Won” and “Close as Lost” starts transitions
• Removed opportunity entity flow
• Added allowed transition buttons to workflow items table
• On "qualify" transition from lead added a form with three attributes: opportunity name (prefilled from lead name), lead account, lead company name. Prefilled account or company with existing account or with newly created based on Company name.
• Added button to clear selection on entity selector, fix CSS issues for focused filed
• Marked as required account attribute on "Develop" transition form

Call entity

Added ability to log phone calls with contacts. User should go to view contact page and press log a call button.
Added list of calls on Contact and User view.

Add weather layer in the map on contact view page

Release Notes

Removed install.bat/install.sh

Application can be installed using either installation wizard or using oro:install console command.

Workflow transitions

Implemented several improvements for workflow transitions:

• all data entry for workflow will be done in transitions windows.
• transition is displayed in a modal window that shows the relevant form for the transition if all preconditions are met. If not a notice about precondition that need to be met will be displayed
• the result of submitting the Transition Form will be either move to target step of workflow if all conditions are met for entered data. Or error informing the user what needs to be completed or what conditions have not been met to be able to transition to next step;
• attributes can be shown in workflow step form in read-only mode as a table.
• attributes moved from step to transitions
• added new fields to the sales flow from lead and contact: Middle name, Name prefix and Name suffix

Make all entities as Extended

Removed dependency on flexible bundle from all entities.
From now all system entities (entities created by developer, i.e. User, Accounts, …) are extendable, so user can create custom fields for them.

End support for Internet Explorer 9

From 1.0.0-Beta 4 release BAP and OroCRM will not support IE9.

Release Notes

Oro Platform Beta 3 dependency changes

Release Notes

Oro Platform Beta 2 dependency changes

System Requirements Changes

PHP v.5.4.4. and above

Release Notes

CRM Entities reports

Added reports for CRM entities:

• accounts life time
• accounts by opportunities
• leads by date
• opportunities by sales workflow step
• won opportunities by period

These reports demonstrate the approach that we will follow to create other reports. Reports are presented using the Oro Grid.

Custom entities and custom fields

Custom fields can be added to entities marked as extended. This ability was added to the Contact, Leads and Opportunity entities as an example. These fields are added on edit/create form, view page and grid (according to configuration).
Custom entities management appears in System -> Entities -> ... sub-menu, after creating and applying schema.

Contacts Import/Export

Added ability to import/export contacts from/to CSV format.

Account association with contacts

Implemented a more intuitive way to assign contacts to an account from "Account edit" page. Grid with contacts appears in a popup after clicking on "Add" button, selected contacts are presented as "business cards" with short information, user can see more details clicking on a card title. Added ability to choose "Default" contact for an account, first and last name of this contact will be shown in accounts grid.

Release Notes

Leads and Opportunities

Flexible Workflow Engine (FWE)

Added ability to define workflows for CRM entities using .yml workflow definition schema, each bundle can define its own workflows.
Implemented (B2B) sales process workflows for Leads and Opportunities using FWE.