Mailing-List: contact user-help@ofbiz.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ofbiz.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: Swapnil Sawant <Swapnil.Sawant@lntinfotech.com>
To: "user@ofbiz.apache.org" <user@ofbiz.apache.org>
Date: Thu, 1 Jul 2010 15:49:01 +0530
Subject: RE: Help regarding migration services
Thread-Topic: Help regarding migration services
Thread-Index: AcsY+NAY9q+5LgA9Sy+ZhQzXPIHydwABoJaw
Message-ID: 
 <CAE23E69E5D7AA4087E3C4E1AC5E997D028CD18EAF@VSHINMSMBX01.vshodc.lntinfotech.com>
References: 
 <CAE23E69E5D7AA4087E3C4E1AC5E997D028CD18D33@VSHINMSMBX01.vshodc.lntinfotech.com>
 <A4AF698F23574B848B82A7C61346BF41@inspiron530>
In-Reply-To: <A4AF698F23574B848B82A7C61346BF41@inspiron530>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi Jacques,

My implementation is about leave management. Some part of it's functionali=
ty is as follows :

        - Appropriate leave balance data would be there for two basic type=
s of agreements (permanent and contractual)
        - Agreements would be applied to employee/s and thereby he/she wou=
ld get some leave balance
        - Whenever an employee creates new leave application, leave balanc=
e would be checked.
        - Depending on leave balance, leave application may or may not be =
created

In short, I have implemented 'leave balance check' functionality.

        Now, lets consider old data. We may find that different employees =
had applied for different number of leaves in total(e.g. empl1 had applied=
 for 40,empl2 had applied for 50 leaves till now ) . So when newly added f=
unctionality would be applied to 'such old data' conflicts will be seen in=
 data (as you can not keep on creating new agreements specific to employee=
 to cop-up with no of leaves created by him/her)

        Please suggest how to tackle this situation.


Thanks & regards,

Swapnil Sawant

-----Original Message-----
From: Jacques Le Roux [mailto:jacques.le.roux@les7arts.com]
Sent: Thursday, July 01, 2010 2:07 PM
To: user@ofbiz.apache.org
Subject: Re: Help regarding migration services

Quick answer: this may help (examples)
https://cwiki.apache.org/confluence/display/OFBTECH/Revisions+Requiring+Da=
ta+Migration

Jacques

Swapnil Sawant wrote:
> Hi,
>
> I have following queries while writing migration service/s :
>
>
> 1.       I have created two new rows in an existing entity. In this case=
, only exporting data to XML should be done ?
>
> 2.       Functionality which I have implemented won't work with old data=
. In that case, how migration process should be carried
> out ?
>
> For example :
>
>
> -          In my implementation, I am tracking leave applications agains=
t leave balance (i.e. before creating a leave application
> ,his/her current balance would be checked)
>
> -          When an already approved leave is rejected, corresponding 'no=
 of leaves'(calculated using a service) gets credited
> back to his/her balance
>
> -          But,as per old data, there wont be any (stored) value for 'no=
 of leaves'.
>
> -          If at all I use  above service (for calculating no of leaves =
from existing dates),it will give rise to inconsistency
> of data because 'calculated no of leaves' would not be calculated agains=
t some 'leave balance'
>
> Please guide me in this context.
>
>
> Thanks & Regards,
>
> Swapnil Sawant
>
> ________________________________
> This Email may contain confidential or privileged information for the in=
tended recipient (s) If you are not the intended
> recipient, please do not use or disseminate the information, notify the =
sender and delete it from your system.
>
> ______________________________________________________________________


______________________________________________________________________

This Email may contain confidential or privileged information for the inte=
nded recipient (s) If you are not the intended recipient, please do not us=
e or disseminate the information, notify the sender and delete it from you=
r system.

______________________________________________________________________