-
Type:
Bug
-
Status: Production Complete
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: ACA
-
Labels:None
-
Environment:Production
-
Bug Type:Functional
-
Bug Severity:Medium
-
Level:Admin, Partner
-
Module:ACA - 2017
-
Reported by:Harbinger
-
Item State:Production Complete - Closed
-
Issue Importance:Must Have
When we run any 1095-C report, we lock the report by setting a flag IsLocked to true under ACA_1095CLockReportRun table and then release it after the process is completed.
But in-case if any error occurred in between of the processing then the lock is not released and user is not able to re-run that particular report again. (It shows no-records found message )
We have verified above mentioned issue on stage [ASML for Hspl].
Its working fine.
Tested scenarios are as follows.
1.Checked whether no error received while downloading the report when error occurred while processing previous run.
2.Checked there is no entry of previous run for which report was locked.
3.There was message of 'No records found' when report was locked.
This fix is ready for stage.
Fix is ready for production.
Smita Pawar (Inactive)
added a comment - We have verified above mentioned issue on stage [ASML for Hspl] .
Its working fine.
Tested scenarios are as follows.
1.Checked whether no error received while downloading the report when error occurred while processing previous run.
2.Checked there is no entry of previous run for which report was locked.
3.There was message of 'No records found' when report was locked.
This fix is ready for stage.
Fix is ready for production.
We have verified above mentioned issue on LB and Azure environment.
Its working fine.
Tested scenarios are as follows.
1.Checked whether no error received while downloading the report when error occurred while processing previous run.
2.Checked there is no entry of previous run for which report was locked.
3.There was message of 'No records found' when report was locked.
This fix is ready for stage.
Smita Pawar (Inactive)
added a comment - We have verified above mentioned issue on LB and Azure environment.
Its working fine.
Tested scenarios are as follows.
1.Checked whether no error received while downloading the report when error occurred while processing previous run.
2.Checked there is no entry of previous run for which report was locked.
3.There was message of 'No records found' when report was locked.
This fix is ready for stage. Hi Smita Pawar,
I have committed code for this JIRA to LB (old) & Ui-Refresh also , so please make sure that you test this on both the environment as we need to push this JIRA to production also.
The fix will be deployed after tomorrow's build.
Please revert in-case you have any queries.
Thanks,
Kumar Chhajed
We have verified above mentioned issue on Production. [Asml for hspl]
1.Checked whether no error received while downloading the report when error occurred while processing previous run.
2.Checked there is no entry of previous run for which report was locked.
3.There was message of 'No records found' when report was locked.
Its working fine.