[ https://issues.apache.org/jira/browse/OFBIZ-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880231#action_12880231 ]
BJ Freeman commented on OFBIZ-3825: ----------------------------------- sounding better. I suggest that the setup of the agreements be part of the company setup in the setup component. that would take care of 1,2,&3. if not, keep it in mind when doing your way. #3 would be setting up all the types of leaves so there would be many listed under sub-tab. if you used the product model then you have rules, price, cost and cost calc already. the first status of the leaves would be LEAVE_AGRE, when first put in the party benifits. I nightly service would go through all the employees and based on the agreements would calcualted leave in the partybenfits that would have the status of LEAVE_ACCR. a status page that shows all the LEAVE_AGRE and LEAVE_ACCR, would be available to the HR Admin and the employee there would be a check box to select the particular LEAVE_ACCR, the would go to an request leave page with the filled in number of day and a box for start date. the submit of this page would put a message in the approvers myportal that they have a request to review. the approvers page should have ability to modify days and startdate, and an approve or deny, plus a place for comment I would leave room for future to let the approver split dates. the Status would be LEAVE_APPR OR LEAVE_DENY if LEAVE_APPR and SECA will deduct from The LEAVE_ACCR for that particular type of leave for that party, and add a record to LEAVE_USE > Proposal for adding new functionality in Leave sub tab under HR module > ---------------------------------------------------------------------- > > Key: OFBIZ-3825 > URL: https://issues.apache.org/jira/browse/OFBIZ-3825 > Project: OFBiz > Issue Type: Improvement > Components: humanres > Affects Versions: SVN trunk > Environment: Windows XP, JDK 1.6 > Reporter: Swapnil Sawant > Priority: Minor > Fix For: SVN trunk > > Original Estimate: 72h > Remaining Estimate: 72h > > I wish to do some enhancement in existing Leave functionality taking Party > benefits into consideration in OFBiz. > Existing functionalities : > - Currently employee can create leave by selecting his > approver. > - Approver will approve the leave applied by the > employee. > > New functionality : > - Admin party will credit leaves at the beginning of a financial year > for employees > - These leaves can be taken by employee under available benefits from > Party Benefit > - Party Benefits will be setup for each employee as per existing flow > - Whenever employee creates leave application, his/her benefits will be > checked for validation purpose(relation will be set between leave > reason type and benefit type) along with exclusion of weekend and > organization wide holidays. > - On leave approval, corresponding number of leaves would be deducted > from employee's leave account. > > For implementing this, following modifications are being > thought of : > - Adding foreign key column 'benefitTypeId' in 'EmplLeaveReasonType' > (reference from > benefitType.benefitTypeId) > By maintaining this relation, each time employee creates a leave > application (with some leave reason type Id),we can keep track of > 'availableTime' for this particular employee/party-benefitType combination > - We can have CreditEmplLeave,EmplLeave and Holiday tables as mention > in the below thread > http://ofbiz.135035.n4.nabble.com/Proposal-for-adding-new-functionality-in-Leave-sub-tab-under-HR-module-td2250139.html#a2250139 > Following is a demo flow of above mentioned functionality : > 1.Admin credits leaves for an employee. > 2.Employee applies for leave for first time with leave reason type as > 'Medical' (for time being lets assume 'Sick Leave' is benefit type for > this leave reason type in 'EmplLeaveReasonType' table) > 3.Before creating leave application, we would check following two > things : > - If that employee has enough leave balance > - If employee has not crossed 'availableTime' threshold for > benefit type 'Sick Leave'(using Party Benefits already setup through other > existing screen) > 4.After leave application is created, approver can > approve/reject it > 5.Corresponding updations will be made in 'EmplLeave'(changing status > to approve/rejected) and CreditEmplLeave tables(deduction if approved) > Thanks & Regards, > Swapnil Sawant -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.