<a class="reference external image-reference" href="http://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.svg"> </a> <a name="holidays-evaluation-allocation"></a> <h2>Holidays Evaluation Allocation</h2> <p>This module allows you to define ruleset on leave type that are automatically evaluated to get employee's leave allocation at any point in time</p> <a name="installation"></a> <h3>Installation</h3> <p>No additional steps necessary</p> <a name="configuration"></a> <h3>Configuration</h3> <p>To configure this module, you need to:</p> <ul class="simple"> <li>Go to Human Resources &gt; Configuration &gt; Leaves Evaluation Ruleset</li> <li>Create Ruleset and save, then add your set of rules from the ruleset form</li> <li>Go to Leave types. choose a leave type with &quot;Allow to Override limit&quot; checkbox unchecked and select the ruleset you want evaluated for that rule type</li> </ul> <p>Some important concepts to be understood whilst configuring rulesets are as follows:</p> <p>Period Definition Defines the concept of leave period for this ruleset. For example, in the case of legal leaves for some companies a leave period in the start of the year until the last day of that year during which a leaves taken in that year accumulates and resets in the next. Other companies use the anniversary of an employee's employment date to define leave period for that employee. An example for each case is as follows... Employee was hired on 2010-10-21 Start of Year - e.g of a leave period 2015-01-01 to 2015-12-31 - all leaves in this period are accumulated Employment Anniversary -e.g. of a leave period - 2015-10-21 to 2016-10-20 - all leaves in this period are accumulated</p> <p>Evaluation Mode Defines what to do in cases wherein multiple rules satisfy a certain condition. Options are as follows: First - Consider the first rule that satisfies condition Minimum - Consider rule that evaluates to the least number of allocated days Maximum - Consider rule that evaluates to the most number of allocated days</p> <p>Rules These are the individual lines that are evaluated in an order that depends on their sequence. Rules with the smallest sequence number is evaluated first.</p> <p>Rules are evaluated based on the following condition categories:</p> <p>Always True - Will also be evaluated to true; an example of this is a case wherein your organization offers Urgent Personal Leave that users can take at any time up to a certain amount. In this case you can choose &quot;Always True&quot; and isnert the limit, e.g. &quot;5&quot; in the &quot;Amount of Days&quot; field</p> <p>Range - Will evaluate a given field on the models, hr.employee, hr.contract, hr.job and test is the returned value is within the range specified in Minimum Range an Maximum Range. be careful that this field returns and integer or float when computed An example of this is allocating leaves based on employee's length of service.</p> <p>Python Expression - Will evaluate a python expression. To ensure that your rule is aware of the date context please use date_ref in place date.today() if you need to compare date against today()</p> <a name="usage"></a> <h3>Usage</h3> <p>Once your ruleset and rules is configured using requesting for leaves is done as usual however leave allocations can not longer be done as these are now computed from the ruleset attached to leave type</p> <a class="reference external image-reference" href="https://runbot.odoo-community.org/runbot/{repo_id}/{branch}"><img alt="Try me on Runbot" src="https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas" /></a> <a name="known-issues-roadmap"></a> <h3>Known issues / Roadmap</h3> <a name="bug-tracker"></a> <h3>Bug Tracker</h3> <p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/{project_repo}/issues">GitHub Issues</a>. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback <a class="reference external" href="https://github.com/OCA/{project_repo}/issues/new?body=module:%20{module_name}%0Aversion:%20{version}%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**">here</a>.</p> <a name="credits"></a> <h3>Credits</h3> <a name="contributors"></a> <h4>Contributors</h4> <ul class="simple"> <li>Salton Massally &lt;<a class="reference external" href="mailto:smassally&#64;idtlabs.sl">smassally&#64;idtlabs.sl</a>&gt;</li> </ul> <a name="maintainer"></a> <h4>Maintainer</h4> <a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" /></a> <p>This module is maintained by the OCA.</p> <p>OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.</p> <p>To contribute to this module, please visit <a class="reference external" href="http://odoo-community.org">http://odoo-community.org</a>.</p>