Hi Harsh ,

Further to the video below, the bug described above appears to be affecting how documents get loaded within the Document View: https://app.investorstatelawguide.com/DocumentView?rt=Wk21nmb-fNY%3D&docid=%20vkB0rbPc4Q%3D:

image.png 105 KB • Download

Because this is affecting the ability of users to access documents on Subscriber, I'm escalating this task to Priority #1. So please resolve this as soon as possible.

Note that when the document is accessed by browsing to the document, it opens properly: https://app.investorstatelawguide.com/DocumentView?rt=Wk21nmb-fNY%3D&docid=yFwM4xnGWDM%3D

image.png 139 KB • Download

Harsh , does this issue have anything to do with the fact that we're only indexing the Disputes & Dispute Documents search weekly?

Bug in orderning Disputes and Dispute Documents (24-Apr-21).mp4 6.35 MB • Download

Thanks,

Morgan

Hi Morgan ,

The issue related to DtSearch indexing was generated last Sunday and after perform search the data is fetching from indexing. 

The Scenario for this issue is like admin team published the draft version by last week so within application we are getting new Document Id but for Contegra search data is fetching from DtSearch indexing which was created by last Sunday. 

Due to this reason after perform search the Document View is not producing result because it is fetching data from indexing which was created before draft document is published.

We also getting one more issue that if any user copy the document view link and admin user creating draft and published that document then new id will be generated and copy link will not work for user.

so we are working on this change to fetch the data by UIN wise rather the Id. 

We assume this change will be completed by end of tomorrow and will deploy on staging.islg.


The Second issue regarding Ordering after perform the search which we will discuss with Radomir once the document view change will be completed by tomorrow.

Hope this is fine.

OK. Understood, Harsh .

Makes sense. Let us know if you're unable to get this resolved tomorrow.

I've added Radomir to the thread so that he is looped into the issue and then you can discuss next steps with him.

Thanks,

Morgan

Hi Morgan ,

The Document View bug is resolved on staging.islg. For testing this task, you do following step

1) Open any Dispute Document's  Document View
2) Copy browser URL and saved in notepad
3) Create draft of that Published Document and then publish the draft.
4) Once you published the draft version. you can paste the document view URL on subscriber side.
5) The Document View data will be rendered.



Regarding, Ordering for Dispute Document after perform search, We are looking in to this and will communicate with Radomir .

Hi Harsh ,

Further to the video below, I ran a test on staging.islg where I compared the link to the document view for a recently published document: https://staging.investorstatelawguide.com/DocumentView?rt=Wk21nmb-fNY%3D&docid=Iyzsqtzc5NU%3D

image.png 160 KB • Download

to the link to the document view for the same document when accessed through a Dispute & Dispute Documents search: https://staging.investorstatelawguide.com/DocumentView?rt=Wk21nmb-fNY%3D&docid=e%20G%20ZvyadkQ%3D

image.png 96.5 KB • Download

and I'm still not getting connected to the recently published version as expected.

Problem with recently published documents in Dispute Documents (28-Apr-21).mp4 7.22 MB • Download

Thanks,

Morgan

Hi Morgan ,

This issue occurred due to we haven't generated Dtsearch indexing by every week for staging.islg. so the indexing was too old for staging.islg. Today, We have generated Dispute Document module indexing for staging.islg.

You can check now this again on staging.islg.

Ok. Looks good, Harsh . Let's get this element deployed to app.islg during the next deployment; however, we'll keep the to-do open until we've resolved the ordering issues.

Thanks,

Morgan

Hi Radomir ,

We need to take call for Dispute Document Ordering. Let us know your feasible time to take call on skype.

We are available between 11:00 AM to 6:00 PM IST.

Hi Harsh ,

We can talk on Thursday at 12:00 PM IST.

Please send me details about the issue before that. Your request payload, result, etc. so that we can be efficient.

Hi Radomir ,

We need a Dispute Document Result in ordering. It mean When we use our second call for Dispute Document. We need Dispute Document Results in following Order.

Default Ordering Option is  Following:
DisputeDocumentDate ReverseChronologicalDate (Newest->Oldest)

We are using this SQL View (SelectDisputeContegraSearch) to get Dispute Document Result while we click on any Dispute.

You can use ISLGRebuildStaging database on 10.68.138.11 Server.  For More details you can also view the Mogan's First Video in this post. so you can get an idea.

Following is the ordering Criteria.

1) FullCitation Name (A->Z)
2)FullCitation Name (Z->A)
3)DisputeDocumentDate Chronological (Oldest->Newest)
4)DisputeDocumentDate ReverseChronologicalDate (Newest->Oldest)
5) Most Refrence DisputeDocument Count.


We can discuss more on tomorrow's call.

Hi Radomir ,

My health is not well today. so we can take call by Friday 12:00 PM IST.

Please let me know if you are OK with this.

Hi Harsh , I had some things planned for tomorrow but let's see. If we don't make it tomorrow, we can talk on Monday.

Harsh please send me a sample request payload that you're using for getting dispute details.
I tested locally and, as far as I can tell, sorting of dispute details using fields SortField and SortOrder works.

Hi Radomir ,

We have resolved the ordering issue by our side so there is no need of call.

Morgan , Could you please check Dispute Document Ordering issue after search on staging.islg.

Looks good, Harsh . Marking to-do complete.

Please migrate to app.islg during the next deployment window.

Thanks,

Morgan