Remote work management

[ben3474]

The option "Remote work" within the Employee settings must be ticked.
Using the existing information within the employee form, tab "Professional Information", Section "Remote work" the information about the when an employee works remotely is defined. You know if the employee location is considered as remote working using the location icons (house for remote)

=> Within the sustainability setup application :

• add a field to give the ability to select an emission factor similarly as what we have for the accounting section (screenshot
  
  )

=> Similarly as for the commuting section (screenshot attached) add the ability to define the account where the entries will be generated, which journal will be used and the ability to activate the automatic computation.

=> create a batch similarly as for the commuting but separated that will generate the accounting entries every month. In case information is missing for some employees, similarly as for commuting compute an average and use it for these employees. Keep the same logic as the commuting module (number of weeks, active contract mgmt...)

[ben3474]

I have taken a look and actually this feature is not available in v16. So you won't be able to backport it @jacopobacci

[ben3474]

Here are some feedbacks after a first set of tests.

• Only EF with uom.category set as "Time" must be selectable.
• On the demo dataset the entry being generated includes Abigail Peterson whereas she has no contract defined. The logic must be the same as the one for commuting (an active contract for the month being involved).
• The entries must remain draft and not posted/paid similarly as the commuting module.
• It is not possible to open an individual entry from the account.move list view (Invoicing->Accounting->Journal Entries). See traceback attached

traceback_remote.txt

.

• When an employee has no remote work at all in his schedule (only office for instance) he is not considered at 0 home office but ignored. Then his CO2 footprint is the company average. You can check on bch-co2-remote-test db.

Would be great that these "business cases" are transformed in tests before trying to fix them to make sure the tests fail and then after fixing see the tests passing.