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

Hello Tracy Kot & Chris Ellenberger

Is there any update regarding previous message?

Thanks

cc: Satya Santosh Balid Prasanna Karlekar , Jennifer Leugers

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

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

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

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

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

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

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

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

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

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.

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.

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

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

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

For Austin creating separate ticket WT-9412

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

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.

Hi Tracy Kot

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

Thanks

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

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..

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

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

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?

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.

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

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.

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

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

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

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.

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

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

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?

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.

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!!

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

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

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

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

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

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

Hi Tracy Kot,

We are in call, Please join the meeting.

Regards,
Santosh

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.

Hi Tracy Kot,

Did you received any feedback from Austin Industries.

Regards,
Santosh

Cc: Rohan J Khandave, Aditya Vishwakarma

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.

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.

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