The Location of Relevant Document(s) of second and subsequent entries are replaced with that of the first entry. To give you an example, below is what the intended entry looks like.
However, once the entries are saved and I come back to Legal Analytics for AF/0007, the second “Not Decided” entry’s Location in Relevant Document(s) 3.3.4.3 is replaced with the those of the first entry 3.2.4.11, 3.4.4.4, 3.5.4.11 as highlighted below
It seems like when the same Relevant Document is selected (e.g., AF/0007/01) for two different outcomes (e.g., Rejected and Not Decided), the Location in Relevant Document of additional entries (e.g., 3.4.3.3) seems to be replaced by the Location in Relevant Document of the first entry (e.g., 3.2.4.11, 3.4.4.4, 3.5.4.11). The problem seems to occur throughout the Legal Analytics fields, not just the Jurisdiction section.
Thanks,
Paul
Notified 2 people
Harsh Parikh,Tech Lead
Hi
Morgan
and
Paul
,
The above issue is resolved on both rebuild.ilsg and rebuilddemo.islg.
Please check and confirm.
Please clear cache and refresh the page one or two time if you are not able to see any change.
Notified 2 people
Paul Moon
Hi
Harsh
:
I checked it on rebuild.islg, and the issue is resolved.
The Location of Relevant Document(s) of second and subsequent entries are replaced with that of the first entry. To give you an example, below is what the intended entry looks like.
It seems like when the same Relevant Document is selected (e.g., AF/0007/01) for two different outcomes (e.g., Rejected and Not Decided), the Location in Relevant Document of additional entries (e.g., 3.4.3.3) seems to be replaced by the Location in Relevant Document of the first entry (e.g., 3.2.4.11, 3.4.4.4, 3.5.4.11). The problem seems to occur throughout the Legal Analytics fields, not just the Jurisdiction section.
Thanks,
Paul
The above issue is resolved on both rebuild.ilsg and rebuilddemo.islg.
Please check and confirm.
Please clear cache and refresh the page one or two time if you are not able to see any change.
I checked it on rebuild.islg, and the issue is resolved.
Thank you,
Paul