You are browsing documentation for version 5.0 of OroCommerce, OroCRM, and OroPlatform, supported until January 2025. See version 5.1 (the latest LTS version) of the Oro documentation for information on latest features.
See our Release Process documentation for more information on the currently supported and upcoming releases.
With Oro applications, you can record, store, process, and analyze various commerce, sales, and marketing data and activities. How data is represented in your application may depend on its configuration, but much of it is stored, created, and processed similarly. Your principal records are in the main menu and aggregated under topic-based sections (e.g., Marketing > Promotions > Coupons).
Creating new records in the Oro applications follows the same pattern. However, the structure of the information you must provide when creating a new record depends on its type (i.e., entity). To illustrate this pattern of creating new records, have a look at the description of creating a new account, or a task.
You can edit or delete most of the records and perform some type-specific actions to selected records either from their pages or from the pages with the list of all records (displayed in tables). An example of type-specific actions is the ability to convert a lead into an opportunity from the lead page or add an address on a contact’s page.
On the page of all records (table views), additional actions are usually available as buttons on the top right (also record-specific) or under the ellipsis, or more actions, menu located at the end of the row of each specific record. Within the page of all records, you can usually filter and mass delete items in the table, manage table columns, edit items inline, or tag them, so look out for the corresponding icons on the interface. You can find more information on how to work with table views in the Record Tables topic.
Exchange and transfer of data into the Oro application from various third-party applications (and vice versa) is usually achieved either with the help of import/export or integrations. As an illustration, you can look at how import works for leads, and how an integration between Oro application and Dotdigital is configured.
The workflows define actions and transitions available for your records in the application. They enable you to handle complex procedures that can be explicitly configured for your business needs. You can learn more about the configuration of workflows in the dedicated Workflow Management topic.