Uploaded image for project: 'WORKTERRA'
  1. WORKTERRA
  2. WT-8924

Austin-CIGNA EOI processing for Dependent Enrollment

    Details

    • Type: Enhancement
    • Status: Closed
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Module:
      BenAdmin - SSO
    • Reported by:
      Client
    • Item State:
      Production Complete
    • Sprint:
      WT Sprint 28
    • Severity:
      Simple

      Attachments

        Issue Links

          Activity

          aditya.vishwakarma Aditya Vishwakarma (Inactive) created issue -
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Field Original Value New Value
          Assignee Vijay Siddha [ vijays ] Aditya Vishwakarma [ aditya.vishwakarma ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Link This issue relates to WT-8599 [ WT-8599 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Link This issue relates to WT-7143 [ WT-7143 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Summary Symphony-Austin-CIGNA EOI processing for Spouse Enrollment Symphony-Austin-CIGNA EOI processing for Dependent Enrollment
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 22/Mar/17 02:54 PM
          • Time Spent:
            8h
             

            Learning and analysis

          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 23/Mar/17 03:33 PM - edited
          • Time Spent:
            7h
             

            Learning and analysis

          santosh.balid Santosh Balid (Inactive) logged work - 24/Mar/17 12:41 PM
          • Time Spent:
            1h
             

            Initial Analysis Discussion

          santosh.balid Santosh Balid (Inactive) made changes -
          Remaining Estimate 80h [ 288000 ] 79h [ 284400 ]
          Time Spent 1h [ 3600 ]
          Worklog Id 33645 [ 33645 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 24/Mar/17 03:34 PM
          • Time Spent:
            8h
             

            Learning and analysis

          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Remaining Estimate 79h [ 284400 ] 71h [ 255600 ]
          Time Spent 1h [ 3600 ] 9h [ 32400 ]
          Worklog Id 34067 [ 34067 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Remaining Estimate 71h [ 255600 ] 63h [ 226800 ]
          Time Spent 9h [ 32400 ] 17h [ 61200 ]
          Worklog Id 34068 [ 34068 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Remaining Estimate 63h [ 226800 ] 64h [ 230400 ]
          Time Spent 17h [ 61200 ] 16h [ 57600 ]
          Worklog Id 34067 [ 34067 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 27/Mar/17 03:37 PM
          • Time Spent:
            9h
             

            Learning and analysis

          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Remaining Estimate 64h [ 230400 ] 55h [ 198000 ]
          Time Spent 16h [ 57600 ] 25h [ 90000 ]
          Worklog Id 34071 [ 34071 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 29/Mar/17 02:45 PM
          • Time Spent:
            10h
             

            Analysis
            Coding

          santosh.balid Santosh Balid (Inactive) logged work - 30/Mar/17 04:49 AM - edited
          • Time Spent:
            0.5h
             

            discussion

          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 30/Mar/17 02:45 PM
          • Time Spent:
            7h
             

            -Coding
            -Analysis
            -Discussion

          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Remaining Estimate 55h [ 198000 ] 48h [ 172800 ]
          Time Spent 25h [ 90000 ] 32h [ 115200 ]
          Worklog Id 35001 [ 35001 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Remaining Estimate 48h [ 172800 ] 38h [ 136800 ]
          Time Spent 32h [ 115200 ] 42h [ 151200 ]
          Worklog Id 35002 [ 35002 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Remaining Estimate 38h [ 136800 ] 31h [ 111600 ]
          Time Spent 42h [ 151200 ] 49h [ 176400 ]
          Worklog Id 35004 [ 35004 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Worklog Id 35004 [ 35004 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Worklog Id 35004 [ 35004 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Remaining Estimate 31h [ 111600 ] 23h [ 82800 ]
          Time Spent 49h [ 176400 ] 57h [ 205200 ]
          Worklog Id 35011 [ 35011 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Remaining Estimate 23h [ 82800 ] 30h [ 108000 ]
          Time Spent 57h [ 205200 ] 50h [ 180000 ]
          Worklog Id 35004 [ 35004 ]
          Worklog Time Spent 7h [ 25200 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Remaining Estimate 30h [ 108000 ] 29.5h [ 106200 ]
          Time Spent 50h [ 180000 ] 50.5h [ 181800 ]
          Worklog Id 35138 [ 35138 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Remaining Estimate 29.5h [ 106200 ] 23.5h [ 84600 ]
          Time Spent 50.5h [ 181800 ] 56.5h [ 203400 ]
          Worklog Id 35179 [ 35179 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Worklog Id 35138 [ 35138 ]
          santosh.balid Santosh Balid (Inactive) logged work - 31/Mar/17 11:26 AM
          • Time Spent:
            1h
             

            Discussion

          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Attachment WT-8924_symphonyScreenshot.png [ 43852 ]
          Hide
          aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment -

          Hello Tracy Kot & Chris Ellenberger

          We need your feedback for our queries related to dependent life enrollment for EOI for which CIGNA has suggested this new enhancement.

          Problem statement: When employee enrolls for any Life plan which goes to CIGNA for EOI approval through sso, if same employee enrolls for dependent spouse Life plan then CIGNA is not able to process those plans and there is no criteria which will differ dependent spouse life enrollment from employee life enrollment.

          Please refer below plans for which this issue exists:
          Austin - Voluntary Dependent Life
          Symphony - Spouse Voluntary Life Plan ,Spouse Voluntary Critical Illness Plan

          In given above these plans are sounds for spouse/dependent but according to configuration in Workterra the employee does enrollment.
          So when an employee enroll for any Life plan and the respective spouse life plan (e.g Employee Voluntary Life Plan and Spouse Voluntary Life Plan) then while sending data to CIGNA we send both enrollments under employee data, which is confusing to CIGNA , as it is not possible to identify which plan is enrolled for employee and spouse. So CIGNA suggested that please send us spouse enrollment in different section of same request , so that they can distinguish between enrollments.

          Action Item:
          So either Austin or Symphony sholud change the configuration for these plans ( we will be finding more plans later in the system) or we need some criteria on plan so that we can distinguish them.

          attaching Screenshot for an example

          Please let me know if you have any query.

          Thanks

          cc: Satya Santosh Balid Prasanna Karlekar

          Show
          aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment - Hello Tracy Kot & Chris Ellenberger We need your feedback for our queries related to dependent life enrollment for EOI for which CIGNA has suggested this new enhancement. Problem statement: When employee enrolls for any Life plan which goes to CIGNA for EOI approval through sso, if same employee enrolls for dependent spouse Life plan then CIGNA is not able to process those plans and there is no criteria which will differ dependent spouse life enrollment from employee life enrollment. Please refer below plans for which this issue exists: Austin - Voluntary Dependent Life Symphony - Spouse Voluntary Life Plan ,Spouse Voluntary Critical Illness Plan In given above these plans are sounds for spouse/dependent but according to configuration in Workterra the employee does enrollment. So when an employee enroll for any Life plan and the respective spouse life plan (e.g Employee Voluntary Life Plan and Spouse Voluntary Life Plan) then while sending data to CIGNA we send both enrollments under employee data, which is confusing to CIGNA , as it is not possible to identify which plan is enrolled for employee and spouse. So CIGNA suggested that please send us spouse enrollment in different section of same request , so that they can distinguish between enrollments. Action Item: So either Austin or Symphony sholud change the configuration for these plans ( we will be finding more plans later in the system) or we need some criteria on plan so that we can distinguish them. attaching Screenshot for an example Please let me know if you have any query. Thanks cc: Satya Santosh Balid Prasanna Karlekar
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Assignee Aditya Vishwakarma [ aditya.vishwakarma ] Tracy Kot [ tkot ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 31/Mar/17 05:14 PM
          • Time Spent:
            6h
             

            Analysis and code correction as requested information.

          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 03/Apr/17 06:26 AM
          • Time Spent:
            20m
             

            Sent for Review to Santosh

          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Remaining Estimate 23.5h [ 84600 ] 23h 10m [ 83400 ]
          Time Spent 56.5h [ 203400 ] 56h 50m [ 204600 ]
          Worklog Id 35672 [ 35672 ]
          santosh.balid Santosh Balid (Inactive) logged work - 03/Apr/17 11:27 AM
          • Time Spent:
            1h
             

            Code Review

          santosh.balid Santosh Balid (Inactive) made changes -
          Remaining Estimate 23h 10m [ 83400 ] 22h 10m [ 79800 ]
          Time Spent 56h 50m [ 204600 ] 57h 50m [ 208200 ]
          Worklog Id 35733 [ 35733 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Remaining Estimate 22h 10m [ 79800 ] 21h 10m [ 76200 ]
          Time Spent 57h 50m [ 208200 ] 58h 50m [ 211800 ]
          Worklog Id 35734 [ 35734 ]
          Hide
          aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment -

          Hello Tracy Kot & Chris Ellenberger

          Is there any update regarding previous message?

          Thanks

          cc: Satya Santosh Balid Prasanna Karlekar , Jennifer Leugers

          Show
          aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment - Hello Tracy Kot & Chris Ellenberger Is there any update regarding previous message? Thanks cc: Satya Santosh Balid Prasanna Karlekar , Jennifer Leugers
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Issue Type Task [ 3 ] Enhancement [ 4 ]
          santosh.balid Santosh Balid (Inactive) logged work - 04/Apr/17 11:29 AM
          • Time Spent:
            0.5h
             
            <No comment>
          santosh.balid Santosh Balid (Inactive) made changes -
          Remaining Estimate 21h 10m [ 76200 ] 20h 40m [ 74400 ]
          Time Spent 58h 50m [ 211800 ] 59h 20m [ 213600 ]
          Worklog Id 35934 [ 35934 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 04/Apr/17 01:03 PM
          • Time Spent:
            3h
             
            • Review board code changes
            • Code Checkin
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Remaining Estimate 20h 40m [ 74400 ] 17h 40m [ 63600 ]
          Time Spent 59h 20m [ 213600 ] 62h 20m [ 224400 ]
          Worklog Id 35999 [ 35999 ]
          Hide
          Chris.ellenberger Chris Ellenberger added a comment -

          Hi Robyn Adkison,

          Can you please take a look at Aditya's concern above regarding Symphony - Spouse Voluntary Life Plan ,Spouse Voluntary Critical Illness Plans?

          Thanks,
          Chris

          cc Gary Cunningham

          Show
          Chris.ellenberger Chris Ellenberger added a comment - Hi Robyn Adkison , Can you please take a look at Aditya's concern above regarding Symphony - Spouse Voluntary Life Plan ,Spouse Voluntary Critical Illness Plans? Thanks, Chris cc Gary Cunningham
          Hide
          Robyn.Adkison Robyn Adkison (Inactive) added a comment -

          Hi Aditya Vishwakarma,
          The spouse life plan rates and reduction rules are based on the Employee age, so we need to build the spouse life plan as an employee plan. We will not be able to change this to a spouse enrollment plan as it will cause issues with the rates and age band rules.

          Are there any other options available to send the spouse information needed on these plans based on the plan names e.g. Spouse Voluntary Life plan?
          thanks,
          Robyn

          Show
          Robyn.Adkison Robyn Adkison (Inactive) added a comment - Hi Aditya Vishwakarma , The spouse life plan rates and reduction rules are based on the Employee age, so we need to build the spouse life plan as an employee plan. We will not be able to change this to a spouse enrollment plan as it will cause issues with the rates and age band rules. Are there any other options available to send the spouse information needed on these plans based on the plan names e.g. Spouse Voluntary Life plan? thanks, Robyn
          alankar.chavan Alankar Chavan (Inactive) logged work - 05/Apr/17 01:45 PM
          • Time Spent:
            0.25h
             

            discussion and help to Aditya

          alankar.chavan Alankar Chavan (Inactive) made changes -
          Remaining Estimate 17h 40m [ 63600 ] 17h 25m [ 62700 ]
          Time Spent 62h 20m [ 224400 ] 62h 35m [ 225300 ]
          Worklog Id 36339 [ 36339 ]
          Hide
          aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment -

          Hello Robyn Adkison

          We need to move employee enrollments of spouse plan to spouse enrollments.

          As per your last comment:
          The spouse life plan rates and reduction rules are based on the Employee age, so we need to build the spouse life plan as an employee plan. We will not be able to change this to a spouse enrollment plan as it will cause issues with the rates and age band rules.

          For this following is the solution:
          We need to add spouse age bands in rates and select consider age of employee. Also need to roll over employee elections to spouse election through script.

          This will require 2 working days

          Step1: Change Allow Spouse Enrollment to Yes and Allow employee Enrollment to No

          Step2: Reduction schedule need not to change anything as it is not customized

          Step3: Replace employee age bands with spouse age bands

          Step4: Consider age of select to employee

          Step5: Change elections to spouse member type through script

          By this When a spouse is enrolled in spouse plan then system will consider age of employee for calculation for example if spouse falls in age of 0-29 and employee falls in 35-39 then system will consider age band of 35-39 for reduction. So the aim of creating plan rates and reduction rules will based on Employee age will be achieved
          and through this we will be able to distinguish the records between employee and spouse while sending request for EOI to CIGNA.

          Please let us know if you want to consider these changes else we will explore other option.

          Thanks

          cc: Satya , Amruta Lohiya, Prasanna Karlekar,Santosh Balid,Jennifer Leugers , Chris Ellenberger

          Show
          aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment - Hello Robyn Adkison We need to move employee enrollments of spouse plan to spouse enrollments. As per your last comment: The spouse life plan rates and reduction rules are based on the Employee age, so we need to build the spouse life plan as an employee plan. We will not be able to change this to a spouse enrollment plan as it will cause issues with the rates and age band rules. For this following is the solution: We need to add spouse age bands in rates and select consider age of employee. Also need to roll over employee elections to spouse election through script. This will require 2 working days Step1: Change Allow Spouse Enrollment to Yes and Allow employee Enrollment to No Step2: Reduction schedule need not to change anything as it is not customized Step3: Replace employee age bands with spouse age bands Step4: Consider age of select to employee Step5: Change elections to spouse member type through script By this When a spouse is enrolled in spouse plan then system will consider age of employee for calculation for example if spouse falls in age of 0-29 and employee falls in 35-39 then system will consider age band of 35-39 for reduction. So the aim of creating plan rates and reduction rules will based on Employee age will be achieved and through this we will be able to distinguish the records between employee and spouse while sending request for EOI to CIGNA. Please let us know if you want to consider these changes else we will explore other option. Thanks cc: Satya , Amruta Lohiya , Prasanna Karlekar , Santosh Balid , Jennifer Leugers , Chris Ellenberger
          Hide
          Robyn.Adkison Robyn Adkison (Inactive) added a comment -

          Hi Aditya Vishwakarma,
          Updating the Spouse life plan from an Employee enrollment plan to a spouse enrollment plan will not work on this end as it will cause issues.

          In another connection for client DC Taylor, I believe export logic was released to help solve for this issue with the Spouse life plan. this was for the MOO (Mutual of Omaha) connection where the employee was masked and the spouse was able to be populated on the spouse life record.
          Would you be able to use the same logic for this connection?

          Thank you,
          Robyn

          Show
          Robyn.Adkison Robyn Adkison (Inactive) added a comment - Hi Aditya Vishwakarma , Updating the Spouse life plan from an Employee enrollment plan to a spouse enrollment plan will not work on this end as it will cause issues. In another connection for client DC Taylor, I believe export logic was released to help solve for this issue with the Spouse life plan. this was for the MOO (Mutual of Omaha) connection where the employee was masked and the spouse was able to be populated on the spouse life record. Would you be able to use the same logic for this connection? Thank you, Robyn
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Attachment PlanList.xls [ 45250 ]
          Hide
          aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment -

          Hello Tracy Kot , Chris Ellenberger , Robyn Adkison

          For Going other option we need some meta data from your end. I have attached Excel Document PlanList.xls for Austin and Symphony in separate sheet. This Sheet contains all plan for Life and LTD which has provider CIGNA. . All I want is the value for Column PlanMadeFor(EE,SP,CH) in the sheet.

          for eg: if a plan Employee Voluntary Life Plan is intended for Spouse then fill up SP in the column PlanMadeFor(EE,SP,CH) like wise.

          Please note we will not able to take further development without these data.

          Please revert me in case of any query.

          Thanks

          cc: Prasanna Karlekar Satya Santosh Balid Amruta Lohiya Jennifer Leugers

          Show
          aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment - Hello Tracy Kot , Chris Ellenberger , Robyn Adkison For Going other option we need some meta data from your end. I have attached Excel Document PlanList.xls for Austin and Symphony in separate sheet. This Sheet contains all plan for Life and LTD which has provider CIGNA. . All I want is the value for Column PlanMadeFor(EE,SP,CH) in the sheet. for eg: if a plan Employee Voluntary Life Plan is intended for Spouse then fill up SP in the column PlanMadeFor(EE,SP,CH) like wise. Please note we will not able to take further development without these data. Please revert me in case of any query. Thanks cc: Prasanna Karlekar Satya Santosh Balid Amruta Lohiya Jennifer Leugers
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Item State Parent values: Development(10200) Parent values: Development(10200)Level 1 values: In Analysis(10204)
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Item State Parent values: Development(10200)Level 1 values: In Analysis(10204) Parent values: Development(10200)Level 1 values: In Progress(10206)
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 12/Apr/17 10:15 AM
          • Time Spent:
            3h
             
            <No comment>
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Remaining Estimate 17h 25m [ 62700 ] 14h 25m [ 51900 ]
          Time Spent 62h 35m [ 225300 ] 65h 35m [ 236100 ]
          Worklog Id 37701 [ 37701 ]
          Robyn.Adkison Robyn Adkison (Inactive) made changes -
          Attachment Symphony PlanList.xls [ 45294 ]
          Hide
          Robyn.Adkison Robyn Adkison (Inactive) added a comment -

          Hi Aditya Vishwakarma,
          Please see attached, we've populated for the Symphony Client.
          Please let us know if you need anything else for Symphony.

          thanks,
          Robyn
          Symphony PlanList.xls

          Show
          Robyn.Adkison Robyn Adkison (Inactive) added a comment - Hi Aditya Vishwakarma , Please see attached, we've populated for the Symphony Client. Please let us know if you need anything else for Symphony. thanks, Robyn Symphony PlanList.xls
          Hide
          aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment -

          Hello Robyn Adkison
          Thanks for providing the data for Symphony. I will start further analysis based on it

          Hello Tracy Kot
          Do we have some update for Austin ?

          cc: Prasanna Karlekar Satya Santosh Balid Amruta Lohiya Jennifer Leugers

          Show
          aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment - Hello Robyn Adkison Thanks for providing the data for Symphony. I will start further analysis based on it Hello Tracy Kot Do we have some update for Austin ? cc: Prasanna Karlekar Satya Santosh Balid Amruta Lohiya Jennifer Leugers
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 17/Apr/17 11:01 AM
          • Time Spent:
            5h
             

            analysis and coding

          Hide
          Tkot Tracy Kot (Inactive) added a comment - - edited

          Actually, I think I understand what you need. I can review for Austin Industries and can let you know.

          Show
          Tkot Tracy Kot (Inactive) added a comment - - edited Actually, I think I understand what you need. I can review for Austin Industries and can let you know.
          Tkot Tracy Kot (Inactive) made changes -
          Comment [ [~aditya.vishwakarma]Hello, can you give me a brief recap on this? Is this in STAGE for Austin Industries? Or has something been moved to production? Can you give me an update and let me know what actions you need from me to test Austin? I would appreciate it. There are a lot of notes in the ticket so if you could let me know so that I can work on this. Thank you. ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 18/Apr/17 10:59 AM
          • Time Spent:
            7h
             

            analysis and coding

          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 19/Apr/17 10:57 AM
          • Time Spent:
            5h
             

            Analysis and coding

          santosh.balid Santosh Balid (Inactive) logged work - 21/Apr/17 06:16 AM
          • Time Spent:
            1h
             

            Internal discussion + suggestions

          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Status New Request [ 10029 ] Pending for Approval [ 10002 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Status Pending for Approval [ 10002 ] Approved for Development [ 10003 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Status Approved for Development [ 10003 ] In Development [ 10007 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 21/Apr/17 02:49 PM
          • Time Spent:
            5.5h
             
            <No comment>
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Remaining Estimate 14h 25m [ 51900 ] 8h 55m [ 32100 ]
          Time Spent 65h 35m [ 236100 ] 71h 5m [ 255900 ]
          Worklog Id 40160 [ 40160 ]
          Deborah.Mascot@ebsbenefits.com Deborah Mascot (Inactive) made changes -
          Hide
          Deborah.Mascot@ebsbenefits.com Deborah Mascot (Inactive) added a comment -

          Please see uploaded file for Austin. Copy of Austin Industries PlanList ticket WT8924.xls

          Show
          Deborah.Mascot@ebsbenefits.com Deborah Mascot (Inactive) added a comment - Please see uploaded file for Austin. Copy of Austin Industries PlanList ticket WT8924.xls
          Deborah.Mascot@ebsbenefits.com Deborah Mascot (Inactive) made changes -
          Assignee Tracy Kot [ tkot ] Aditya Vishwakarma [ aditya.vishwakarma ]
          santosh.balid Santosh Balid (Inactive) logged work - 24/Apr/17 05:40 AM
          • Time Spent:
            1h
             

            Code Review

          satyap Satya made changes -
          Sprint WT Sprint 28 [ 53 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 24/Apr/17 01:02 PM
          • Time Spent:
            6h
             

            Coding and Discussion

          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 25/Apr/17 03:58 PM
          • Time Spent:
            4h
             

            Code checkin

          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Code Reviewed By Santosh Balid [ 13300 ]
          khandu.kshirsagar Khandu Kshirsagar (Inactive) made changes -
          Item State Parent values: Development(10200)Level 1 values: In Progress(10206) Parent values: LB QA(10201)Level 1 values: LB Deployed(11600)
          khandu.kshirsagar Khandu Kshirsagar (Inactive) made changes -
          Item State Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602)
          khandu.kshirsagar Khandu Kshirsagar (Inactive) made changes -
          Item State Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) Parent values: LB QA(10201)Level 1 values: LB Deployed(11600)
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 26/Apr/17 05:42 PM - edited
          • Time Spent:
            0.5h
             

            Code Checkin

          santosh.balid Santosh Balid (Inactive) made changes -
          Remaining Estimate 8h 55m [ 32100 ] 7h 55m [ 28500 ]
          Time Spent 71h 5m [ 255900 ] 72h 5m [ 259500 ]
          Worklog Id 41642 [ 41642 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Remaining Estimate 7h 55m [ 28500 ] 7h 25m [ 26700 ]
          Time Spent 72h 5m [ 259500 ] 72h 35m [ 261300 ]
          Worklog Id 41647 [ 41647 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Worklog Id 41647 [ 41647 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Remaining Estimate 7h 25m [ 26700 ] 6h 25m [ 23100 ]
          Time Spent 72h 35m [ 261300 ] 73h 35m [ 264900 ]
          Worklog Id 41732 [ 41732 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Remaining Estimate 6h 25m [ 23100 ] 2h 25m [ 8700 ]
          Time Spent 73h 35m [ 264900 ] 77h 35m [ 279300 ]
          Worklog Id 42049 [ 42049 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Remaining Estimate 2h 25m [ 8700 ] 0h [ 0 ]
          Time Spent 77h 35m [ 279300 ] 83h 35m [ 300900 ]
          Worklog Id 42053 [ 42053 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 83h 35m [ 300900 ] 88h 35m [ 318900 ]
          Worklog Id 42210 [ 42210 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 88h 35m [ 318900 ] 95h 35m [ 344100 ]
          Worklog Id 42219 [ 42219 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 95h 35m [ 344100 ] 100h 35m [ 362100 ]
          Worklog Id 42229 [ 42229 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 28/Apr/17 11:06 AM - edited
          • Time Spent:
            6h
             

            Self testing
            Discussion

          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 100h 35m [ 362100 ] 103h 35m [ 372900 ]
          Worklog Id 42242 [ 42242 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 103h 35m [ 372900 ] 106h 35m [ 383700 ]
          Worklog Id 42242 [ 42242 ]
          alankar.chavan Alankar Chavan (Inactive) logged work - 28/Apr/17 02:22 PM
          • Time Spent:
            0.5h
             

            SSO help for creating the scenario and testing

          alankar.chavan Alankar Chavan (Inactive) made changes -
          Time Spent 106h 35m [ 383700 ] 107h 5m [ 385500 ]
          Worklog Id 42477 [ 42477 ]
          Hide
          Tkot Tracy Kot (Inactive) added a comment -

          Hi, is this the ticket I need to place the Austin Industries EOI SSO with CIGNA feedback?
          I tested it and you must have worked on Symphony because none of Austin Industries Client Feedback has been addressed since their original feedback provided. I will update this ticket.

          Show
          Tkot Tracy Kot (Inactive) added a comment - Hi, is this the ticket I need to place the Austin Industries EOI SSO with CIGNA feedback? I tested it and you must have worked on Symphony because none of Austin Industries Client Feedback has been addressed since their original feedback provided. I will update this ticket.
          Tkot Tracy Kot (Inactive) made changes -
          Tkot Tracy Kot (Inactive) made changes -
          Attachment screenshot-1.png [ 46633 ]
          Hide
          Tkot Tracy Kot (Inactive) added a comment - - edited

          Hi, is this the ticket I need to place the Austin Industries EOI SSO with CIGNA feedback?
          I tested it and you must have worked on Symphony because none of Austin Industries Client Feedback has been addressed since their original feedback provided. I will update this ticket.

          Austin Industries PlanList ticket WT8924.xls is per your request.
          Also, I tested this again and the client feedback appears to not have been addressed.

          Client Feedback (which is what they gave originally and I can re-attach)-
          Austin Industries does not like the fact that the employee has to decide if they are done with enrolling in benefits that require EOI. The employees do NOT know what benefits require EOI or not. So this box does not work for Austin "If you have enrolled in all benefits for life and disability that may require EOI you can click OK. If you want to enroll in additional life and disability benefits that may require EOI click on cancel". The Austin Industries employees will not know how to answer this because they do not know the EOI rules/benefit EOI. They dependent on WORKTERRA system to tell them that. So with that. If the employee hits cancel, do they ever see the SSO screen?
          Austin Industries would like the system to offer the EOI SSO once they are done enrolling in the life and disability and if anything is pending EOI, then to move to the EOI SSO CIGNA box. I will find the original.
          Also I tested the tunnel and never saw any of these message boxes. I only saw them when I was logged in as an Admin enrolling for the EE.
          Also for Austin, when I did click on OK to SSO screen, the SSO has error. "ERROR OCCURRED".

          Adding document name; 4.28.2017_STAGE NAME Austin OE 2017 for SSO CIGNA Testing to the attachments too.

          Show
          Tkot Tracy Kot (Inactive) added a comment - - edited Hi, is this the ticket I need to place the Austin Industries EOI SSO with CIGNA feedback? I tested it and you must have worked on Symphony because none of Austin Industries Client Feedback has been addressed since their original feedback provided. I will update this ticket. Austin Industries PlanList ticket WT8924.xls is per your request. Also, I tested this again and the client feedback appears to not have been addressed. Client Feedback (which is what they gave originally and I can re-attach)- Austin Industries does not like the fact that the employee has to decide if they are done with enrolling in benefits that require EOI. The employees do NOT know what benefits require EOI or not. So this box does not work for Austin "If you have enrolled in all benefits for life and disability that may require EOI you can click OK. If you want to enroll in additional life and disability benefits that may require EOI click on cancel". The Austin Industries employees will not know how to answer this because they do not know the EOI rules/benefit EOI. They dependent on WORKTERRA system to tell them that. So with that. If the employee hits cancel, do they ever see the SSO screen? Austin Industries would like the system to offer the EOI SSO once they are done enrolling in the life and disability and if anything is pending EOI, then to move to the EOI SSO CIGNA box. I will find the original. Also I tested the tunnel and never saw any of these message boxes. I only saw them when I was logged in as an Admin enrolling for the EE. Also for Austin, when I did click on OK to SSO screen, the SSO has error. "ERROR OCCURRED". Adding document name; 4.28.2017_STAGE NAME Austin OE 2017 for SSO CIGNA Testing to the attachments too.
          Hide
          Tkot Tracy Kot (Inactive) added a comment -

          Also note, I am using the STAGE NAME: Austin OE 2017; is that where the work has been done?

          Show
          Tkot Tracy Kot (Inactive) added a comment - Also note, I am using the STAGE NAME: Austin OE 2017; is that where the work has been done?
          Tkot Tracy Kot (Inactive) made changes -
          Tkot Tracy Kot (Inactive) made changes -
          Hide
          aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment -

          Hello Tracy Kot

          The deployment for dependent section currently will work only for Symphony.
          The error which you got we got it same today while testing for Symphony and inform Zachary through an email you are also in cc.

          For Austin there is one problem with Plan Voluntary Dependent Life we are analyzing it internally and will get you back soon on this.

          As per your last message Can you collect a bit more information from Austin how they are expecting it. meanwhile I will discuss it with Santosh Balid and will you let you know.

          Thanks

          Show
          aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment - Hello Tracy Kot The deployment for dependent section currently will work only for Symphony. The error which you got we got it same today while testing for Symphony and inform Zachary through an email you are also in cc. For Austin there is one problem with Plan Voluntary Dependent Life we are analyzing it internally and will get you back soon on this. As per your last message Can you collect a bit more information from Austin how they are expecting it. meanwhile I will discuss it with Santosh Balid and will you let you know. Thanks
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 28/Apr/17 03:14 PM
          • Time Spent:
            1h
             

            Unit testing.
            Client Reply

          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 107h 5m [ 385500 ] 108h 5m [ 389100 ]
          Worklog Id 42500 [ 42500 ]
          Hide
          santosh.balid Santosh Balid (Inactive) added a comment - - edited

          Tracy Kot, I will suggest , please create a open enrollment workflow for Austin on stage environment. Create a new employee such way that ,all demographic fields of employee should have a proper value exactly like a original employee , and that employee should eligible for all life and LTD/STD benefits.

          Now login with that employee and start the enrollment workflow, when you enrolle into Life and LTD/STD benefits with EOI , you will notice at the end of workflow before beneficiary page there is page which has list down all enrolled Life and STD/LDT benefits eligible for EOI, and on click of "CIGNA SSO" button on that page, it will open CIGNA sso page in new window , and there you will get all your answers that everything is implemented as per previous discussions with you and every point of our discussion is tracked into jira at the same time.

          Now , if you have concern about the implementation in case of "Admin Login", then could uou please tell me how you want it to be handled, because my concern is, in case of admin there is no such workflow which will tell you now this is the end of workflow so submit your enrollments to CIGNA, so how we can decide which will be the last enrollment and now we should go for SSO after this last enrollment.

          And again my point is if Admin is doing enrollment on behalf of employee , so why should employee worry about messages, Admin is the person who has known the things better. and the same thing you also acknowledged in past, if you track jira WT-7143, you will notice that only you had given us that "Popup" messages for enrollment through Admin Login.

          Chris Ellenberger : We saw that you have closed the ticket WT-7143, so can we assume "Symphony" is ok with what we implemented.

          Cc :Aditya Vishwakarma, Satya, Samir, Vijay Siddha, shyam sharma, Rohan J Khandave, Chris Ellenberger

          Show
          santosh.balid Santosh Balid (Inactive) added a comment - - edited Tracy Kot , I will suggest , please create a open enrollment workflow for Austin on stage environment. Create a new employee such way that ,all demographic fields of employee should have a proper value exactly like a original employee , and that employee should eligible for all life and LTD/STD benefits. Now login with that employee and start the enrollment workflow, when you enrolle into Life and LTD/STD benefits with EOI , you will notice at the end of workflow before beneficiary page there is page which has list down all enrolled Life and STD/LDT benefits eligible for EOI, and on click of "CIGNA SSO" button on that page, it will open CIGNA sso page in new window , and there you will get all your answers that everything is implemented as per previous discussions with you and every point of our discussion is tracked into jira at the same time. Now , if you have concern about the implementation in case of "Admin Login", then could uou please tell me how you want it to be handled, because my concern is, in case of admin there is no such workflow which will tell you now this is the end of workflow so submit your enrollments to CIGNA, so how we can decide which will be the last enrollment and now we should go for SSO after this last enrollment. And again my point is if Admin is doing enrollment on behalf of employee , so why should employee worry about messages, Admin is the person who has known the things better. and the same thing you also acknowledged in past, if you track jira WT-7143 , you will notice that only you had given us that "Popup" messages for enrollment through Admin Login. Chris Ellenberger : We saw that you have closed the ticket WT-7143 , so can we assume "Symphony" is ok with what we implemented. Cc : Aditya Vishwakarma , Satya , Samir , Vijay Siddha , shyam sharma , Rohan J Khandave , Chris Ellenberger
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 02/May/17 01:04 PM
          • Time Spent:
            4.5h
             

            Code changes

          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 108h 5m [ 389100 ] 112h 35m [ 405300 ]
          Worklog Id 42718 [ 42718 ]
          khandu.kshirsagar Khandu Kshirsagar (Inactive) made changes -
          Item State Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602)
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 03/May/17 05:06 PM
          • Time Spent:
            1.5h
             

            Unit testing
            Client communcation

          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 112h 35m [ 405300 ] 114h 5m [ 410700 ]
          Worklog Id 43054 [ 43054 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 04/May/17 01:57 PM
          • Time Spent:
            1.5h
             

            test case creation
            issue analysis
            Client communication.

          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Item State Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) Parent values: Stage QA(10202)Level 1 values: In Testing(10214)
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Assignee Aditya Vishwakarma [ aditya.vishwakarma ] Tracy Kot [ tkot ]
          Hide
          aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment -

          For Austin creating separate ticket WT-9412

          Show
          aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment - For Austin creating separate ticket WT-9412
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Link This issue relates to WT-9412 [ WT-9412 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Status In Development [ 10007 ] Local Testing [ 10200 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Status Local Testing [ 10200 ] Pending for Stage Approval [ 10300 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Status Pending for Stage Approval [ 10300 ] Approved for Stage [ 10030 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Status Approved for Stage [ 10030 ] Stage Testing [ 10201 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 05/May/17 01:53 PM
          • Time Spent:
            1h
             
            • Analysis
            • Client communcation
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 114h 5m [ 410700 ] 115h 5m [ 414300 ]
          Worklog Id 43564 [ 43564 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 115h 5m [ 414300 ] 116h 35m [ 419700 ]
          Worklog Id 43568 [ 43568 ]
          khandu.kshirsagar Khandu Kshirsagar (Inactive) made changes -
          Item State Parent values: Stage QA(10202)Level 1 values: In Testing(10214) Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602)
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 08/May/17 02:01 PM
          • Time Spent:
            1h
             

            Code Changes

          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 09/May/17 02:02 PM - edited
          • Time Spent:
            2.5h
             

            Code changes and check ins
            Client communication.

          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 116h 35m [ 419700 ] 117h 35m [ 423300 ]
          Worklog Id 44187 [ 44187 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 117h 35m [ 423300 ] 119h 5m [ 428700 ]
          Worklog Id 44189 [ 44189 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 119h 5m [ 428700 ] 120h 5m [ 432300 ]
          Worklog Id 44189 [ 44189 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 10/May/17 02:07 PM
          • Time Spent:
            2h
             

            Code change
            Check ins
            Unit testing

          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 120h 5m [ 432300 ] 122h 5m [ 439500 ]
          Worklog Id 44524 [ 44524 ]
          santosh.balid Santosh Balid (Inactive) logged work - 11/May/17 10:24 AM - edited
          • Time Spent:
            2h
             

            Discussion + Review

          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 11/May/17 03:00 PM
          • Time Spent:
            2.5h
             

            analysis and coding

          santosh.balid Santosh Balid (Inactive) logged work - 12/May/17 10:23 AM - edited
          • Time Spent:
            1h
             

            Discussion

          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 12/May/17 03:07 PM
          • Time Spent:
            3h
             

            analysis

          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 15/May/17 03:10 PM
          • Time Spent:
            8h
             

            made changes XML format as suggested by client

          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 122h 5m [ 439500 ] 124h 5m [ 446700 ]
          Worklog Id 45979 [ 45979 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 124h 5m [ 446700 ] 125h 5m [ 450300 ]
          Worklog Id 45980 [ 45980 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 125h 5m [ 450300 ] 126h 5m [ 453900 ]
          Worklog Id 45980 [ 45980 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Remaining Estimate 0h [ 0 ] 1h [ 3600 ]
          Time Spent 126h 5m [ 453900 ] 125h 5m [ 450300 ]
          Worklog Id 45979 [ 45979 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 16/May/17 02:53 PM
          • Time Spent:
            4h
             

            analysis and code devlopment

          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 17/May/17 02:56 PM
          • Time Spent:
            8h
             

            Code analysis
            Client call

          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 18/May/17 02:51 PM
          • Time Spent:
            7h
             

            analysis and code devlopment

          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 18/May/17 02:51 PM
          • Time Spent:
            1h
             

            Client Call

          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 19/May/17 02:48 PM
          • Time Spent:
            7h
             

            Analysis and code devlopment

          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 22/May/17 02:41 PM
          • Time Spent:
            3.5h
             

            Client Response analysis.

          santosh.balid Santosh Balid (Inactive) logged work - 31/May/17 11:29 AM
          • Time Spent:
            0.5h
             

            Queries discussion

          santosh.balid Santosh Balid (Inactive) made changes -
          Remaining Estimate 1h [ 3600 ] 0.5h [ 1800 ]
          Time Spent 125h 5m [ 450300 ] 125h 35m [ 452100 ]
          Worklog Id 51107 [ 51107 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 31/May/17 02:27 PM
          • Time Spent:
            1h
             

            Queries Discussion

          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Remaining Estimate 0.5h [ 1800 ] 0h [ 0 ]
          Time Spent 125h 35m [ 452100 ] 126h 35m [ 455700 ]
          Worklog Id 51324 [ 51324 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 126h 35m [ 455700 ] 130h 5m [ 468300 ]
          Worklog Id 51347 [ 51347 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 130h 5m [ 468300 ] 137h 5m [ 493500 ]
          Worklog Id 51354 [ 51354 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 137h 5m [ 493500 ] 144h 5m [ 518700 ]
          Worklog Id 51357 [ 51357 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 144h 5m [ 518700 ] 145h 5m [ 522300 ]
          Worklog Id 51358 [ 51358 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 145h 5m [ 522300 ] 149h 5m [ 536700 ]
          Worklog Id 51360 [ 51360 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 149h 5m [ 536700 ] 157h 5m [ 565500 ]
          Worklog Id 51364 [ 51364 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 157h 5m [ 565500 ] 159h 35m [ 574500 ]
          Worklog Id 51370 [ 51370 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 159h 35m [ 574500 ] 162h 35m [ 585300 ]
          Worklog Id 51374 [ 51374 ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 162h 35m [ 585300 ] 170h 35m [ 614100 ]
          Worklog Id 51377 [ 51377 ]
          jyoti.mayne Jyoti Mayne logged work - 31/May/17 03:51 PM
          • Time Spent:
            1h
             

            design team meeting

          jyoti.mayne Jyoti Mayne made changes -
          Time Spent 170h 35m [ 614100 ] 171h 35m [ 617700 ]
          Worklog Id 51408 [ 51408 ]
          santosh.balid Santosh Balid (Inactive) logged work - 01/Jun/17 01:01 PM
          • Time Spent:
            4h
             
            <No comment>
          santosh.balid Santosh Balid (Inactive) logged work - 02/Jun/17 01:01 PM
          • Time Spent:
            5h
             
            <No comment>
          santosh.balid Santosh Balid (Inactive) logged work - 05/Jun/17 01:00 PM
          • Time Spent:
            6h
             
            <No comment>
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 05/Jun/17 03:06 PM
          • Time Spent:
            1.5h
             

            Client Reply.

          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 171h 35m [ 617700 ] 173h 5m [ 623100 ]
          Worklog Id 52407 [ 52407 ]
          santosh.balid Santosh Balid (Inactive) logged work - 06/Jun/17 05:32 AM
          • Time Spent:
            0.5h
             

            discussion and email review

          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 173h 5m [ 623100 ] 173h 35m [ 624900 ]
          Worklog Id 52421 [ 52421 ]
          Hide
          aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment -

          Hello Chris Ellenberger

          Do Symphony Client process the SSO EOI records at their end? Basically our question is how client knows which EOI's are in pending state and which are get approved? In Workterra System do we have any process to update the status of SSO EOI records?

          Thanks

          Santosh Balid

          Show
          aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment - Hello Chris Ellenberger Do Symphony Client process the SSO EOI records at their end? Basically our question is how client knows which EOI's are in pending state and which are get approved? In Workterra System do we have any process to update the status of SSO EOI records? Thanks Santosh Balid
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Assignee Tracy Kot [ tkot ] Chris Ellenberger [ chris.ellenberger ]
          Hide
          Tkot Tracy Kot (Inactive) added a comment -

          I know you have a question or Chris above, but for Austin I need to review / test prod again because Austin wants us to turn the EOI SSO off for Austin if it doesn't meet their original testing feedback they gave originally. Let me test again first though, which ticket do you want me to update for Austin? Thanks.

          Show
          Tkot Tracy Kot (Inactive) added a comment - I know you have a question or Chris above, but for Austin I need to review / test prod again because Austin wants us to turn the EOI SSO off for Austin if it doesn't meet their original testing feedback they gave originally. Let me test again first though, which ticket do you want me to update for Austin? Thanks.
          Hide
          aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment -

          Hi Tracy Kot

          Ok you can test for Austin.The Ticket Id for Austin is WT-9412.

          Thanks

          Show
          aditya.vishwakarma Aditya Vishwakarma (Inactive) added a comment - Hi Tracy Kot Ok you can test for Austin.The Ticket Id for Austin is WT-9412 . Thanks
          Hide
          santosh.balid Santosh Balid (Inactive) added a comment - - edited

          Hi Tracy Kot,

          Could you please let us know which points from Austin's feedback missed in implementation. As per our understanding and time to time communication in jira and email, we don't find anything is missing.

          Please find our last communication in attached email, where you had asked for summary on what is going on.

          Regards,
          Santosh

          Cc: Aditya Vishwakarma, Satya, Samir, Vijay Siddha, shyam sharma RE Symphony-Austin-CIGNA EOI processing for Dependent Enrollment.msg

          Show
          santosh.balid Santosh Balid (Inactive) added a comment - - edited Hi Tracy Kot , Could you please let us know which points from Austin's feedback missed in implementation. As per our understanding and time to time communication in jira and email, we don't find anything is missing. Please find our last communication in attached email, where you had asked for summary on what is going on. Regards, Santosh Cc: Aditya Vishwakarma , Satya , Samir , Vijay Siddha , shyam sharma RE Symphony-Austin-CIGNA EOI processing for Dependent Enrollment.msg
          Chris.ellenberger Chris Ellenberger made changes -
          Assignee Chris Ellenberger [ chris.ellenberger ] Tracy Kot [ tkot ]
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Summary Symphony-Austin-CIGNA EOI processing for Dependent Enrollment Symphony-CIGNA EOI processing for Dependent Enrollment
          santosh.balid Santosh Balid (Inactive) logged work - 07/Jun/17 01:00 PM
          • Time Spent:
            2h
             
            <No comment>
          santosh.balid Santosh Balid (Inactive) logged work - 08/Jun/17 09:07 AM
          • Time Spent:
            1.5h
             

            Merged Aditya's code from trunk to Uirefresh branch.

          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 173h 35m [ 624900 ] 175h 5m [ 630300 ]
          Worklog Id 53216 [ 53216 ]
          santosh.balid Santosh Balid (Inactive) logged work - 08/Jun/17 12:59 PM - edited
          • Time Spent:
            4.5h
             
            <No comment>
          Tkot Tracy Kot (Inactive) made changes -
          Attachment screenshot-2.png [ 51685 ]
          Hide
          Tkot Tracy Kot (Inactive) added a comment - - edited

          Santosh Balid

          Austin Industries wants the EOI SSO to come up once the employee has enrolled in all the life and disability that require EOI instead of asking the employee to choose either OK or cancel. The employee will not know the answer to that question and will guess at the answer.

          Per Austin, the employee will not know the answer to this pop up question. The employees do not know if an EOI is required and do not know which benefits require EOI; that is why they have WORKTERRA to show which benefits require EOI. If the employee answers cancel each time, will they ever see the EOI SSO (no, correct)? If the employee chooses “OK” and does EOI SSO, and they have more benefits that required EOI does it still time out? Austin Feedback is the employee will not know how to answer this pop up question…. They don’t know which benefits might require EOI.

          The client says if the employee hits "cancel" each time, will the employee ever see the EOI SSO popup?

          CC Aditya Vishwakarma Satya Samir Vijay Siddha shyam sharma

          Let me know if you have questions, if the EOI SSO can't do this, Austin Industries wants to turn this off and use the PDF form (paper form) until WORKTERRA can bring up the EOI SSO at the end of the enrollments of Life and Disability or at the end of enrolling so that the EE completes the EOI SSO..

          Show
          Tkot Tracy Kot (Inactive) added a comment - - edited Santosh Balid Austin Industries wants the EOI SSO to come up once the employee has enrolled in all the life and disability that require EOI instead of asking the employee to choose either OK or cancel. The employee will not know the answer to that question and will guess at the answer. Per Austin, the employee will not know the answer to this pop up question. The employees do not know if an EOI is required and do not know which benefits require EOI; that is why they have WORKTERRA to show which benefits require EOI. If the employee answers cancel each time, will they ever see the EOI SSO (no, correct)? If the employee chooses “OK” and does EOI SSO, and they have more benefits that required EOI does it still time out? Austin Feedback is the employee will not know how to answer this pop up question…. They don’t know which benefits might require EOI. The client says if the employee hits "cancel" each time, will the employee ever see the EOI SSO popup? CC Aditya Vishwakarma Satya Samir Vijay Siddha shyam sharma Let me know if you have questions, if the EOI SSO can't do this, Austin Industries wants to turn this off and use the PDF form (paper form) until WORKTERRA can bring up the EOI SSO at the end of the enrollments of Life and Disability or at the end of enrolling so that the EE completes the EOI SSO..
          santosh.balid Santosh Balid (Inactive) made changes -
          Attachment screenshot-3.png [ 51688 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Attachment screenshot-4.png [ 51691 ]
          Hide
          santosh.balid Santosh Balid (Inactive) added a comment -

          Hello Tracy Kot,

          The process and image you described above is for admin user enrolling on behalf of employee or employee enrolling out-of workflow.

          As I gave you summary many times about this enhancement through emails or jira's, it seems you need a brief history of this enhancement, I will suggest you please go through every line of WT-7143, and all tickets associated with WT-7143 , every commutation happened for this enhancement is tracked in jira and then still if you have any concerns then please schedule a call with Austin people, we will discuss this over call.

          Still again providing you the shortcut to understand this quickly, I hope by going through this direction you will get your answers.

          Please start OE on stage for Austin, and with proper test employee traverse the OE workflow, you will notice for employee it is handled the same way as you suggested in previously and now again. Before beneficiary page you will get below page if you enrolled for EOI to CIGNA.

          I think , to go through every line mentioned in jira from starting, will be better , so that you can demonstrate client in right direction. If still have questions for me, please schedule a call for next week with Austin.

          Note: Though we have implemented workflow scenario and out-of workflow scenario differently, Could you please let me know your thoughts on below point.
          If we have to consider, implicitly employee/Admin will always click on "Cancel" button of the image you attached, then when should we process the "OK" button functionality implicitly or explicitly, because CIGNA SSO is a manual process where employee has to gone through their workflow, manually.

          Regards,
          Santosh

          Cc: Bharti Satpute, Samir, Satya, Vijay Siddha, Jaideep Vinchurkar, Aditya Vishwakarma

          Show
          santosh.balid Santosh Balid (Inactive) added a comment - Hello Tracy Kot , The process and image you described above is for admin user enrolling on behalf of employee or employee enrolling out-of workflow. As I gave you summary many times about this enhancement through emails or jira's, it seems you need a brief history of this enhancement, I will suggest you please go through every line of WT-7143 , and all tickets associated with WT-7143 , every commutation happened for this enhancement is tracked in jira and then still if you have any concerns then please schedule a call with Austin people, we will discuss this over call. Still again providing you the shortcut to understand this quickly, I hope by going through this direction you will get your answers. Please start OE on stage for Austin, and with proper test employee traverse the OE workflow, you will notice for employee it is handled the same way as you suggested in previously and now again. Before beneficiary page you will get below page if you enrolled for EOI to CIGNA. I think , to go through every line mentioned in jira from starting, will be better , so that you can demonstrate client in right direction. If still have questions for me, please schedule a call for next week with Austin. Note: Though we have implemented workflow scenario and out-of workflow scenario differently, Could you please let me know your thoughts on below point. If we have to consider, implicitly employee/Admin will always click on "Cancel" button of the image you attached, then when should we process the "OK" button functionality implicitly or explicitly, because CIGNA SSO is a manual process where employee has to gone through their workflow, manually. Regards, Santosh Cc: Bharti Satpute , Samir , Satya , Vijay Siddha , Jaideep Vinchurkar , Aditya Vishwakarma
          santosh.balid Santosh Balid (Inactive) made changes -
          Attachment screenshot-5.png [ 51692 ]
          Hide
          santosh.balid Santosh Balid (Inactive) added a comment -

          Tracy Kot, If you go through the earlier communication in Jira of this enhancements, then you will notice , the text of below popup is provided by you only, after your communication with Austin Industries, at that time.

          Regards,
          Santosh

          Cc: Bharti Satpute, Samir, Satya, Vijay Siddha, Jaideep Vinchurkar, Aditya Vishwakarma

          Show
          santosh.balid Santosh Balid (Inactive) added a comment - Tracy Kot , If you go through the earlier communication in Jira of this enhancements, then you will notice , the text of below popup is provided by you only, after your communication with Austin Industries, at that time. Regards, Santosh Cc: Bharti Satpute , Samir , Satya , Vijay Siddha , Jaideep Vinchurkar , Aditya Vishwakarma
          Hide
          Tkot Tracy Kot (Inactive) added a comment -

          Santosh Balid, I did put that in when Debbie, Chris and I spoke because we had decided on a wording update from what DEV had originally in wording. But when Austin was asked to test it, Austin's feedback was that the employee won't know how to answer that question. Per Austin, the Austin employees do not know the exact EOI rules, even if it was communicated to them, Austin feedback is they won't know how to answer it.

          Austin Questions:
          1) If the employee chooses CANCEL, and doesn't enroll in another benefit that requires EOI, will the pop up come up again? or will the employee not see the EOI SSO pop up again and not get another change to do the SSO EOI?
          2) If the employee chooses "OK" and gets the EOI SSO right away, EE does the EOI SSO, and then if EE enrolls in another benefit that does require EOI, will the EOI SSO come up again and time out like the original problem?

          Show
          Tkot Tracy Kot (Inactive) added a comment - Santosh Balid , I did put that in when Debbie, Chris and I spoke because we had decided on a wording update from what DEV had originally in wording. But when Austin was asked to test it, Austin's feedback was that the employee won't know how to answer that question. Per Austin, the Austin employees do not know the exact EOI rules, even if it was communicated to them, Austin feedback is they won't know how to answer it. Austin Questions: 1) If the employee chooses CANCEL, and doesn't enroll in another benefit that requires EOI, will the pop up come up again? or will the employee not see the EOI SSO pop up again and not get another change to do the SSO EOI? 2) If the employee chooses "OK" and gets the EOI SSO right away, EE does the EOI SSO, and then if EE enrolls in another benefit that does require EOI, will the EOI SSO come up again and time out like the original problem?
          Tkot Tracy Kot (Inactive) made changes -
          Assignee Tracy Kot [ tkot ] Santosh Balid [ santosh.balid ]
          Tkot Tracy Kot (Inactive) made changes -
          Assignee Santosh Balid [ santosh.balid ] Tracy Kot [ tkot ]
          Hide
          santosh.balid Santosh Balid (Inactive) added a comment -

          Tracy Kot, Please see answers to your queries.

          1) If the employee chooses CANCEL, and doesn't enroll in another benefit that requires EOI, will the pop up come up again? or will the employee not see the EOI SSO pop up again and not get another change to do the SSO EOI?
          Santosh: Have you gone through the employee workflow, if yes where you saw this popup, the popup is only for out-of workflow enrollment.

          2) If the employee chooses "OK" and gets the EOI SSO right away, EE does the EOI SSO, and then if EE enrolls in another benefit that does require EOI, will the EOI SSO come up again and time out like the original problem?
          Santosh: Are you still facing the timeout issue, if you face any issues after SSO screen opened, that needs to be discuss with CIGNA, because may be this is because of wrong data problem.

          Show
          santosh.balid Santosh Balid (Inactive) added a comment - Tracy Kot , Please see answers to your queries. 1) If the employee chooses CANCEL, and doesn't enroll in another benefit that requires EOI, will the pop up come up again? or will the employee not see the EOI SSO pop up again and not get another change to do the SSO EOI? Santosh: Have you gone through the employee workflow, if yes where you saw this popup, the popup is only for out-of workflow enrollment. 2) If the employee chooses "OK" and gets the EOI SSO right away, EE does the EOI SSO, and then if EE enrolls in another benefit that does require EOI, will the EOI SSO come up again and time out like the original problem? Santosh: Are you still facing the timeout issue, if you face any issues after SSO screen opened, that needs to be discuss with CIGNA, because may be this is because of wrong data problem.
          Hide
          satyap Satya added a comment - - edited

          Hi Tracy Kot,

          There has been several to & from going on this jira ticket. Can we schedule a call with Austin to go over implementation details of partner & employee side both.

          Proposed time: Friday, 16th June 2017, 7:30 AM PST
          Friday, 16th June 2017 at 8:30 AM PST

          Please let us know your preferred time & share meeting invite with Austin & us.

          Regards,
          Satya Prakash

          Cc: Santosh Balid Samir Vijay Siddha Jennifer Leugers Jaideep Vinchurkar Aditya Vishwakarma

          Show
          satyap Satya added a comment - - edited Hi Tracy Kot , There has been several to & from going on this jira ticket. Can we schedule a call with Austin to go over implementation details of partner & employee side both. Proposed time: Friday, 16th June 2017, 7:30 AM PST Friday, 16th June 2017 at 8:30 AM PST Please let us know your preferred time & share meeting invite with Austin & us. Regards, Satya Prakash Cc: Santosh Balid Samir Vijay Siddha Jennifer Leugers Jaideep Vinchurkar Aditya Vishwakarma
          Hide
          Tkot Tracy Kot (Inactive) added a comment -

          Thank you, let me see if I can get Austin comfortable with the process. If we need to meet I will let you know.
          Thank you for Satya for offering the meeting. Let me check to see if we need it.

          Show
          Tkot Tracy Kot (Inactive) added a comment - Thank you, let me see if I can get Austin comfortable with the process. If we need to meet I will let you know. Thank you for Satya for offering the meeting. Let me check to see if we need it.
          Hide
          Tkot Tracy Kot (Inactive) added a comment -

          Satya, Mandar Kulkarni Santosh Balid

          Hello, once you confirm you can remove the EOI SSO only for client Austin Industries, we can advise CIGNA too. This request is ONLY for Austin Industries.
          Please move the CIGNA SSO EOI for Austin Industries and put back the EOI process that populates the EOI PDF form.

          The client Austin Industries appreciates all the work that went in to the SSO EOI. But Austin knows their population well and feels that even though the SSO EOI for CIGNA/WORKTERRA technically works well and is accurate; that their Austin population will not know how to handle the pop up question. Austin did like it when each benefit had it’s own EOI message but CIGNA’s system timed out so that didn’t work. Austin is aware and realizes that the CIGNA side didn’t allow for that.

          Austin Industries would like to go back to the paper forms at this time. They just feel that with their employee population, the employee will not be able to go through the tunnel correctly and will not know how to answer the question on the pop up below. Their employees do not know which benefits or amounts require EOI and they depend on our tool to tell them that.

          For now, please remove the EOI SSO for Austin Industries client (only Austin) and put the paper / PDF EOI process back up.
          REQUEST: Per Austin’s request, could you consider an enhancement in the future (before their November OE hopefully) so that the system just pops up the EOI once the employee has enrolled in all life and disability benefits and has a pending EOI in WT? Is that possible to work towards? That way the employee is not answering if they need EOI or want to continue to enroll in a benefit that requires an EOI.

          CC Samir Vijay Siddha Jennifer Leugers Jaideep Vinchurkar Aditya Vishwakarma Deborah Mascot

          Show
          Tkot Tracy Kot (Inactive) added a comment - Satya , Mandar Kulkarni Santosh Balid Hello, once you confirm you can remove the EOI SSO only for client Austin Industries, we can advise CIGNA too. This request is ONLY for Austin Industries. Please move the CIGNA SSO EOI for Austin Industries and put back the EOI process that populates the EOI PDF form. The client Austin Industries appreciates all the work that went in to the SSO EOI. But Austin knows their population well and feels that even though the SSO EOI for CIGNA/WORKTERRA technically works well and is accurate; that their Austin population will not know how to handle the pop up question. Austin did like it when each benefit had it’s own EOI message but CIGNA’s system timed out so that didn’t work. Austin is aware and realizes that the CIGNA side didn’t allow for that. Austin Industries would like to go back to the paper forms at this time. They just feel that with their employee population, the employee will not be able to go through the tunnel correctly and will not know how to answer the question on the pop up below. Their employees do not know which benefits or amounts require EOI and they depend on our tool to tell them that. For now, please remove the EOI SSO for Austin Industries client (only Austin) and put the paper / PDF EOI process back up. REQUEST: Per Austin’s request, could you consider an enhancement in the future (before their November OE hopefully) so that the system just pops up the EOI once the employee has enrolled in all life and disability benefits and has a pending EOI in WT? Is that possible to work towards? That way the employee is not answering if they need EOI or want to continue to enroll in a benefit that requires an EOI. CC Samir Vijay Siddha Jennifer Leugers Jaideep Vinchurkar Aditya Vishwakarma Deborah Mascot
          Tkot Tracy Kot (Inactive) made changes -
          Assignee Tracy Kot [ tkot ] Satya [ ID10004 ]
          Hide
          santosh.balid Santosh Balid (Inactive) added a comment -

          Please refer attached email communication (RE Confirmation to off the CIGNA SSO EOI settings for Austin Industries )for the same.

          Show
          santosh.balid Santosh Balid (Inactive) added a comment - Please refer attached email communication (RE Confirmation to off the CIGNA SSO EOI settings for Austin Industries )for the same.
          santosh.balid Santosh Balid (Inactive) made changes -
          Assignee Satya [ ID10004 ] Tracy Kot [ tkot ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Attachment CIGNA_Success.jpg [ 52621 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Attachment NotEnrolledToCIGNA.jpg [ 52622 ]
          Hide
          santosh.balid Santosh Balid (Inactive) added a comment -

          Hello Tracy Kot,

          Please see my comments to your queries.

          For now, please remove the EOI SSO for Austin Industries client (only Austin) and put the paper / PDF EOI process back up.

          Santosh : Ok, we can off the CIGNA SSO EOI settings , so that by default they will get paper EOI functioning. But Could you please give us your feedback for below queries, which we had asked many times with your repeated queries again and again, because we have not received your feedback on that, yet.

          1. Have you gone through the employee workflow on stage environment for testing purpose of this feature?
          2. Have you done any enrollment into life and disability plans for test employee using workflow(OE)?
          3. Have you seen any such popup, which you have provided in below email thread, while doing enrollment through employee workflow(OE)?

          Please confirm whether we should off the CIGNA SSO EOI settings for Austin or we have to wait for a call schedule with Austin?

          Per Austin’s request, could you consider an enhancement in the future (before their November OE hopefully) so that the system just pops up the EOI once the employee has enrolled in all life and disability benefits and has a pending EOI in WT? Is that possible to work towards? That way the employee is not answering if they need EOI or want to continue to enroll in a benefit that requires an EOI.

          Santosh: As per our earlier discussion through WT-8924, Could you please schedule a call with Austin . If scheduling a call is not possible, then could you please give us contact details/email id of the respective Austin’s member to whom we can share the details of this feature.

          If still you want us to work on Austin’s requirement, then please create a separate jira ticket as a change request on which we have to work before Nov 17, put all the requirements into that jira. I hope you have gone through the employee workflow , which functions as below. I am repeating below things as usual , because I would like to confirm , whether you would like to change this functionality or what.

          Austin-CIGNA EOI through SSO using employee workflow :

          1. In workflow, If employee did enrollment into life and disability benefits for which EOI is required, till the end of workflow, we do not ask employee whether he would like to go for SSO or not.
          2. Till the end of workflow we store the employees EOI details into Workterra system only, if employee has done any EOI enrollment.
          3. Before beneficiary page , we show the below page to the employee, which contains all of the EOI enrollment details which requires SSO.

          4. On click of CIGNA SSO button , the above popup get appear which is a confirmation that , all the enrollments details has been enrolled into CIGNA system successfully, now you can go ahead with SSO part, by click on OK button, and do a required customization on CIGNA portal through SSO.

          5. In case of any issue while enrolling to CIGNA System, below popup gets appear.

          Please note that the purpose behind this enchantment was , to submit all enrollment details into single SSO request to CIGNA.

          Regards,
          Santosh

          Show
          santosh.balid Santosh Balid (Inactive) added a comment - Hello Tracy Kot , Please see my comments to your queries. For now, please remove the EOI SSO for Austin Industries client (only Austin) and put the paper / PDF EOI process back up. Santosh : Ok, we can off the CIGNA SSO EOI settings , so that by default they will get paper EOI functioning. But Could you please give us your feedback for below queries, which we had asked many times with your repeated queries again and again, because we have not received your feedback on that, yet. 1. Have you gone through the employee workflow on stage environment for testing purpose of this feature? 2. Have you done any enrollment into life and disability plans for test employee using workflow(OE)? 3. Have you seen any such popup, which you have provided in below email thread, while doing enrollment through employee workflow(OE)? Please confirm whether we should off the CIGNA SSO EOI settings for Austin or we have to wait for a call schedule with Austin? Per Austin’s request, could you consider an enhancement in the future (before their November OE hopefully) so that the system just pops up the EOI once the employee has enrolled in all life and disability benefits and has a pending EOI in WT? Is that possible to work towards? That way the employee is not answering if they need EOI or want to continue to enroll in a benefit that requires an EOI. Santosh: As per our earlier discussion through WT-8924 , Could you please schedule a call with Austin . If scheduling a call is not possible, then could you please give us contact details/email id of the respective Austin’s member to whom we can share the details of this feature. If still you want us to work on Austin’s requirement, then please create a separate jira ticket as a change request on which we have to work before Nov 17, put all the requirements into that jira. I hope you have gone through the employee workflow , which functions as below. I am repeating below things as usual , because I would like to confirm , whether you would like to change this functionality or what. Austin-CIGNA EOI through SSO using employee workflow : 1. In workflow, If employee did enrollment into life and disability benefits for which EOI is required, till the end of workflow, we do not ask employee whether he would like to go for SSO or not. 2. Till the end of workflow we store the employees EOI details into Workterra system only, if employee has done any EOI enrollment. 3. Before beneficiary page , we show the below page to the employee, which contains all of the EOI enrollment details which requires SSO. 4. On click of CIGNA SSO button , the above popup get appear which is a confirmation that , all the enrollments details has been enrolled into CIGNA system successfully, now you can go ahead with SSO part, by click on OK button, and do a required customization on CIGNA portal through SSO. 5. In case of any issue while enrolling to CIGNA System, below popup gets appear. Please note that the purpose behind this enchantment was , to submit all enrollment details into single SSO request to CIGNA. Regards, Santosh
          Hide
          Tkot Tracy Kot (Inactive) added a comment - - edited

          Santosh Balid received your notes above, thank you.
          I will review your notes in detail, I will reply to each question and go back through stage and test again before the end of day today.
          Yes, I can schedule a call with Austin. When are you available and I can check with Austin?
          Also, are you referring to STAGE name Austin OE 2017? Is that the STAGE name your updates are in?
          Per Santosh; Please confirm whether we should off the CIGNA SSO EOI settings for Austin or we have to wait for a call schedule with Austin? - Yes sir you can turn CIGNA SSO EOI off in PROD at this time, you don't have to wait for the call with Austin.

          Show
          Tkot Tracy Kot (Inactive) added a comment - - edited Santosh Balid received your notes above, thank you. I will review your notes in detail, I will reply to each question and go back through stage and test again before the end of day today. Yes, I can schedule a call with Austin. When are you available and I can check with Austin? Also, are you referring to STAGE name Austin OE 2017? Is that the STAGE name your updates are in? Per Santosh; Please confirm whether we should off the CIGNA SSO EOI settings for Austin or we have to wait for a call schedule with Austin? - Yes sir you can turn CIGNA SSO EOI off in PROD at this time, you don't have to wait for the call with Austin.
          Tkot Tracy Kot (Inactive) made changes -
          Assignee Tracy Kot [ tkot ] Santosh Balid [ santosh.balid ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Attachment CIGNA_Success.jpg [ 52770 ]
          Hide
          santosh.balid Santosh Balid (Inactive) added a comment -

          Hi Tracy Kot,

          Thanks for your feedback. We have turn off the CIGNA SSO EOI settings for Austin on production.

          On stage you can either refer "Austin" or "Austin OE 2017" , but please note that when you will enroll through OE, you will able to see the below page where all the EOI details get displayed.

          But , you may face issues on click of "CIGNA SSO" button, or nothing will happen on click of "CIGNA SSO" button. This is due to Aditya Vishwakarma recent changes for dependent enrollment for Symphony, are deployed on stage and for which is in testing phase. Aditya Vishwakarma , will rollback his changes by tommorrow, so that production and stage will be at same level and you can test even SSO page by tomorrow EOD. Till the time you can at-least check the above mentioned page. Hope this helps.

          Regards,
          Santosh

          Cc: Aditya Vishwakarma, Satya, Jaideep Vinchurkar

          Show
          santosh.balid Santosh Balid (Inactive) added a comment - Hi Tracy Kot , Thanks for your feedback. We have turn off the CIGNA SSO EOI settings for Austin on production. On stage you can either refer "Austin" or "Austin OE 2017" , but please note that when you will enroll through OE, you will able to see the below page where all the EOI details get displayed. But , you may face issues on click of "CIGNA SSO" button, or nothing will happen on click of "CIGNA SSO" button. This is due to Aditya Vishwakarma recent changes for dependent enrollment for Symphony, are deployed on stage and for which is in testing phase. Aditya Vishwakarma , will rollback his changes by tommorrow, so that production and stage will be at same level and you can test even SSO page by tomorrow EOD. Till the time you can at-least check the above mentioned page. Hope this helps. Regards, Santosh Cc: Aditya Vishwakarma , Satya , Jaideep Vinchurkar
          Hide
          santosh.balid Santosh Balid (Inactive) added a comment -

          Hi Tracy Kot,

          If you do enrollment for spouse as well in "Voluntary Dependent Life", then might be you don't face issue with "CIGNA SSO" button click.

          Regards,
          Santosh

          Show
          santosh.balid Santosh Balid (Inactive) added a comment - Hi Tracy Kot , If you do enrollment for spouse as well in "Voluntary Dependent Life", then might be you don't face issue with "CIGNA SSO" button click. Regards, Santosh
          Hide
          Tkot Tracy Kot (Inactive) added a comment - - edited

          My testing notes using QE noted below since I don't have an OE option: I did not see the pop up you noted above and I saw issues in dependent vol life.
          Santosh Balid, I did some more testing in STAGE NAME: Austin OE 2017
          But I did testing in QE, not OE so is that why I never saw the pop up you gave screenshot above? My testing didn't go well in QE. Here is my testing in QE.

          Here is my testing in QE of ChildBirth Adoption:
          STAGE NAME: Austin OE 2017
          EE is Lopez Abraham 6312, has 90K in vol life, did QE to increate vol life.
          Logged in as Admin: Did Birth of a child QE, 6/1. Added test child. Enroll now, increased vol life to 140K,
          If logged in as EE: al7660325, password is Workterr@

          Selected enroll, pop up box did appear stating “The Elections for Employee Voluntary Life have been changed successfully.” Clicked ok, this next box appears which is what Austin has given feedback the employees will not know how to answer, they will get confused and will most likely end up either not submitting it at all, thinking they did, or they will answer it wrong. Here is where I saw the pop up again that says "If you have enrolled in all benefits for life and disability .............................."

          I clicked cancel. I’m still in admin, clicked cancel, then I choose Dependent Life under the childbirth QE.
          Issue found in STAGE: There are no options under dependent life when I click on the drop down. The only option I get is Select Coverage. Is this an issue in STAGE? I have the Vol Life in force so not sure why I do not have options.
          Went back and signed in to the tunnel as though I am the EE and I never got EOI message at all for this QE ChildBirth Adoption.

          Do I have to test in OE?
          Let me know when I can test again:
          Here are the answers to your questions:

          Have you gone through the employee workflow on stage environment for testing purpose of this feature? I tested, notes above and I didn't see the pop up you noted called "you have successfully enrolled to CIGNA. Please click on OK to SSO to CIGNA". I did not see this message.
          2. Have you done any enrollment into life and disability plans for test employee using workflow(OE)? Yes I had done that testing before today and again today. Let me know when I can test again... I haven't see any new updates as I keep seeing that same pop up that Austin Doesn't like of "If you have enrolled in all benefits for life and disability......."
          3. Have you seen any such popup, which you have provided in below email thread, while doing enrollment through employee workflow(OE)? I don't have OE workflow in stage. Are you using Austin OE 2017 stage?

          Show
          Tkot Tracy Kot (Inactive) added a comment - - edited My testing notes using QE noted below since I don't have an OE option: I did not see the pop up you noted above and I saw issues in dependent vol life. Santosh Balid , I did some more testing in STAGE NAME: Austin OE 2017 But I did testing in QE, not OE so is that why I never saw the pop up you gave screenshot above? My testing didn't go well in QE. Here is my testing in QE. Here is my testing in QE of ChildBirth Adoption: STAGE NAME: Austin OE 2017 EE is Lopez Abraham 6312, has 90K in vol life, did QE to increate vol life. Logged in as Admin: Did Birth of a child QE, 6/1. Added test child. Enroll now, increased vol life to 140K, If logged in as EE: al7660325, password is Workterr@ Selected enroll, pop up box did appear stating “The Elections for Employee Voluntary Life have been changed successfully.” Clicked ok, this next box appears which is what Austin has given feedback the employees will not know how to answer, they will get confused and will most likely end up either not submitting it at all, thinking they did, or they will answer it wrong. Here is where I saw the pop up again that says "If you have enrolled in all benefits for life and disability .............................." I clicked cancel. I’m still in admin, clicked cancel, then I choose Dependent Life under the childbirth QE. Issue found in STAGE: There are no options under dependent life when I click on the drop down. The only option I get is Select Coverage. Is this an issue in STAGE? I have the Vol Life in force so not sure why I do not have options. Went back and signed in to the tunnel as though I am the EE and I never got EOI message at all for this QE ChildBirth Adoption. Do I have to test in OE? Let me know when I can test again: Here are the answers to your questions: Have you gone through the employee workflow on stage environment for testing purpose of this feature? I tested, notes above and I didn't see the pop up you noted called "you have successfully enrolled to CIGNA. Please click on OK to SSO to CIGNA". I did not see this message. 2. Have you done any enrollment into life and disability plans for test employee using workflow(OE)? Yes I had done that testing before today and again today. Let me know when I can test again... I haven't see any new updates as I keep seeing that same pop up that Austin Doesn't like of "If you have enrolled in all benefits for life and disability......." 3. Have you seen any such popup, which you have provided in below email thread, while doing enrollment through employee workflow(OE)? I don't have OE workflow in stage. Are you using Austin OE 2017 stage?
          Hide
          Tkot Tracy Kot (Inactive) added a comment -

          Also, Santosh Balid, let me know when you can meet with Austin and I can set up the call with Austin. But let's work through these issues internally first.

          Show
          Tkot Tracy Kot (Inactive) added a comment - Also, Santosh Balid , let me know when you can meet with Austin and I can set up the call with Austin. But let's work through these issues internally first.
          Hide
          Tkot Tracy Kot (Inactive) added a comment -

          Santosh Balid I also went back in to STAGE Austin OE 2017 and I turned on OE and I still do not see the pop up you are trying to show me.
          Please see my notes above too in my detail testing.
          Let me know when you want me to test again. I do not see the updates you noted.. Thank you very much!!

          Show
          Tkot Tracy Kot (Inactive) added a comment - Santosh Balid I also went back in to STAGE Austin OE 2017 and I turned on OE and I still do not see the pop up you are trying to show me. Please see my notes above too in my detail testing. Let me know when you want me to test again. I do not see the updates you noted.. Thank you very much!!
          Hide
          santosh.balid Santosh Balid (Inactive) added a comment -

          Hi Tracy Kot,

          Doesn't matter whether you do enrollment in QE or OE, only thing matter is whether you do enrollment in active workflow (e.g employee enrolling under OE workflow, where we consider implicitly that we will go for SSO at the end of workflow) or out of workflow( e.g Admin do enrollment on behalf of employee, where we implicitly can not decide when to go for CIGNA SSO, employee needs to take that decision)

          Issue found in STAGE: There are no options under dependent life when I click on the drop down. The only option I get is Select Coverage. Is this an issue in STAGE?

          Santosh: Might be plan configurations or employee eligibility is not set proper. Need to check with enrollment team.
          Could you please refer "Austin", and check if this issue is there as well.

          And yes to check the employee flow, you need to traverse through OE.

          Regards,
          Santosh

          Cc: Satya, Aditya Vishwakarma, Jaideep Vinchurkar

          Show
          santosh.balid Santosh Balid (Inactive) added a comment - Hi Tracy Kot , Doesn't matter whether you do enrollment in QE or OE, only thing matter is whether you do enrollment in active workflow (e.g employee enrolling under OE workflow, where we consider implicitly that we will go for SSO at the end of workflow) or out of workflow( e.g Admin do enrollment on behalf of employee, where we implicitly can not decide when to go for CIGNA SSO, employee needs to take that decision) Issue found in STAGE: There are no options under dependent life when I click on the drop down. The only option I get is Select Coverage. Is this an issue in STAGE? Santosh: Might be plan configurations or employee eligibility is not set proper. Need to check with enrollment team. Could you please refer "Austin", and check if this issue is there as well. And yes to check the employee flow, you need to traverse through OE. Regards, Santosh Cc: Satya , Aditya Vishwakarma , Jaideep Vinchurkar
          Hide
          santosh.balid Santosh Balid (Inactive) added a comment - - edited

          Hi Tracy Kot,

          I will be available to take a call with Austin on below dates.

          06/26 : 7:30 or 8:00 AM PST

          06/27 : 7:30 or 8:00 AM PST

          06/28 : 7:30 or 8:00 AM PST

          For your next round of testing, let me check , once Aditya Vishwakarma rollback his changes tomorrow, I will create one test employee and will share with you the credentials by starting OE on stage for Austin, so that it will be easy for you to test.

          Regards,
          Santosh

          Cc: Satya, Aditya Vishwakarma, Jaideep Vinchurkar, Rohan J Khandave

          Show
          santosh.balid Santosh Balid (Inactive) added a comment - - edited Hi Tracy Kot , I will be available to take a call with Austin on below dates. 06/26 : 7:30 or 8:00 AM PST 06/27 : 7:30 or 8:00 AM PST 06/28 : 7:30 or 8:00 AM PST For your next round of testing, let me check , once Aditya Vishwakarma rollback his changes tomorrow, I will create one test employee and will share with you the credentials by starting OE on stage for Austin, so that it will be easy for you to test. Regards, Santosh Cc: Satya , Aditya Vishwakarma , Jaideep Vinchurkar , Rohan J Khandave
          santosh.balid Santosh Balid (Inactive) logged work - 20/Jun/17 02:52 PM
          • Time Spent:
            4h
             

            Communication with Tracy kot, and testing on stage along with issue analysis due to Aditya's code deployment.

          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 175h 5m [ 630300 ] 179h 5m [ 644700 ]
          Worklog Id 56855 [ 56855 ]
          Hide
          santosh.balid Santosh Balid (Inactive) added a comment -

          Hello Tracy Kot,

          I created one employee for you , please use below credentials.

          User Name: th9991108
          Password: Test@1234
          Company Name: Austin OE 2017

          Currently this employee is eligible for below two CIGNA Life plans, so by enrolling into these two plans you will be able to view the "EOI details" page at the end before beneficiary page.

          1) Employee Voluntary Life
          2) Voluntary Dependent Life

          If you know how to set eligibility , then you can make this employee eligible for "LTD" and "STD" plans as well, but this is optional, if you know it well you can go for that as well.

          Please let me know your feedback once you go through the OE for above employee.

          Regards,
          Santosh

          Cc: Satya, Jaideep Vinchurkar, Aditya Vishwakarma, Rohan J Khandave

          Show
          santosh.balid Santosh Balid (Inactive) added a comment - Hello Tracy Kot , I created one employee for you , please use below credentials. User Name: th9991108 Password: Test@1234 Company Name: Austin OE 2017 Currently this employee is eligible for below two CIGNA Life plans, so by enrolling into these two plans you will be able to view the "EOI details" page at the end before beneficiary page. 1) Employee Voluntary Life 2) Voluntary Dependent Life If you know how to set eligibility , then you can make this employee eligible for "LTD" and "STD" plans as well, but this is optional, if you know it well you can go for that as well. Please let me know your feedback once you go through the OE for above employee. Regards, Santosh Cc: Satya , Jaideep Vinchurkar , Aditya Vishwakarma , Rohan J Khandave
          santosh.balid Santosh Balid (Inactive) made changes -
          Assignee Santosh Balid [ santosh.balid ] Tracy Kot [ tkot ]
          santosh.balid Santosh Balid (Inactive) logged work - 22/Jun/17 07:00 AM - edited
          • Time Spent:
            4h
             

            Dependent enrollment scenario implementation

          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 179h 5m [ 644700 ] 183h 5m [ 659100 ]
          Worklog Id 57735 [ 57735 ]
          Hide
          santosh.balid Santosh Balid (Inactive) added a comment -

          Hi Tracy Kot,

          I forgot that 06/26 is a holiday in India.
          So, Could you please reschedule call with Austin on 06/27 or 06/28 at the same time i.e 7:30 AM PST.

          Regards,
          Santosh

          Cc: Aditya Vishwakarma

          Show
          santosh.balid Santosh Balid (Inactive) added a comment - Hi Tracy Kot , I forgot that 06/26 is a holiday in India. So, Could you please reschedule call with Austin on 06/27 or 06/28 at the same time i.e 7:30 AM PST. Regards, Santosh Cc: Aditya Vishwakarma
          Hide
          Tkot Tracy Kot (Inactive) added a comment -

          Yes, we can reschedule. Let me check with Austin. No problem. I will update ticket.

          Show
          Tkot Tracy Kot (Inactive) added a comment - Yes, we can reschedule. Let me check with Austin. No problem. I will update ticket.
          santosh.balid Santosh Balid (Inactive) made changes -
          Worklog Id 57735 [ 57735 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 183h 5m [ 659100 ] 185h 5m [ 666300 ]
          Worklog Id 58032 [ 58032 ]
          Hide
          Tkot Tracy Kot (Inactive) added a comment -

          I sent the invite for: 06/28 : 7:30 or 8:00 AM PST

          Show
          Tkot Tracy Kot (Inactive) added a comment - I sent the invite for: 06/28 : 7:30 or 8:00 AM PST
          santosh.balid Santosh Balid (Inactive) logged work - 27/Jun/17 12:55 PM
          • Time Spent:
            3.5h
             
            <No comment>
          aditya.vishwakarma Aditya Vishwakarma (Inactive) logged work - 28/Jun/17 09:38 AM
          • Time Spent:
            1h
             

            -Client Call

          santosh.balid Santosh Balid (Inactive) logged work - 28/Jun/17 12:47 PM
          • Time Spent:
            1h
             

            Client Call

          Hide
          santosh.balid Santosh Balid (Inactive) added a comment -

          Hi Tracy Kot,

          We are in call, Please join the meeting.

          Regards,
          Santosh

          Show
          santosh.balid Santosh Balid (Inactive) added a comment - Hi Tracy Kot , We are in call, Please join the meeting. Regards, Santosh
          Hide
          Tkot Tracy Kot (Inactive) added a comment -

          Excellent demo/call, thank you and the team. That went very well.
          Austin Industries will test themselves some more and will provide feedback on Monday.

          Show
          Tkot Tracy Kot (Inactive) added a comment - Excellent demo/call, thank you and the team. That went very well. Austin Industries will test themselves some more and will provide feedback on Monday.
          santosh.balid Santosh Balid (Inactive) logged work - 29/Jun/17 12:49 PM
          • Time Spent:
            7.5h
             
            <No comment>
          aditya.vishwakarma Aditya Vishwakarma (Inactive) made changes -
          Time Spent 185h 5m [ 666300 ] 186h 5m [ 669900 ]
          Worklog Id 59934 [ 59934 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 186h 5m [ 669900 ] 187h 5m [ 673500 ]
          Worklog Id 60271 [ 60271 ]
          santosh.balid Santosh Balid (Inactive) logged work - 30/Jun/17 12:49 PM
          • Time Spent:
            7h
             
            <No comment>
          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 187h 5m [ 673500 ] 194h 35m [ 700500 ]
          Worklog Id 60275 [ 60275 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 194h 35m [ 700500 ] 201h 35m [ 725700 ]
          Worklog Id 60276 [ 60276 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 201h 35m [ 725700 ] 205h 5m [ 738300 ]
          Worklog Id 60335 [ 60335 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 205h 5m [ 738300 ] 210h 35m [ 758100 ]
          Worklog Id 60362 [ 60362 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 210h 35m [ 758100 ] 212h 35m [ 765300 ]
          Worklog Id 60368 [ 60368 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 212h 35m [ 765300 ] 218h 35m [ 786900 ]
          Worklog Id 60369 [ 60369 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 218h 35m [ 786900 ] 222h 35m [ 801300 ]
          Worklog Id 60373 [ 60373 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 222h 35m [ 801300 ] 227h 35m [ 819300 ]
          Worklog Id 60374 [ 60374 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Remaining Estimate 0h [ 0 ] 1h [ 3600 ]
          Time Spent 227h 35m [ 819300 ] 226h 35m [ 815700 ]
          Worklog Id 60362 [ 60362 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Remaining Estimate 1h [ 3600 ] 3h [ 10800 ]
          Time Spent 226h 35m [ 815700 ] 224h 35m [ 808500 ]
          Worklog Id 58032 [ 58032 ]
          Worklog Time Spent 2h [ 7200 ]
          santosh.balid Santosh Balid (Inactive) logged work - 03/Jul/17 01:13 PM
          • Time Spent:
            5.5h
             
            <No comment>
          santosh.balid Santosh Balid (Inactive) made changes -
          Assignee Tracy Kot [ tkot ] Santosh Balid [ santosh.balid ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Status Stage Testing [ 10201 ] Reopen in Stage [ 10023 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Status Reopen in Stage [ 10023 ] In Development [ 10007 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Item State Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) Parent values: Development(10200)Level 1 values: Ready for Review(10208)
          santosh.balid Santosh Balid (Inactive) made changes -
          Assignee Santosh Balid [ santosh.balid ]
          Code Reviewed By Santosh Balid [ 13300 ] Satya Prakash [ 12300 ]
          Developer Santosh Balid [ santosh.balid ]
          Stage Due Date 5/Jul/17 [ 2017-07-05 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Code Review Date 03/Jul/2017
          santosh.balid Santosh Balid (Inactive) made changes -
          Assignee Santosh Balid [ santosh.balid ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Item State Parent values: Development(10200)Level 1 values: Ready for Review(10208) Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213)
          rakeshr Rakesh Roy (Inactive) made changes -
          Status In Development [ 10007 ] Local Testing [ 10200 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Status Local Testing [ 10200 ] Pending for Stage Approval [ 10300 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Status Pending for Stage Approval [ 10300 ] Approved for Stage [ 10030 ]
          ashwin.wankhede Ashwin Wankhede (Inactive) made changes -
          Item State Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213) Parent values: LB QA(10201)Level 1 values: LB Deployed(11600)
          khandu.kshirsagar Khandu Kshirsagar (Inactive) made changes -
          Item State Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602)
          khandu.kshirsagar Khandu Kshirsagar (Inactive) made changes -
          Item State Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) Parent values: LB QA(10201)Level 1 values: LB Deployed(11600)
          priya.handepatil Priya Handepatil (Inactive) logged work - 05/Jul/17 11:56 AM
          • Time Spent:
            1h
             

            Meeting

          priya.handepatil Priya Handepatil (Inactive) made changes -
          Remaining Estimate 3h [ 10800 ] 2h [ 7200 ]
          Time Spent 224h 35m [ 808500 ] 225h 35m [ 812100 ]
          Worklog Id 60840 [ 60840 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Status Approved for Stage [ 10030 ] Stage Testing [ 10201 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Item State Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) Parent values: Stage QA(10202)Level 1 values: In Testing(10214)
          santosh.balid Santosh Balid (Inactive) logged work - 05/Jul/17 01:20 PM
          • Time Spent:
            6h
             

            Unit testing on stage + KT to QA

          santosh.balid Santosh Balid (Inactive) made changes -
          Remaining Estimate 2h [ 7200 ] 0h [ 0 ]
          Time Spent 225h 35m [ 812100 ] 231h 35m [ 833700 ]
          Worklog Id 60927 [ 60927 ]
          prasadp Prasad Pise (Inactive) logged work - 05/Jul/17 01:36 PM
          • Time Spent:
            3h
             

            Discussions, Analysis and Stage test scenarios executions with dev

          kunal.kedari Kunal Kedari (Inactive) logged work - 05/Jul/17 04:59 PM
          • Time Spent:
            1h
             

            Meeting and discussion about testing

          santosh.balid Santosh Balid (Inactive) made changes -
          Status Stage Testing [ 10201 ] Reopen in Stage [ 10023 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Status Reopen in Stage [ 10023 ] In Development [ 10007 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Status In Development [ 10007 ] Local Testing [ 10200 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Item State Parent values: Stage QA(10202)Level 1 values: In Testing(10214) Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213)
          santosh.balid Santosh Balid (Inactive) made changes -
          Status Local Testing [ 10200 ] Pending for Stage Approval [ 10300 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Status Pending for Stage Approval [ 10300 ] Approved for Stage [ 10030 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Account Executive Chris Ellenberger [ chris.ellenberger ]
          Code Review Date 03/Jul/2017 06/Jul/2017
          QA Prasad Pise [ prasadp ]
          khandu.kshirsagar Khandu Kshirsagar (Inactive) made changes -
          Item State Parent values: LB QA(10201)Level 1 values: Ready for Stage(10213) Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602)
          prasadp Prasad Pise (Inactive) made changes -
          Time Spent 231h 35m [ 833700 ] 234h 35m [ 844500 ]
          Worklog Id 61241 [ 61241 ]
          prasadp Prasad Pise (Inactive) made changes -
          QA Prasad Pise [ prasadp ] Kunal Kedari [ kunal.kedari ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Status Approved for Stage [ 10030 ] Stage Testing [ 10201 ]
          santosh.balid Santosh Balid (Inactive) logged work - 06/Jul/17 02:12 PM
          • Time Spent:
            2.5h
             

            Test Scenario generation and send to CIGNA

          santosh.balid Santosh Balid (Inactive) made changes -
          Item State Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) Parent values: Stage QA(10202)Level 1 values: In Testing(10214)
          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 234h 35m [ 844500 ] 237h 5m [ 853500 ]
          Worklog Id 61266 [ 61266 ]
          Hide
          santosh.balid Santosh Balid (Inactive) added a comment -

          Hi Tracy Kot,

          Did you received any feedback from Austin Industries.

          Regards,
          Santosh

          Cc: Rohan J Khandave, Aditya Vishwakarma

          Show
          santosh.balid Santosh Balid (Inactive) added a comment - Hi Tracy Kot , Did you received any feedback from Austin Industries. Regards, Santosh Cc: Rohan J Khandave , Aditya Vishwakarma
          ashwin.wankhede Ashwin Wankhede (Inactive) made changes -
          Item State Parent values: Stage QA(10202)Level 1 values: In Testing(10214) Parent values: LB QA(10201)Level 1 values: LB Deployed(11600)
          santosh.balid Santosh Balid (Inactive) logged work - 07/Jul/17 09:12 AM
          • Time Spent:
            4h
             

            Client Query resolution + Improvement in existing exception handling.

          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 237h 5m [ 853500 ] 241h 5m [ 867900 ]
          Worklog Id 61513 [ 61513 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Item State Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) Parent values: Stage QA(10202)Level 1 values: In Testing(10214)
          khandu.kshirsagar Khandu Kshirsagar (Inactive) made changes -
          Item State Parent values: Stage QA(10202)Level 1 values: In Testing(10214) Parent values: LB QA(10201)Level 1 values: LB Deployed(11600)
          santosh.balid Santosh Balid (Inactive) made changes -
          Item State Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) Parent values: Stage QA(10202)Level 1 values: In Testing(10214)
          santosh.balid Santosh Balid (Inactive) made changes -
          Time Spent 241h 5m [ 867900 ] 246h 35m [ 887700 ]
          Worklog Id 61724 [ 61724 ]
          ashwin.wankhede Ashwin Wankhede (Inactive) made changes -
          Item State Parent values: Stage QA(10202)Level 1 values: In Testing(10214) Parent values: LB QA(10201)Level 1 values: LB Deployed(11600)
          khandu.kshirsagar Khandu Kshirsagar (Inactive) made changes -
          Item State Parent values: LB QA(10201)Level 1 values: LB Deployed(11600) Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602)
          santosh.balid Santosh Balid (Inactive) made changes -
          Item State Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) Parent values: Stage QA(10202)Level 1 values: In Testing(10214)
          santosh.balid Santosh Balid (Inactive) made changes -
          Status Stage Testing [ 10201 ] Pending for Production Approval [ 10301 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Status Pending for Production Approval [ 10301 ] Approved for production [ 10034 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Item State Parent values: Stage QA(10202)Level 1 values: In Testing(10214) Parent values: Stage QA(10202)Level 1 values: Ready for Production(10217)
          Hide
          Tkot Tracy Kot (Inactive) added a comment -

          Santosh Balid, I followed up with Austin on Monday 7/3 and they needed more time to discuss internally at client's office. I am following up with Austin again today. I'm really hoping for approval so I will keep pushing client for the approval.

          Show
          Tkot Tracy Kot (Inactive) added a comment - Santosh Balid , I followed up with Austin on Monday 7/3 and they needed more time to discuss internally at client's office. I am following up with Austin again today. I'm really hoping for approval so I will keep pushing client for the approval.
          Hide
          Tkot Tracy Kot (Inactive) added a comment -

          Santosh Balid Per Austin Industries, they did test more in STAGE and they are happy with the CIGNA SSO now. There is only one item left before Austin approves the move to PROD and to turn it back on. Austin wants me to confirm with CIGNA that CIGNA can still accept the paper forms even if we go back live with the CIGNA SSO for EOI. I sent Erica at CIGNA a note to ask her. I'm waiting for her reply. If CIGNA confirms that they can still take the paper EOI forms (if EEs submit it) even if we go live with the CIGNA SSO then Austin will approve the CIGNA SSO EOI.

          Show
          Tkot Tracy Kot (Inactive) added a comment - Santosh Balid Per Austin Industries, they did test more in STAGE and they are happy with the CIGNA SSO now. There is only one item left before Austin approves the move to PROD and to turn it back on. Austin wants me to confirm with CIGNA that CIGNA can still accept the paper forms even if we go back live with the CIGNA SSO for EOI. I sent Erica at CIGNA a note to ask her. I'm waiting for her reply. If CIGNA confirms that they can still take the paper EOI forms (if EEs submit it) even if we go live with the CIGNA SSO then Austin will approve the CIGNA SSO EOI.
          khandu.kshirsagar Khandu Kshirsagar (Inactive) made changes -
          Item State Parent values: Stage QA(10202)Level 1 values: Ready for Production(10217) Parent values: Production QA(10203)Level 1 values: Production Deployed(10221)
          santosh.balid Santosh Balid (Inactive) made changes -
          Status Approved for production [ 10034 ] Production Testing [ 10202 ]
          santosh.balid Santosh Balid (Inactive) made changes -
          Item State Parent values: Production QA(10203)Level 1 values: Production Deployed(10221) Parent values: Production QA(10203)Level 1 values: In Testing(10218)
          santosh.balid Santosh Balid (Inactive) made changes -
          Item State Parent values: Production QA(10203)Level 1 values: In Testing(10218) Parent values: Production Complete(10222)
          santosh.balid Santosh Balid (Inactive) made changes -
          Summary Symphony-CIGNA EOI processing for Dependent Enrollment Austin-CIGNA EOI processing for Dependent Enrollment
          santosh.balid Santosh Balid (Inactive) made changes -
          Assignee Santosh Balid [ santosh.balid ] Tracy Kot [ tkot ]
          Resolution Done [ 10000 ]
          Status Production Testing [ 10202 ] Production Complete [ 10028 ]
          Hide
          santosh.balid Santosh Balid (Inactive) added a comment -

          Hi Tracy Kot,

          Thanks for updates. Please close this ticket , once you got a confirmation from Austin that everything is working fine.
          This ticket was specifically for spouse enrollment scenarios demanded by CIGNA, and those are already available till production.

          We did testing for same for Symphony, but we haven't tested spouse enrollment scenarios for Austin, as now on production SSO is off for Austin. But we don't think there will be any issue for spouse enrollment scenarios, as those are CIGNA specific and not client specific, so same process applicable for both Symphony and Austin. If in future CIGNA demanded from us that send spouse enrollment test scenarios for Austin as well, then will do the needful.

          Regards,
          Santosh

          Show
          santosh.balid Santosh Balid (Inactive) added a comment - Hi Tracy Kot , Thanks for updates. Please close this ticket , once you got a confirmation from Austin that everything is working fine. This ticket was specifically for spouse enrollment scenarios demanded by CIGNA, and those are already available till production. We did testing for same for Symphony, but we haven't tested spouse enrollment scenarios for Austin, as now on production SSO is off for Austin. But we don't think there will be any issue for spouse enrollment scenarios, as those are CIGNA specific and not client specific, so same process applicable for both Symphony and Austin. If in future CIGNA demanded from us that send spouse enrollment test scenarios for Austin as well, then will do the needful. Regards, Santosh
          kunal.kedari Kunal Kedari (Inactive) made changes -
          Time Spent 246h 35m [ 887700 ] 247h 35m [ 891300 ]
          Worklog Id 62847 [ 62847 ]
          Hide
          santosh.balid Santosh Balid (Inactive) added a comment -

          Hi Tracy Kot,

          Please close this ticket , if Austin has no issue. We already had provided all possible test cases to CIGNA, and all get executed successfully. CIGNA had already approved it for both Stage and Production.

          Please refer attached email for more details.

          Regards,
          Santosh RE Symphony-Austin-CIGNA EOI processing for Dependent Enrollment.msg

          Show
          santosh.balid Santosh Balid (Inactive) added a comment - Hi Tracy Kot , Please close this ticket , if Austin has no issue. We already had provided all possible test cases to CIGNA, and all get executed successfully. CIGNA had already approved it for both Stage and Production. Please refer attached email for more details. Regards, Santosh RE Symphony-Austin-CIGNA EOI processing for Dependent Enrollment.msg
          Tkot Tracy Kot (Inactive) made changes -
          Resolution Done [ 10000 ] Fixed [ 1 ]
          Status Production Complete [ 10028 ] Closed [ 6 ]
          Transition Time In Source Status Execution Times
          Aditya Vishwakarma (Inactive) made transition -
          New Request Pending for Approval
          30d 22h 59m 1
          Aditya Vishwakarma (Inactive) made transition -
          Pending for Approval Approved for Development
          4s 1
          Aditya Vishwakarma (Inactive) made transition -
          Approved for Development In Development
          2s 1
          Santosh Balid (Inactive) made transition -
          Stage Testing Reopened in Stage
          59d 15h 49m 2
          Santosh Balid (Inactive) made transition -
          Reopened in Stage In Development
          9s 2
          Santosh Balid (Inactive) made transition -
          In Development In LB Testing
          15d 17h 59m 3
          Santosh Balid (Inactive) made transition -
          In LB Testing Pending for Stage Approval
          16m 5s 3
          Santosh Balid (Inactive) made transition -
          Pending for Stage Approval Approved for Stage
          13s 3
          Santosh Balid (Inactive) made transition -
          Approved for Stage Stage Testing
          15h 22m 3
          Santosh Balid (Inactive) made transition -
          Stage Testing Pending for Production Approval
          3d 22h 49m 1
          Santosh Balid (Inactive) made transition -
          Pending for Production Approval Approved for production
          8s 1
          Santosh Balid (Inactive) made transition -
          Approved for production In Production Testing
          18h 21m 1
          Santosh Balid (Inactive) made transition -
          In Production Testing Production Complete
          3h 27m 1
          Tracy Kot (Inactive) made transition -
          Production Complete Closed
          14d 2h 22m 1

            People

            Assignee:
            Tkot Tracy Kot (Inactive)
            Reporter:
            aditya.vishwakarma Aditya Vishwakarma (Inactive)
            Account Executive:
            Chris Ellenberger
            Developer:
            Santosh Balid (Inactive)
            QA:
            Kunal Kedari (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Pre-Prod Due Date:
              Code Review Date:

                Time Tracking

                Estimated:
                Original Estimate - 80h Original Estimate - 80h
                80h
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 247h 35m
                247h 35m