summaryrefslogtreecommitdiff
path: root/addons/utm/models/utm.py
AgeCommit message (Collapse)Author
2018-10-26[MOV] utm: organize module structure according to guidelinesThibault Delavallée
This module holds old code and is still not updated according to guidelines. Let us update a bit the naming in this module to have readable code. This commit is linked to task ID 1896681 and PR #27975. No functional change should occur with this commit as it contains only renaming / move.
2018-09-21[IMP]tools, technial modules: Improvement in model descriptionNimesh Jethva
Purpose of this commit is to give description more "business oriented" because those descriptions appears in Odoo Studio which is supposed to be used by end users, not only by developers. Related Task ID : 37311
2017-10-26[FIX] utm: fix the fix typoMartin Trigaux
Look at the commit message of c4ba5adc, not the content
2017-10-25[FIX] utm: use proper Englsih abreviationMartin Trigaux
ex is French e.g. should be used
2017-08-20[FIX] P3: text model typesXavier Morel
* remove references to basestring & unicode (use relevant pycompat helpers) * remove some str calls (either entirely or replaced by relevant helper, either text or native) * use better API to avoid unnecessary conversions * remove some XML declarations in views
2017-03-27[IMP] sale_crm: Pass utm values from a quote to a sales orderDhawal Limbuwala
Purpose ======= Create an opportunity Fill in the campaign, medium and source Create a quotation from this opportunity The fields campaign, medium and source on the quotation are empty. -> they should be populated from the opport. Specification ============= Campaign, meduim, source data should be passed to quoation when create quotation from oppor
2016-08-09[MIG] utm: remaining self.pool in ir_http.pyYannick Tivisse
2016-06-09[IMP] base,sales_team: Move res_groups and menuitems to sales_teamYannick Tivisse
Purpose: Having the res_group defined in base and sales_team auto installed with mail doens't make sense. - Move the empty res_config class and the related view from base_setup to sales_team (base_setup only contains the 'General Settings' model and views - Move the 'sale' related content from product to sale module (Access rights, menuitems,...) - Set sales_team at autoinstall False. The module is installed when needed by crm or sale for example - Set sales_team as a dependency of voip. (Access rights defined for configuration purpose) - Set sales_team ad a dependency of subscription (Access rights issue too) [FIX] account: move some ir.model.access to sale module [FIX] payment: Move some ir.rule to website_sale [FIX] stock: move some ir.model.access rule to sale_stock [FIX] project: Move some ir.model.access rules to crm_project_issue [FIX] mrp: Move some ir.model.access rules to sale_mrp [FIX] calendar: move some ir.model.access rules to crm Rename xmlids accordingly. Example: 'base.group_sale_manager' becomes sales_team.group_sale_manager. [ADD] sales_team: See own documents => See only his sales team Moved the "User: Own Leads Only", "User: All Leads" and "Manager" groups from sale and crm into sales_team module. Add the record rules so that user can see only his Own Sales Team if "See Own Leads" is sales right and can see all sales teams if he is having sales rights of "See All Leads" or manager.
2016-06-06Revert "[IMP] base,sales_team: Move res_groups and menuitems to sales_team"Yannick Tivisse
This branch need more testing instead of doing 10 fixes. A lot of issues are occuring when installing modules in different orders. This reverts commit fa6e415cdb23ce9494487ed672792186157b40e0.
2016-06-06[IMP] base,sales_team: Move res_groups and menuitems to sales_teamYannick Tivisse
Purpose: Having the res_group defined in base and sales_team auto installed with mail doens't make sense. - Move the empty res_config class and the related view from base_setup to sales_team (base_setup only contains the 'General Settings' model and views - Move the 'sale' related content from product to sale module (Access rights, menuitems,...) - Set sales_team at autoinstall False. The module is installed when needed by crm or sale for example - Set sales_team as a dependency of voip. (Access rights defined for configuration purpose) - Set sales_team ad a dependency of subscription (Access rights issue too) Rename xmlids accordingly. Example: 'base.group_sale_manager' becomes sales_team.group_sale_manager.
2016-04-06[FIX] utm: ignore utm for saleman.Jeremy Kersten
When a saleman create a lead or a sale after clicking on a link to test their own campaign, they don't want to be linked to this campaign
2016-02-02[MERGE] forward port of branch 9.0 up to f0a63e5Christophe Simonis
2016-02-01[FIX] utm: use tracking_fields from utm.mixin and not from the current modelJeremy Kersten
This function cannot be overridden in a model which inherit utm.mixin Limitation by the heritage on AbstractModel record_crm_lead.tracking_fields() will call tracking_fields() from module utm.mixin (if not overridden on crm.lead) instead of the overridden method from utm.mixin. To force the call of overridden method, we use self.pool['utm.mixin'].tracking_fields() which respects overridden methods of utm.mixin, but will ignore overridden method on crm.lead Eg: class utm_mixin(osv.AbstractModel): _name = 'utm.mixin' def tracking_fields(self): return "A" class utm_mixin_overridden(osv.AbstractModel): _inherit = 'utm.mixin' def tracking_fields(self): return "B" class crm_lead(osv.osv): _name = "crm.lead" _inherit = ['utm.mixin'] def func_1(self): print self.tracking_fields() # print "A" def func_2(self): print self.pool['utm.mixin'].tracking_fields() # print "B" It's the dispatch method of ir_http which save GET parameters in cookies, ignoring the overridden tracking_fields method in inherited model.
2015-10-26[MIG] utm:Migrated into new api.Srushti Patel
2015-06-02[LEGAL] Use global LICENSE/COPYRIGHT files, remove boilerplate textOlivier Dony
- Preserved explicit 3rd-party copyright notices - Explicit boilerplate should not be necessary - copyright law applies automatically in all countries thanks to Berne Convention + WTO rules, and a reference to the applicable license is clear enough.
2015-04-02[FIX] utm* - Allow to customize the cookies nameJeremy Kersten
2014-12-27[FIX] hr_recruitment: use utm_mixin to allow to track the job applicant.Jeremy Kersten
Remove old source_id Use hr.recruitment.source to generate link with utm and create alias with default value for utm [FIX] crm/utm: Fix bug with utm (ddac26cdbb3535239f5dbb41f5b464366065f3ba) Move demo into data Move ir_http to save the utm in the dispatch
2014-12-17[ADD] Add the website_links module.Julien De Coster
This module tracks clicks in mass mailing mails and allow the generation of trackable links in a website interface. Modules modifications --------------------- Refractoring of the crm_tracking_* classes in a new module. * Extract the crm_tracking_* from the crm module into a new module "utm" * Remove the crm_mass_mailing bridge module * New dependencies of mass_mailing and website_links to utm.