The previous behaviour used the uom of the product while it is not necessary the one selected (eg: by default the purchase unit of measure for purchase orders).
This was an issue especially when having a different uom with supplier info lines setting degressive prices. The price should be computed based on selected uom and not the product uom.
bzr revid: mat@openerp.com-20140211152703-twnzco2dwxeqt8hz
- updated groups on some fields of bom
- removed some icons in form view, to be coherent with other form views
- BOM form view: updated onchange_product_id that now takes product_qty into account to compute
uos and uos quantity.
bzr revid: tde@openerp.com-20140211152116-niwt0pak4r0n8jst
The previous behaviour used the uom of product while it could be a different one selected (by default the purchase unit of measure for purchase orders).
This was an issue especially when having different uom with supplier info lines setting degressive prices. The price should be computed based on selected uom and not the product uom.
bzr revid: mat@openerp.com-20140211145703-9uut4hw9aqh7326o
hr: hr.job
- no_of_recruitment now indicates the number of employees you want to hire in a given recruitment phase
- added no_of_hired_employee that is the number of employees already recruited in the current recruitment phase
- updated form view
- removed simplified form view
- the job in the employee form view is now clickable and redirects to the job form view
hr_recruitment
- new dependency: web_kanban_gauge
- installing this module adds the 'Job Positions' menu, and adds a new kanban view for hr.job
- adds fields on hr.job to track applicants and their documents, used in the kanban view
- added configuration for default jobs alias, available in the Human Resources settings
- updated applicant / job subtypes: following some subtypes on the job now makes automatically follow some subtypes on applicants, like salesteam/opportunities or project/tasks and issues
mail: mail_alias
- when migrating to alias, use mail_notrack to avoid performing the tracking; indeed we are in a transient state, and trying to browse and track value change is risky.
mail: mail_thread: empty list help: small tweak to try to find a default alias
misc
- sale_crm: update for the new gauge widget parameters
bzr revid: tde@openerp.com-20140211140149-l15qr876s5ykfww5
- max_value: maximum value of the gauge [default: 100]
- max_field: get the max_value from the field that must be present in the view; takes over max_value
- gauge_value_field: if set, the value displayed below the gauge is taken from this field instead of the base field used for the gauge. This allows to display a number different from the gauge.
- force_set: is value is 0, display a text 'Click to set' [default: True]
- label: lable of the gauge, displayed below the gauge value
- title: title of the gauge, displayed on top of the gauge
- on_change: action to call when cliking and setting a value (previously names action_change)
- on_click_label: optional label of the input displayed when clicking
Coming with an update of jobs that triggered those various changes and cleaning in the gauge widget.
bzr revid: tde@openerp.com-20140211140101-33259mv4i5c1ge7j
- alias finding extgracted in its own method, and uses the new ir.model.data API
xmlid_to_resid
- simplified code of get_default_alias and set_default_alias
- alias_domain default method calls the one defined in mail.alias to try to have only
one method doing the trick
bzr revid: tde@openerp.com-20140211112434-iuqy2a2mrm0pmaxq
- some code reindentation
- updated subtypes, to use parent_id feature between applicants and jobs. Another task will
improve the layout bu hiding some subtypes in applicant; currently we keep a child / parent
behavior.
- renamed open_attachments method
- some changes in create reverted
- chatter posted in job now hav ea subtype, not sure to keep those
bzr revid: tde@openerp.com-20140211105807-ay93xbwilsz3mso6
- new parameters: input_value_field is now called gauge_value_field, this is the field
displayed under the gauge
- new parameter: force_set: whether to force setting a value when the value is nul
- new parameter: on_click_label: label under the input when editing the gauge value
- action_change renamed on_click_action
bzr revid: tde@openerp.com-20140211100445-289mvmr8grcgns8x
Frédéric van der Essen