I have updated specs based on meeting on 5/11/2017. [^OE-Dashboard-RequirementsV2.0.docx]

Hi All,

While going through document, We have come up with an suggestion which will avoid need to sync system data with dashboard data.

We will have data structure ( table ) to hold only user input values of OE dashboard and not for the values which are sourced from system data.

While listing templates, we will get templates which are on scheduler with system information like templates flags, group template name, schedule details etc, along with this if there is an information present for particular template in dashboard data structure then will also show those along with system information, if there is nothing in dashboard data structure for a particular template then we'll show only system information along with empty ( blank ) user input values.

We can update OE start date and end date from company information page to dashboard data structure in real time. So whenever OE dates are entered/updated on company information page, we can update same dates including logic of earliest effective date in case of multiple open enrollments to dashboard data structure.

All other logic of background process will remain same on dashboard data. Let us know your views on same.

Vinayak Kulkarni - your suggestions are great.
As I understand, you are talking about the implementation detail and there is no change in the functionality (that is exposed to the user) envisaged in the requirement document.
Thanks!

Vinayak Kulkarni - I have uploaded a slightly revised version. [^OE-Dashboard-RequirementsV2.1.docx]
Have added the following in the requirements.
Note: User update of OE dates needs to be synchronized with all other templates of that company. In other words, when OE dates for a template are edited by the user, OE dates on all templates belonging to that company need to be updated.

CC Amit Thorve Satya

Hi Abhay Patil

Noted it.

Actually during analysis and mock-ups discussion, we came up with new idea to have two tables instead of showing everything in one table on screen.

First table would contain only company specific data and OE dates goes there and second table would contain template specific data. By this we need to update OE dates for company which will be considered for all the template on that company.

This might be little confusing to you right now. We are creating two mock-ups, first that we had discussed in call ( single row for every template ) and second one which i mentioned above.

Once we are done with mock-ups then we can have call to discuss both to make everyone on same page.

Hi Abhay Patil and Amit Thorve

We would be done with Mock-ups creation soon,
Can we have call on 06/02/2017 at 10am IST to discuss these mock-ups?

Thanks,
Vinayak

Vinayak Ghanwat Satya

Sure Vinayak Kulkarni - please schedule and send calendar invite for the meeting.

Vinayak Kulkarni I am fine with the time as well.

Hi Amit Thorve Abhay Patil,

As we discussed, here I have attached OE dashboard mockups, Please go through it and share your feedback.
OE Dashboard.zip

Vinayak KulkarniSatya

Thanks,
Vinayak G

Attached Mockups as discussed in call.

Abhay Patil, Amit Thorve; Please let us know your feedback on this.

Regards,
Satya Prakash

Cc: Vijay Siddha Vinayak Kulkarni Vinayak Ghanwat

I have uploaded the latest version of the requirement document. I have added a few questions too.

I have not commented on option 1 and 2. As per the meeting, we recommend one row per template where company information is repeated.

This looks good to me. Abhay Patil, Cindy Wibbing Please check this.

Thanks Vinayak Ghanwat - this is good.
Vinayak Kulkarni, Satya Amit Thorve - please see the updated requirements document, especially for filters, grid management, import/export and data constraints.

Hi Abhay Patil Amit Thorve

We have some queries related to how filters would be shown on screen and wanted to discuss to clear those queries, Can we have a call tomorrow 06/08/2017 at 10am IST to discuss this?
If yes, I will send meeting invite for the same. Thanks.

Gaurav Sodani Vijay Siddha Satya Ganesh Sadawarte

Vinayak Kulkarni I am not available at 10.00am IST. Can we have this meeting at 8.00am IST or 11.00am IST?

11:00am will be fine with us, Abhay Patil is this fine with you?

Vinayak Kulkarni Amit Thorve - yes 11 AM IST (i.e. 10:30 PM PST) will be okay for me. Please send me the invite.

Amit Thorve Abhay Patil Gaurav Sodani Ganesh Sadawarte Punam Satpute Pallavi Kulkarni Aniruddha Dev

Hi All,

Thanks for taking out your time. Please find the MoM of our discussion today(06/08/2017).

1. UI:

• The approach shown by Vinayak for Advance filter is good to go with.
• "Blank" or "Empty" option will be shown for each Advance filter which will indicate filter is applied with blank value
• Multiple select as well as Single select will be applicable based on the values the specific filter carries

2. Concurrent usage of dashboard by multiple users

• Team needs to discuss with Amit and finalize the approach on the change control and refresh approach, this is a specific condition when 2 or more concurrent users are working on the OE dashboard at once

3. OE dashboard separate table

• Harbinger team needs to decide whether OE dashboard will be using the system data to pull out filer specific data or maintaining a separate table for OE dashboard. This has been proposed in order to decrease the latency that would be caused because of the huge amount of data which needs to be scanned. However, harbinger team needs to consult the Performance team and understand the current implementation latency

4. Blackout Period:

• The requirement is understood
• Amit to confirm on which date needs to be considered for swapping the Flag from YES to NO and shifting schedule to next enrollment year.
• File due date
• File sent date

Please add if anything is missing here. Thanks.

Abhay Patil,Vinayak Kulkarni,Gaurav Sodani,Pallavi Kulkarni,Punam Satpute

Hi Amit Thorve,

Please check below summary of our discussion.

1) We will update open enrollment dashboard data at same time whenever any field get changed in the system which is referenced in open enrollment dashboard, so we don't need any sync service.

2) We will have another input column on open enrollment dashboard for black out period, which will have default value to 'Yes', if some one don't want to consider as black out period for that specific template then set value to 'No'. The value of this input will determine whether to shift schedule start date to next enrollment year.

3) OE file Due date will consider to set current year flag to 'No' and set schedule start date to next enrollment year.

4) While importing data,keep only those rows which we want to update into open enrollment dashboard and delete other rows from excel file. Also we will show the note on open enrollment dashboard.

5) If user enter open enrollment start date and end date then it will populate for all templates of that same company.

6) Once open enrollment start date and end date are entered into company information and reflected into OE dashboard then user should not be able update again. We will show those fields as non editable.

7) We need to check for new template as well as new company is added in WT. While adding new company will add this point into our check list.

8) Configuration Screen - User access restriction of import/export functionality.

Thanks,
Ganesh

Looping Nagini to OE dashboard thread++

CC Nagini Indugula

Regards
Gaurav

Amit Thorve,Abhay Patil,Vinayak Kulkarni,Gaurav Sodani,Pallavi Kulkarni,Punam Satpute

Hi All,

There are total 31 fields given in OE dashboard and out below three fields are not exits in system. so we are implementing these fields into system as part of OE dashboard development.

1) Client Executive
2) EDI Executive (for Company) .
3) Carrier Contact.

There is an enhancement WT-9262 which need implementation of Client Executive and EDI Executive (for Company) fields in system. As per requirement document if these fields are implemented in the system then we need to show this as read only on open enrollment dashboard. So we will display it as text as we are implementing those into system, if no value selected then blank will populate on dashboard.

Thanks,
Ganesh

Attaching screenshot of current developed page.

Note: Development is in progress and few small changes are still pending.

Hi Amit Thorve and Abhay Patil

We got one query about shifting Schedule start day to first day of next enrollment year.

Here we are fine with company level template which are on scheduler, we can get next enrollment year's start date from company information.

But, How about group level templates? they can have multiple companies involved and which companies enrollment period should we look for?

Shall we look enrollment period for any one of the group companies or we shall not update schedule for group templates? let us know your views on the same. Thanks.

Vinayak Kulkarni and Abhay Patil Here is what I feel should happen for Group Level Templates:

1. The Black Out Period flag should be set to YES for all company level feeds under group level (if Black out Period needs to be set).
2. If Black Out period flag is set to NO for any company feed under group level feed then Black Out period is considered as NO for that global level feed.
3. If multiple companies feeds are grouped under Global Level feed and if those companies have different financial year in that case financial year of the first company in the sequence is considered to set the schedule.

*Note: *As per my advice, we should not set black out period for global feeds which consists of multiple company level feeds having different financial year.

CC-Cindy Wibbing, Van Nguyen, Chris Ellenberger, Damion M Velasquez, Kevin Hale, Rochelle Thomas, Nathaniel Cornejo-Walker

Amit Thorve
While doing a demo for the CE and CT teams today it was brought to our attention that the values set on the company page for Fiscal Start and Fiscal End dates is not driven by the renewal date for Open Enrollment but can be setup based on such things as life plans for the company. The company may have a renewal date of January 1 but have the Fiscal Settings on the company page set to July 1 because of the way the salary updates need to be addressed.

In light of this information it sounds like we may need to make adjustments to the OE Dashboard to pull the renewal information instead of these fields.

Vinayak Kulkarni We need to check this out. Based on Cindy's above mentioned comment, we might need to keep this field editable. We will populate the values based on Fiscal year settings from Company Info but will allow the user to override the same.

Adding testing feedback reported by Van Nguyen.

Error:
Austin: template: TEST VSP Van
“EDI Analyst” field. I tried to overwrite this field with “Van Nguyen,” but I got a message stating “No changes found” after I clicked “Save.”

In “Advanced Filtering,” there’s no option to “Check All” or “Uncheck All”

Success:
“OE Start Date” field. I added 10/01/2017 and it saved successfully.
“OE End Date” field. I added 10/31/2017 and it saved successfully.
“OE File Due Date” field. I added 12/01/2017 and it saved successfully.
“Is New Structure” field. I clicked on the checkbox and it saved successfully.
“OE File Sent Date” field. I added 12/01/2017 and it saved successfully.
“Carrier Confirmation Date” field. I added 12/5/2017 and it saved successfully.
“Data Discrepancies Processed” field. I added 12/6/2017 and it saved successfully.

Hi Abhay Patil,

We have created JIRA WT-10864 for above issue.

Please check and let us know if you have any questions.

Thanks,
Ganesh

Hi Abhay and Amit,

We need to discuss below one point related to OE dashboard.

Currently, Whenever someone enters OE dates on company information page then those dates gets reflected into dashboard and after that those date cannot be modified from dashboard.

For this year, there won't be any problems with this, However when we go to next year and come closer to next year's OE then these dates will still be there and user cannot modify it as those dates were entered on Company information.

One solution to this could be reset "updated from company" flag ( we use this to determine whether to allow user to modify OE dates ) on a particular date automatically.
This date could be OE end date of respective company. Let us know your views on same. Thanks.

Hi Vinayak Kulkarni and Ganesh Sadawarte,

Take a note of below observations:-

1.As per implementation , During File importing we have to delete rows for the templates which we dont want to change as they are not reflected on OE dashboard,but when we insert any another value in deleted rows,it will create bad file for that with unknown Company ID .

2.All data flushed out after making schedule off for Group / Company level templates,i.e values saved before scheduling off ,it will not persists on Dashboard again.(Editable fields such as EDI analyst,OE start date ,End date)

3.: If OE start date and OE end date are editable from OE dashboard,after exporting it as per implementation ,we can change Dates from exporte file and Insert new dates,But for one company it should reflect one OE start date or end date for all templates ,which is not handled for importing.
For example, If OE start date is 09/06/2017 and OE end date is 09/07/2017 for all templates , when we export it and done changes for only one template as OE start date 06/01/2017 and OE end date 06/06/2017 then it is only reflected for one template as shown in attachment below.
It is causing discrepancy.

CC-Amit ThorveAbhay PatilHrishikesh DeshpandeAniruddha DevGaurav SodaniRakesh Roy

As all linked WT tickets are assigned to QA, assigning parent ticket to QA as well.