e3fee2cf46
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
41 lines
1.3 KiB
ReStructuredText
41 lines
1.3 KiB
ReStructuredText
================================
|
|
Convert leads into opportunities
|
|
================================
|
|
|
|
The system can generate leads instead of opportunities, in order to add
|
|
a qualification step before converting a *Lead* into an
|
|
*Opportunity* and assigning to the right sales people. You can
|
|
activate this mode from the CRM Settings. It applies to all your sales
|
|
channels by default. But you can make it specific for specific channels
|
|
from their configuration form.
|
|
|
|
Configuration
|
|
=============
|
|
|
|
For this feature to work, go to :menuselection:`CRM --> Configuration --> Settings`
|
|
and activate the *Leads* feature.
|
|
|
|
.. image:: media/convert01.png
|
|
:align: center
|
|
|
|
You will now have a new submenu *Leads* under *Leads* where they
|
|
will aggregate.
|
|
|
|
.. image:: media/convert02.png
|
|
:align: center
|
|
|
|
Convert a lead into an opportunity
|
|
==================================
|
|
|
|
When you click on a *Lead* you will have the option to convert it to
|
|
an opportunity and decide if it should still be assigned to the same
|
|
channel/person and if you need to create a new customer.
|
|
|
|
.. image:: media/convert03.png
|
|
:align: center
|
|
|
|
If you already have an opportunity with that customer Odoo will
|
|
automatically offer you to merge with that opportunity. In the same
|
|
manner, Odoo will automatically offer you to link to an existing
|
|
customer if that customer already exists.
|