-
Type:
Enhancement
-
Status: Closed
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
Affected Files:
Workterra Utility
Form1.vb
Database :
SP's
1. OES_SP_CreateDefaultGenericEligibilityRules.sql
2.OES_SP_MigrationScriptForPlanDesignFromDemograhicEligibilityRuleToGenericEligibilityRule.sql
3. OES_SP_MigrationScriptForRate_SubNameFromSubRatesEligibilityRulesToGenericEligibilityRule.sql
4. OES_SP_MigrationScriptForCreditPoolFromCreditPoolEligibilityRulesToGenericEligibilityRule.sql
5. OES_SP_MigrationScriptFromPlanDesignHealthTierMappingToGenericEligibilityRule.sql
6. OES_SP_MigrationScriptForNewHireReHireRulesFromNewHireRehireRulesEligibilityRulesToGenericEligibilityRule.sql
7. OES_SP_MigrationScriptForEffectiveDateTerminationDateRulesFromEffectiveDateTerminationDateRulesToGenericEligibilityRule.sql
8.OES_SP_MigrationScriptForLandingPageFromLandingPageEligibilityRulesToGenericEligibilityRule.StoredProcedure.sql
9.OES_SP_MigrationScriptForQualifyingEventFromQualifyingEventEligibilityRulesToGenericEligibilityRule.sql
10.OES_SP_MigrationScriptForAdditionalFieldInfoFromAdditionalFieldEligibilityRulesToGenericEligibilityRule.StoredProcedure.sql
- relates to
-
WT-3747 Generic Eligibility Component for Classwise open Enrllment - UI and Business logic
-
- Closed
-
Eligibility Rule Migration tool for Plan design completed on LB.
Utility For Migration of PlanDesign,SubRate and CreditPool is not Deploy on LB.
Hi,
Move existing eligibility rule to Generic Eligibility Rule for single company is deployed on LB for Following tables :
1.PlanDesign
2.Rate_SubName
3.CreditPool
MigrateUtility button is used to move existing eligibility rule to Generic Eligibility Rule.
Move existing eligibility rule to Generic Eligibility Rule for All companies is in progress for unit testing.
Amit Gude : why this ticket is with you ?
Satya Vinanti Yadav : This task is from Sprint 5 and till date Dev Due Date and code reviewed by and code review date is not updated. can you please update this ASP ?
Satya : I do not see any progress on this front and yet dev due date is not updated.. This is really not looks good.
Vinanti Yadav
we are planning to deploy Migration scripts for following table with LB Deployment Date :-
1) Effective - Termination Date Rule (LB Deployment Date :1 July 2016 )
2) New Hire Re Hire Rule (LB Deployment Date :1 July 2016 )
3) Class wise OE (LB Deployment Date :8 July 2016 )
4) Qualifying Event(LB Deployment Date :8 July 2016 )
5) Landing Page(LB Deployment Date :15 July 2016 )
6) Additional Fields(LB Deployment Date :15 July 2016 )
7) Form Builder(LB Deployment Date :22 July 2016 )
8) Employee Home Page Files(LB Deployment Date :22 July 2016 )
9) Forms Library(LB Deployment Date :29 July 2016 )
thanks,
vinanti
Hi ,Deepali Tidke
Move existing eligibility rule to Generic Eligibility Rule is deployed on LB (Today 24 June)for Following tables :
1. PlanDesignHealthTierMapping
(PlanDesign,Subrate,CreditPool are already Deployed.)
MigrateUtility button is used to move existing eligibility rule to Generic Eligibility Rule.
Affected Files:
\App\Supporting Projects\Workterra Utility\Form1.vb
OES_SP_MigrationScriptFromPlanDesignHealthTierMappingToGenericEligibilityRule.sql
Thanks,
Vinanti
Venkatesh Pujari please test the patch on lb , @Neelam will give you demo first how to test the patch on lb using DB.
Hi Deepali,
As discussed please assign this to someone.
Thanks,
Venkatesh
Neelam Yangal as discussed Venkatesh has tried to check this from Db however he is finding difficult, can you please help us in checking this from DB.
As discussed with you , even we can test this by UI.
1) Restore one of company from stage on LB.
2) Do not allow to change any customization on stage till your testing.
3) Do script changes and migration on stage.
4) Refer old eligibility rule from stage and new one from LB.
In this way you can test all possible scenarios
Venkatesh Pujari please check above comments and try to check this.
Hi Venkatesh Pujari,
Move existing eligibility rule to Generic Eligibility Rule is deployed on LB ( 4 July) for Following tables :
1. NewHireEffectiveDateRule
2 .EffectiveDateTerminationDateRules
Impacted Areas:
1. Import
2. Export
3. Enroll Now
4. Employee Data Exchange
Thanks,
Vinanti
Hi Ashwin,
Please take one backup of stage company (austin) and attach this to LB and also run the latest scripts on this backup for testing of Eligibility Rule to Generic Rule enhancement. Once this is done please reassign this ticket to me.
Thanks & Regards,
Venkatesh.
HI Gokul,
Can you please check this request?
@Venkatesh- Can you please mentioned you need this company for what purpose?
-------------------------------
Thanks & Regards,
Ashwin Wankhede
Ph: +91-20-6673-2500 | Ext:472
Hi Ashwin,
I have already mentioned I need this company for Testing for Eligibility Rule enhancement.
Thanks,
Venkatesh.
Ashwin Wankhede Venkatesh Pujari : Guys this task is already late ideally by this time this should be on production please speed up the required things what ever is needs to be done.
Hi Shyam,
This enhancement has to be tested thoroughly so that is why we are trying are best to test this feature at our level best. As soon this is done I will start testing it from my end.
Thanks,
Venkatesh.
Hi Venkatesh,
As discussed, This can be tested on any existing company. Last week you have requested 3 companies from stage. You can use it for same purpose.
-------------------------------
Thanks & Regards,
Ashwin Wankhede
Ph: +91-20-6673-2500 | Ext:472
Hi Ashwin,
As conveyed to you those companies have not been provided to me till date. I have requested them from last two weeks. But there is no resolution to this. How will I use those companies when they are not yet provided to me.
Vijay Siddha,Samir,Deepali Tidke,Rakesh Roy
Thanks,
Venkatesh.
Hi Gokul,
Have you completed the request for 6 companies requested by venkatesh?
-------------------------------
Thanks & Regards,
Ashwin Wankhede
Ph: +91-20-6673-2500 | Ext:472
Hi Gokul,
Adding Gokul. Gokul Sonawane
As he is not aware of any JIRA comments as he is not added in any loop.
Thanks & Regards,
Neelam A. Yangal
Ashwin Wankhede : can you please look in to this , it seems that Gokul is not checking jira from last 2 days, can you please move this ahead as this task is from sprint 5 and by this time it should be completed, we are already too much late, please speed up the things at your end.
Hi Venkatesh ,
You requested 6 companies on LB which are ready, Can you use same companies for this testing. Please confirm if it affects.
Hi Neelam,
I have verified the enhancement of moving existing eligibility rule to generic eligibility rule through utility and observed that rules are moved properly. I have checked this through the option you had mentioned in the earlier comments. The below are the steps which I have followed;-
1) Restored one of company from stage on LB.
2) Run scripts and did migration from stage.
3) Refered old eligibility rule from stage and new one from LB.
These changes have been done on Rates,New Hire/ Rehire Rules,Effective termination rules and Plans as per now.
Thanks,
Venkatesh.
Hi Venkatesh Pujari,
Migration Scripts for LandingPage and QualifyingEvent table are deployed on LB today(11 july).
Verify Migration of (Eligibility related date) data for both tables(Using Migration Utility).
Thanks,
Vinanti.
Hi Venkatesh Pujari,
Migration Scripts for AdditionalFieldInfo are deployed on LB today(19 july).
Verify Migration of (Eligibility related date) data of "AdditionalFieldInfo" table(Using Migration Utility).
Thanks,
Vinanti.
Tested the migration of additional field eligibility through Utility the rules are properly migrated.
For the migration related part this ticket is ready for stage.
Hi Deepali Tidke,
Migration Scripts for Classwise Open Enrollment Effective Date Rules deployed on LB today(27july).
Verify Migration of (Eligibility related date) data of "OpenEnrollmentRules" table(Using Migration Utility).
Thanks,
Vinanti.
Swapnil Pandhare : why this is still on LB ?
Hi shyam sharma,
As this enhancement is related with common eligibility change.
This item contains many module,We are releasing this all module step by step.
With each release we are updating this ticket accordingly with proper comments.
Recently we have released "Classwise Open Enrollment Effective Date Rules" Migration.
so we again set there status as LB deployed.
For any further details just ask to Vinanti Yadav, as she is the owner of this ticket.
Thanks & Regards,
Neelam A. Yangal
Hi Neelam and Vinanti,
Please create a separate ticket for the points which you deploy on LB because this ticket is ready for Stage so please do not change the item status of this ticket.
For Classwise Open enrollment effective date rules please refer WT-3747.
Thanks,
Venkatesh.
Hi Venkatesh Pujari and Neelam Yangal,
Migration scripts are missing form stage branch which must be present in stage branch.
I have done check in stage branch.
Thanks,
vinanti
Hi Neelam,
I have verified the enhancement of moving existing eligibility rule to generic eligibility rule through utility and observed that rules are moved properly. I have checked this through the option you had mentioned in the earlier comments. The below are the steps which I have followed:-
1) Restored one of company from Production on stage.
2) Run scripts and did migration on Stage company.
3) Refered old eligibility rule from production and new one from Stage.
These changes have been tested on Rates,New Hire/ Rehire Rules,Effective termination rules and Plans.
Thanks,
Venkatesh.
Cannot test this on production so closing this ticket
Move existing eligibility for plan design has been done and Testing is in progress.
Rest of the eligibility movement, will start from 28 March 2016.
1)Sub Rate
2)Credit Pool
3) New Hire ReHire
4) FormBuilderPage
5) EffectiveDateTerminationDate
6) LandingPage
7) AdditionalField
8)QualifyingEvent
9)tblReward
10)tblWellnessProgram
11) TourInfo
12) CrossBoardingRule
13) ClasswiseOE
14) PlanDesignHealthTierMapping
15)FormCategoriesFiles
16)EmployeeHomePageFiles