OFBiz
  1. OFBiz
  2. OFBIZ-3825

Proposal for adding new functionality in Leave sub tab under HR module

    Details

    • Type: Improvement Improvement
    • Status: Patch Available
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: SVN trunk
    • Fix Version/s: SVN trunk
    • Component/s: humanres
    • Labels:
      None
    • Environment:

      Windows XP, JDK 1.6

      Description

      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

        Activity

        Hide
        BJ Freeman added a comment -

        OK

        Show
        BJ Freeman added a comment - OK
        Hide
        Swapnil Sawant added a comment -

        Hi BJ,

        At first, we will be starting with basic implementation and then will advance to higher level of implementation for this proposal.

        Taking this and your suggestions into consideration, we have following flow :

        • New term types will be added into DB for leaves e.g. sick leave term type, casual leave term type(Agreements tab)
        • Total number of leaves for each of term type will be mentioned under 'term value' field on 'Agreement Term' tab.
        • These term types will correspond to SICK_LEAVE and CASUAL_LEAVE benefits applicable for that employee.
        • When an agreement is selected during employment of an employee, corresponding 'term value' will be getting credited to Party Benefit table for that particular employee.
        • Hence, 'term values' mentioned in selected agreement will be inserted into 'Party Benefit' table for SICK_LEAVE and CASUAL_LEAVE benefits for that employee
        • Then we will have one to one mapping between 'leave reason type'and 'benefit type'
        • Using this mapping, whenever an employee applies for leave,based on leave reason type we would find out corresponding benefit ype and hence proceed with validations related to 'available time' and actual balance for that benefit (from party benefit table)
        Show
        Swapnil Sawant added a comment - Hi BJ, At first, we will be starting with basic implementation and then will advance to higher level of implementation for this proposal. Taking this and your suggestions into consideration, we have following flow : New term types will be added into DB for leaves e.g. sick leave term type, casual leave term type(Agreements tab) Total number of leaves for each of term type will be mentioned under 'term value' field on 'Agreement Term' tab. These term types will correspond to SICK_LEAVE and CASUAL_LEAVE benefits applicable for that employee. When an agreement is selected during employment of an employee, corresponding 'term value' will be getting credited to Party Benefit table for that particular employee. Hence, 'term values' mentioned in selected agreement will be inserted into 'Party Benefit' table for SICK_LEAVE and CASUAL_LEAVE benefits for that employee Then we will have one to one mapping between 'leave reason type'and 'benefit type' Using this mapping, whenever an employee applies for leave,based on leave reason type we would find out corresponding benefit ype and hence proceed with validations related to 'available time' and actual balance for that benefit (from party benefit table)
        Hide
        BJ Freeman added a comment -

        The costing portion of a product has the ability to select the costing calc service.
        https://demo-trunk.ofbiz.apache.org/catalog/control/EditProductCosts
        Cost Component Calc Id
        There can be one or more for costing leaves of different types. This allows open ended ability to do costing.

        Show
        BJ Freeman added a comment - The costing portion of a product has the ability to select the costing calc service. https://demo-trunk.ofbiz.apache.org/catalog/control/EditProductCosts Cost Component Calc Id There can be one or more for costing leaves of different types. This allows open ended ability to do costing.
        Hide
        BJ Freeman added a comment - - edited

        I am not clear about the place of sub agreements.
        agreement ID 86749 (page 147 vol I)

        this agreement is for a entry level job postion.created from the Companies Template for that position.
        The agreement has AgreementItems
        one of those AgreementItems is a productID for Sickleave.
        using the format on page 153
        termtype total amount sick leave
        termvalue 10
        new sequence termtype number of hours for one hour of sickleave
        termvalue 180
        new sequence termtype needs approval over
        termvalue 0
        new sequence termtype employers paid percent
        termvalue 100
        you can specify any and all terms for a leave/benefits this way.

        for each type of leave/benefits would be a product with the terms

        Once an employee is hired these agreements are copied then are associated with the employee partyID. The reason is the agreements for this employee will change and should not affect the standard company templates.
        For instance they get a pay raise that increased their terms for leave.
        The previous would be an thru date of the new terms from date.

        To get the partybenefits cost you use product pricing, take from Position.paygrade (page335), with pricing Subtype (page 88) and the Estimated Product Cost (page 94-95)

        The nightly service would
        1) Build new partybenefits for new employees
        2) Review the terms and add parybenefits type Sick leave available time (page 320)

        all the above is automated, except for building the company templates, and possibly assigning the agreement to the party at interview time. these assignments are linked to the company templates till the party is hired.

        The employee benefit page will list all the partybenefits type they have and the available time.
        Then the requester can check which benefit type they want to request up to the available time.
        this take them to a page where they can modify the time that is now label "amount to use". this then puts a through date on the current record and create a new record with the available being less than that ask for.
        this is then sent as a communication event to the approver.
        should the approver not approve then the thrudate of the new record is added and new record with the old available time is created. And another communication event of the results is sent the requester. This allows for an audit of requests and denials.

        Note: these are also added to payroll (not in the book) and use the payment method type "benifits" and the partybenefits are listed.

        I borrowed the communication event from Inquiry of the alternative performance review (page 332)

        as you can see the is non specific from a model point of view and can be used for all types of benefits. The only thing that changes is the code to work with the types needed. The specific code can be added to the main routine as it is required or can access a config record of a service that is been activated.
        Most of that is general enough you can pass a set of parms to it .

        Show
        BJ Freeman added a comment - - edited I am not clear about the place of sub agreements. agreement ID 86749 (page 147 vol I) this agreement is for a entry level job postion.created from the Companies Template for that position. The agreement has AgreementItems one of those AgreementItems is a productID for Sickleave. using the format on page 153 termtype total amount sick leave termvalue 10 new sequence termtype number of hours for one hour of sickleave termvalue 180 new sequence termtype needs approval over termvalue 0 new sequence termtype employers paid percent termvalue 100 you can specify any and all terms for a leave/benefits this way. for each type of leave/benefits would be a product with the terms Once an employee is hired these agreements are copied then are associated with the employee partyID. The reason is the agreements for this employee will change and should not affect the standard company templates. For instance they get a pay raise that increased their terms for leave. The previous would be an thru date of the new terms from date. To get the partybenefits cost you use product pricing, take from Position.paygrade (page335), with pricing Subtype (page 88) and the Estimated Product Cost (page 94-95) The nightly service would 1) Build new partybenefits for new employees 2) Review the terms and add parybenefits type Sick leave available time (page 320) all the above is automated, except for building the company templates, and possibly assigning the agreement to the party at interview time. these assignments are linked to the company templates till the party is hired. The employee benefit page will list all the partybenefits type they have and the available time. Then the requester can check which benefit type they want to request up to the available time. this take them to a page where they can modify the time that is now label "amount to use". this then puts a through date on the current record and create a new record with the available being less than that ask for. this is then sent as a communication event to the approver. should the approver not approve then the thrudate of the new record is added and new record with the old available time is created. And another communication event of the results is sent the requester. This allows for an audit of requests and denials. Note: these are also added to payroll (not in the book) and use the payment method type "benifits" and the partybenefits are listed. I borrowed the communication event from Inquiry of the alternative performance review (page 332) as you can see the is non specific from a model point of view and can be used for all types of benefits. The only thing that changes is the code to work with the types needed. The specific code can be added to the main routine as it is required or can access a config record of a service that is been activated. Most of that is general enough you can pass a set of parms to it .
        Hide
        Swapnil Sawant added a comment -

        Hi BJ,

        Following is what we have thought of :

        • We will have 'sub-agreements' for various kind of leaves e.g. sub-agreement for sick leave/casual leave.This will be accomplished under 'Agreement Items' sub-tab.
        • How to associate corresponding number of leaves for each of the sub-agreement under 'Agreement Items' tab.Under 'Agreement Items' (after selecting a particular Agreement Item), 'Agreement Item' , 'Promotions' , 'Terms' , 'Products' , 'Party' , ' Geo' tabs are there. Could you please elaborate more as to 'where and how' to 'add number of leaves' that will be credited to employee's account when we select 'Parent Agreement Id' and hit 'Create' button under 'Employements -> Agreement Employment Appl' tab in HR (here functionality will be crediting leaves as per selected 'Agreement Id' "after" 'Create' button is hit)
        • Leave benefits would be added under 'Employments -> Party benefits' tab for a particular 'Employment' as per decided 'agreeement'(lets say agreement id 'aggr1') for it. here leave benefits would be added under Employees account but number of leaves would be getting credited only after 'Create' button hit under 'Employements -> Agreement Employment Appl' tab (after selecting agreement id 'aggr1' )
        • So the concept is ' leave benefits would be added to employee's account as per agreement decided'.When I am saying 'leave benefits would be added' I mean to say 'only specifying what benefits an employee would be getting' but 'for leave benefits , actual no. of leaves would not be credited at this stage. Actual leaves would be credited to his/her leaves benefit (sick leave or casual leave benefit) , only after 'Create' button hit under 'Employements -> Agreement Employment Appl' tab depending on agreement choosen.
        • Reason for deferring 'leaves credition' till 'assigning agreement to employment' is that it sounds logical to credit leaves to employee's account only after we assign any 'agreement' to it and not before that

        Please let us know if this functionality is good to go

        Show
        Swapnil Sawant added a comment - Hi BJ, Following is what we have thought of : We will have 'sub-agreements' for various kind of leaves e.g. sub-agreement for sick leave/casual leave.This will be accomplished under 'Agreement Items' sub-tab. How to associate corresponding number of leaves for each of the sub-agreement under 'Agreement Items' tab.Under 'Agreement Items' (after selecting a particular Agreement Item), 'Agreement Item' , 'Promotions' , 'Terms' , 'Products' , 'Party' , ' Geo' tabs are there. Could you please elaborate more as to 'where and how' to 'add number of leaves' that will be credited to employee's account when we select 'Parent Agreement Id' and hit 'Create' button under 'Employements -> Agreement Employment Appl' tab in HR (here functionality will be crediting leaves as per selected 'Agreement Id' "after" 'Create' button is hit) Leave benefits would be added under 'Employments -> Party benefits' tab for a particular 'Employment' as per decided 'agreeement'(lets say agreement id 'aggr1') for it. here leave benefits would be added under Employees account but number of leaves would be getting credited only after 'Create' button hit under 'Employements -> Agreement Employment Appl' tab (after selecting agreement id 'aggr1' ) So the concept is ' leave benefits would be added to employee's account as per agreement decided'.When I am saying 'leave benefits would be added' I mean to say 'only specifying what benefits an employee would be getting' but 'for leave benefits , actual no. of leaves would not be credited at this stage. Actual leaves would be credited to his/her leaves benefit (sick leave or casual leave benefit) , only after 'Create' button hit under 'Employements -> Agreement Employment Appl' tab depending on agreement choosen. Reason for deferring 'leaves credition' till 'assigning agreement to employment' is that it sounds logical to credit leaves to employee's account only after we assign any 'agreement' to it and not before that Please let us know if this functionality is good to go
        Hide
        BJ Freeman added a comment -

        as far as setup having a couple of standard type templates of agreement with agreement items for leave would be nice.
        once I see you final version, I will try to add to that from my templates.

        Show
        BJ Freeman added a comment - as far as setup having a couple of standard type templates of agreement with agreement items for leave would be nice. once I see you final version, I will try to add to that from my templates.
        Hide
        BJ Freeman added a comment -

        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

        Show
        BJ Freeman added a comment - 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
        Hide
        Swapnil Sawant added a comment -

        Hi BJ,

        As per your comments, we have come up with following flow :

        Agreements creation :

        • Appropriate agreements will be created prior to recruitment

        For example following steps would be followed to create Permanent employment agreement :

        1. From 'Agreements' tab in 'Accounting', create an agreement for permanent employment
        2. Once agreement is created, under 'Agreement Items' tab, we will add 'Leave' item(by selecting Agreement Item Type Id as 'Sub-agreement' from drop down)
        3. Now that we are automating the 'Leave Crediting' process, at this point in time we should decide on as to how many leaves should be credited if this agreement is selected for an employee.
        i.e Leaves would be credited as per agreements ( as suggested by you)
        Hence,how should we add 'no. of leaves' when we are under 'Agreement Items' sub-tab ? Should we provide a new text box ?

        Similary, we will create agreements based on company locations/positions etc and attach 'no. of leaves to be automatically credited' with each of these agreements

        Creating employement :

        • Pre-requisite to creating employement is creating a party in party module for 'hired person'
        • For employement purpose, we would go to 'HR -> Employements' tab and select the above party id
        • Once we hit submit on 'new employement creation', currently system is adding benifits automatically for that 'hired employee'
        • After this, we would go to 'Agreement Employment Appl' sub-tab
        • In this tab, we would select appropriate 'agreement id' (based on position he has been hired for i.e. permanent/contractual/location etc)
        • Once done with above step, now we would select 'Agreement Item Seq Id' which was been created when we had created 'sub-agreement for Leave' for above selected agreement
        • After all other relevant data is filled up, when we would hit 'Create' button under this i.e. 'Agreement Employment Appl' sub-tab, then based on 'Agreement Id' selected , no. of leaves will be credited in 'Party Benefit' table for that employee (against 'Leave benefits')

        This is the functionality we have thought of to start our implementation with. Later on, we will come up with brief flow about 'aligning' this functionality with other modules like Work Effort etc

        Show
        Swapnil Sawant added a comment - Hi BJ, As per your comments, we have come up with following flow : Agreements creation : Appropriate agreements will be created prior to recruitment For example following steps would be followed to create Permanent employment agreement : 1. From 'Agreements' tab in 'Accounting', create an agreement for permanent employment 2. Once agreement is created, under 'Agreement Items' tab, we will add 'Leave' item(by selecting Agreement Item Type Id as 'Sub-agreement' from drop down) 3. Now that we are automating the 'Leave Crediting' process, at this point in time we should decide on as to how many leaves should be credited if this agreement is selected for an employee. i.e Leaves would be credited as per agreements ( as suggested by you) Hence,how should we add 'no. of leaves' when we are under 'Agreement Items' sub-tab ? Should we provide a new text box ? Similary, we will create agreements based on company locations/positions etc and attach 'no. of leaves to be automatically credited' with each of these agreements Creating employement : Pre-requisite to creating employement is creating a party in party module for 'hired person' For employement purpose, we would go to 'HR -> Employements' tab and select the above party id Once we hit submit on 'new employement creation', currently system is adding benifits automatically for that 'hired employee' After this, we would go to 'Agreement Employment Appl' sub-tab In this tab, we would select appropriate 'agreement id' (based on position he has been hired for i.e. permanent/contractual/location etc) Once done with above step, now we would select 'Agreement Item Seq Id' which was been created when we had created 'sub-agreement for Leave' for above selected agreement After all other relevant data is filled up, when we would hit 'Create' button under this i.e. 'Agreement Employment Appl' sub-tab, then based on 'Agreement Id' selected , no. of leaves will be credited in 'Party Benefit' table for that employee (against 'Leave benefits') This is the functionality we have thought of to start our implementation with. Later on, we will come up with brief flow about 'aligning' this functionality with other modules like Work Effort etc
        Hide
        BJ Freeman added a comment - - edited

        As i stated before all the leave data storage can be done with the partybenifiet entitiy.
        the goal of the model is reuse as much of the basic entities as possible.
        Agreements would be a one to many relationship with the partyID.
        the type of agreements would be in the agreement, not related to agreement ID''s
        refer to page 146 of vol I.
        Agreement roles would by permanent or contractual employees.
        as agreement changes new agreements are generated and/or new agreement Items.
        leave would be defined under a agreement Item.
        to carry this further, a company may have different location and the agreement may differ for employments in those locations.
        refer to page 149.
        Just as a thought the leaves can be a product in the agreement. again this resuses entities and provide an open ended way to describe things.
        for instance, if a party benifit was insturance the the Agreement could have a product from a insurance company.

        Agreements type employment are also determine by the organization. so there may be a union that had a contract agreement with the company that would effect leave.following the Agreement Item layout allows for that, in the future, if you don't want to do any code on it now.

        Leave types would be in the enumeration entity. take a look at enumTypeId EMPLOY_STTS
        https://demo-trunk.ofbiz.apache.org/webtools/control/FindGeneric?entityName=Enumeration&find=true&searchOptions_collapsed=false&VIEW_SIZE=50&VIEW_INDEX=0

        So would be LEAVE_STTS and LEAVE_REAS(ON) that puts an a one to many relationship for enumeration ID in partybenefit that leaves it open for many other enumerations, depending on the benefit.

        When an employee is going to be interview they will need to know what their benefits are,so the time the HR Admin setup up the appointment they have associated the Resume with a job postion. HR admin selects the company location if many, which then calls up the agreements for that organization.That Job postion will be associate with those agreements.
        once the perspective employee is hired the HR admin changes the employment status to Hired and the code would then generate the partybenifits from the agreements. as well as associate the partyid of the employee to the agreements. and partybenifits
        when a employee wants to request leave they are presented with the accrued benefits.
        they select the type of leave that then narrows the benifits available.
        they then enter a number within the range available and a start date from their calendar.. they submit for approval. this add a tentative workeffort of not availible for that period.
        there can be a check box for extra ordinary leave that should be covered under agreements, other wise it would not show.
        once approved or denied they get a message in my portal that informs them of the status of thier request.
        Thier Work effort (calendar) is updated so any planning on projects will be aware of their unavailability

        Show
        BJ Freeman added a comment - - edited As i stated before all the leave data storage can be done with the partybenifiet entitiy. the goal of the model is reuse as much of the basic entities as possible. Agreements would be a one to many relationship with the partyID. the type of agreements would be in the agreement, not related to agreement ID''s refer to page 146 of vol I. Agreement roles would by permanent or contractual employees. as agreement changes new agreements are generated and/or new agreement Items. leave would be defined under a agreement Item. to carry this further, a company may have different location and the agreement may differ for employments in those locations. refer to page 149. Just as a thought the leaves can be a product in the agreement. again this resuses entities and provide an open ended way to describe things. for instance, if a party benifit was insturance the the Agreement could have a product from a insurance company. Agreements type employment are also determine by the organization. so there may be a union that had a contract agreement with the company that would effect leave.following the Agreement Item layout allows for that, in the future, if you don't want to do any code on it now. Leave types would be in the enumeration entity. take a look at enumTypeId EMPLOY_STTS https://demo-trunk.ofbiz.apache.org/webtools/control/FindGeneric?entityName=Enumeration&find=true&searchOptions_collapsed=false&VIEW_SIZE=50&VIEW_INDEX=0 So would be LEAVE_STTS and LEAVE_REAS(ON) that puts an a one to many relationship for enumeration ID in partybenefit that leaves it open for many other enumerations, depending on the benefit. When an employee is going to be interview they will need to know what their benefits are,so the time the HR Admin setup up the appointment they have associated the Resume with a job postion. HR admin selects the company location if many, which then calls up the agreements for that organization.That Job postion will be associate with those agreements. once the perspective employee is hired the HR admin changes the employment status to Hired and the code would then generate the partybenifits from the agreements. as well as associate the partyid of the employee to the agreements. and partybenifits when a employee wants to request leave they are presented with the accrued benefits. they select the type of leave that then narrows the benifits available. they then enter a number within the range available and a start date from their calendar.. they submit for approval. this add a tentative workeffort of not availible for that period. there can be a check box for extra ordinary leave that should be covered under agreements, other wise it would not show. once approved or denied they get a message in my portal that informs them of the status of thier request. Thier Work effort (calendar) is updated so any planning on projects will be aware of their unavailability
        Hide
        Swapnil Sawant added a comment -

        Hi BJ,

        As per your comments, we have modified our 'crediting leaves' functionality as follows :

        Agreements for Employement(both permanent and contractual) :

        • We will have separate agreements for both types of employment (Existing screens will be used).
        • While creating above agreements , under 'agreement terms' sub-tab, we would see a 'newly added term' called leave term(this new term will be added to DB as it is not present currently)
        • While creating an 'Employement', appropriate 'agreement id' will be choosen (depending on permanent/contractual position)
        • When 'create' button will be hit, corresponding 'term value' for that agreement id will be credit to 'CreditEmplLeave' table(Leave crediting process)
        • UOM for 'term value' will be days

        And rest of the functionality will be implemented as stated above.

        Please let me know if you have any comments.

        Show
        Swapnil Sawant added a comment - Hi BJ, As per your comments, we have modified our 'crediting leaves' functionality as follows : Agreements for Employement(both permanent and contractual) : We will have separate agreements for both types of employment (Existing screens will be used). While creating above agreements , under 'agreement terms' sub-tab, we would see a 'newly added term' called leave term(this new term will be added to DB as it is not present currently) While creating an 'Employement', appropriate 'agreement id' will be choosen (depending on permanent/contractual position) When 'create' button will be hit, corresponding 'term value' for that agreement id will be credit to 'CreditEmplLeave' table(Leave crediting process) UOM for 'term value' will be days And rest of the functionality will be implemented as stated above. Please let me know if you have any comments.
        Hide
        BJ Freeman added a comment - - edited

        for consideration

        Admin party will credit leaves at the beginning of a financial year for employees
        this should be driven by an employee agreement,
        In this senario there is a company agreement for all employees, then a employee agreement that specifies only for that employee.
        the second one could be a union contract.

        citation??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.??citation
        the employee can view available leave accrued(partybenifits) and request to use it for a range of dates.

        On leave approval, corresponding number of leaves would be deducted from employee's leave account.
        this can be accomplished but specific a type for the period of leave they have been approved in the benifits.
        possibly add a reason typeID to the benifits.

        should have a thresold, in the agreement, that the benefits can be allowed with out approval.

        Show
        BJ Freeman added a comment - - edited for consideration Admin party will credit leaves at the beginning of a financial year for employees this should be driven by an employee agreement, In this senario there is a company agreement for all employees, then a employee agreement that specifies only for that employee. the second one could be a union contract. citation??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.??citation the employee can view available leave accrued(partybenifits) and request to use it for a range of dates. On leave approval, corresponding number of leaves would be deducted from employee's leave account. this can be accomplished but specific a type for the period of leave they have been approved in the benifits. possibly add a reason typeID to the benifits. should have a thresold, in the agreement, that the benefits can be allowed with out approval.

          People

          • Assignee:
            Unassigned
            Reporter:
            Swapnil Sawant
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Time Tracking

              Estimated:
              Original Estimate - 72h
              72h
              Remaining:
              Remaining Estimate - 72h
              72h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development