to define custom light workflows on opportunities. Activities are linked to mail.message.subtype through inheritance. This means that the follow mechanism works for activities. When an activity is done, a message with the matching subtype is posted on the opportunity. Activities are internal by default. They are only visible by employees. A shortcut in the 'log a note' chatter option allows to post a note linked to an activity (subtype).
18 lines
505 B
ReStructuredText
18 lines
505 B
ReStructuredText
.. _changelog:
|
|
|
|
Changelog
|
|
=========
|
|
|
|
`trunk (saas-2)`
|
|
----------------
|
|
|
|
- Stage/state update
|
|
|
|
- ``crm.lead``: removed ``state`` field. Added ``date_last_stage_update`` field
|
|
holding last stage_id modification. Updated reports.
|
|
- ``crm.case.stage``: removed ``state`` field.
|
|
|
|
- ``crm``, ``crm_claim``: removed inheritance from ``base_stage`` class. Missing
|
|
methods have been added into ``crm`` and ``crm_claim``. Also removed inheritance
|
|
in ``crm_helpdesk`` because it uses states, not stages.
|