Tech Portal "Completed" history duration

Even if we modify the lobby to increase the days, the resulting page - page/ServiceTechnicianTaskExeuction/AssignmentCompleted seems to have it hardcoded to 30 days.

Hi ​@athasanka 

Kindly note that what you have observed is correct.

We have reviewed the related SELECT query used to fetch data for the window "My Assignments - Completed". Based on our analysis, the query retrieves data with the following conditions as well,

1. The state is 'COMPLETED', 'INCOMPLETED', or 'CANCELLED'.
2. It checks the Work Finish Date:
If the Work Finish Date is empty, the data is fetched without date filtering.
If a Work Finish Date exists, the data is fetched for assignments completed within the last 30 days from the system date.

As a result:
For assignments in the COMPLETED state, only records from the last 30 days are fetched.
For assignments in the CANCELLED state, there is no filtering based on the Work Finish Date, so all relevant data is displayed.

This value is hard coded: (work_finish IS NULL OR trunc(work_finish) >= trunc(sysdate - 30))

I cannot confirm the reason, but it can be that, if more and more data is displayed, it might affect the performance of the technician portal. However, our Product Development team will have more information on this.

Best Regards,

Thilini

Thanks Thilini,

It doesn’t make sense to apply a hard-coded 30-day limit on the select logic and again on the lobby data source. Should have been applied only on the lobby data source, allowing it to be configurable to the customers to modify the where conditions considering the system performance. 

This causes the “completed” area practically useless for us as our techs need to see farther than 30 days.

The lobby datasource has a few conditions applied.

But the element navigation simply directs to the destination page, completely disregarting the conditions on the datasource. Sounds like a disjoint somewhere?