When users try to find a document on the new live site, expected documents do not show up.

Dispute documents search field does not work (15-Jan-21).mp4 2.93 MB • Download

Hi Harsh ,

In addition to the above and further to the video, the loading times for generating results within the filters is very slow, could you please ensure these are sped up so that auto-suggest options are presented instantaneously.

Thanks,

Morgan

Dispute Documents search and filters (2-Feb-21).mp4 2.13 MB • Download

Hi Morgan and Paul ,

This issue is resolved on staging.islg. Please check and confirm.

Hi Harsh ,

The keyword search appears to be working on staging.islg; however, I'll let Naomi and Melissa confirm that it meets all the requirements in UAT.

However, as described in video below, I found issues with the filters and sorting options in the tools:

Problems with Disputes and Dispute Documents search (1-Mar-21).mp4 4.68 MB • Download

Further to the second video below, it appears that Dispute results always present the results with the Dispute branch open. Would it be an easy change to make it so that results are presented with the Dispute branch closed? Naomi and Melissa please comment if you foresee any problems with the UX if we implemented this change.

Problems with Disputes and Dispute Documents search results (1-Mar-21).mp4 11.3 MB • Download

Thanks,

Morgan

Hi Morgan ,

As decided in last call, We have displayed only Dispute node branches after search and when user click on + icon then relevant result are displayed based on dtsearch.

Please check on staging.islg and confirm.

Thanks Harsh ​.

Naomi ​, could you please test and confirm that this meets the requirements we discussed.

Thanks,

Morgan

Hi Harsh ,

Could you confirm whether the search and filters within Dispute & Dispute Documents is working, because I just attempted to use it and was unable to make it work.

Morgan

Hi Morgan ,

We checked and it is working. Please check on staging.islg. We haven't deployed on app.islg.

Hi Harsh ,

Ok. It appears to be running, but very slowly. It took more than 30 seconds for me to apply a simple date range filter. I thought we agree that shouldn't take more than a few seconds to produce results?

Thanks,

Morgan

Hi Morgan ,

I discussed with Radomir for same but he said without Paging it is taking time to get response.

You can communicate with Radomir for same.  If you filter without any search keyword then it is taking some time. It depends on data which you filter.

Harsh , this isn't acceptable. We can't have filtering take 30 seconds to return a results. Please reconnect with Radomir and come up with a solution. 

Morgan

Hi Morgan ,

Is it possible to we make Search Keyword Mandatory for Dispute Document module same as FTS. Probably this will help us to get result faster ?

Hi Harsh ,

No, we need to be able to use the filters without a keyword. Users need to be able to use the filters to navigate through documents. For example, a common query will be, "I want to find all documents between 2010 and 2015." This will require applying the date range filters without a keyword.

Morgan

OK Morgan . Then Radomir need to work on to provide search response faster from indexing.

Ok. Please connect with him and provide him with instructions on what needs to be resolved, but Harsh you're in charge of delivery the features in the application, so please ensure that you're accountable to ensuring the searches perform at an acceptable level before the next deployment. 

Thanks,

Morgan

Yes Morgan .  As per criteria given we have implemented but if search result is taking time then Radomir needs to work on that as we can not handle it from our end.

Ok, Harsh , but again, you or Ketan need to to keep on top of Radomir to ensure you are getting the results you need. I've messaged Rob and Radomir to emphasize the priority, but you need to take the lead in ensuring you have what you need to delivery fast searches that meet requirements. 

Moran

Sure Morgan . We are on top of it and trying to resolve it with help of Radomir as soon as possible. Hoping to get quicker response from Radomir.

Ok. Great. Thanks Harsh . We're almost there...

BTW: the updated views within Dispute & Dispute Documents look good on my end, but I'd like Naomi to confirm.

Thanks,

Morgan

Hi Morgan ,

The Performance issue of Dispute Document's dtSearch is resolved on staging.islg.

Please check and confirm.

Hi Harsh ,

The speed looks great. However, further to issues that were raised by Naomi last week and the video below, there is a problem when attempting to use certain filters in combination with each other:

Problems with DD filters (21-Mar-21).mp4 7.44 MB • Download

Thanks,

Morgan

Hi Morgan ,

This issue is resolved on staging.islg. Please check and confirm.

Looks good Harsh . Marking to-do complete.

Morgan