-
Type:
Enhancement
-
Status: Closed
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: ACA
-
Labels:None
-
Module:ACA - 2017
-
Reported by:Harbinger
-
Item State:Production Complete - Closed
-
Issue Importance:Good To Have
-
Feature Category:Integration
-
Severity:Simple
As we came across a scenario while furnishing the request of Austin company for conditional codes(1J/1K), An idea popped into my mind.
The earlier implementation of Multi-Employer Eligibility Rule is only for 1H/2E Codes,
the change in this implementation is that, user can add the choice of codes which he/she want to display on PDF.
Actual implementation -
After selecting Multi Employer Eligibility Rule on 1095-C Report user can enter Line 14 Code,Line 15 Cost & Line 16 code into the text boxes and those inputs will be considered for those bunch of employees falling under that rule.
- relates to
-
WT-9199 ACA 2017 Safe harbor cost should also be taken as input on ACA 1095C Class wise rate configuration
-
- Closed
-
-
WT-10209 UI refresh_Getting server error on clicking of SAVE & Preview
-
- Rejected
-
-
WT-10738 ACA_Suggestion_ We need to add note 'if any new employee is added under the rule need to re-save the configuration' on Class wise configuration screen.
-
- Closed
-
-
WT-11385 ACA 2017 PDF Key Changes
-
- Closed
-
-
- Time Spent:
- 5h
-
Coding
Unit testing
Internal discussion with nandu
-
- Time Spent:
- 5h
-
Coding
Unit testing
Internal discussion
-
- Time Spent:
- 1.5h
-
Changes for Ui refresh branch
-
- Time Spent:
- 4h
-
Coding
Internal discussion
Unit testing
-
- Time Spent:
- 4.5h
-
Coding
Unit testing
-
- Time Spent:
- 4h
-
Unit testing
Coding
Internal discussion with Ramya and Nandu
-
- Time Spent:
- 5h
-
Coding
Documentation
Internal discussion
Unit testing
-
- Time Spent:
- 4h
-
Analysis and test scenario preparation
-
- Time Spent:
- 3h
-
Unit testing
Coding
Internal discussion
-
- Time Spent:
- 4h
-
Unit testing
Code Review
Code Review Changes
Internal discussion
-
- Time Spent:
- 3h
-
Test cases completion
Jira updates
-
- Time Spent:
- 1h
-
Stage testing & Internal discussion with Rutuja
-
- Time Spent:
- 0.5h
-
Internal discussion with Rutuja
-
- Time Spent:
- 1h
-
Internal Discussion with Mahendra
-
- Time Spent:
- 1h
-
Bug verification on Production.
-
- Time Spent:
- 0.25h
-
Jira updates and discussion