TOLOGIX - ISLG App Rebuild

Unable to suppress fields from appearing on Subscriber site

Assigned to
Martin Laporte, CTO at Tologix Martin L.
Notes
There may be an oversight in the requirements for meta field management. It was assumed that when fields were suppressed from displaying within the front end filters within meta field management, that the field would not display within the Subscriber site (e.g., would no appear within the Dispute details):

However, as outline the video below, that is not the case, the fields are showing within the Subscriber site:


I see two possible solutions to this problem:
  • Create an additional Yes/No toggle field within meta field management (e.g., Show on subscriber site) that allows admin users to control whether a field is suppressed from displaying in the subscriber site.
    • In addition, automatically apply the following to all existing fields:
      • Yes = to all fields that have Show as Front-end Filter enabled
      • No = to fields that have Show as Front-end Filter disabled
  • Expand the current requirements so that when Show as Front-end Filter is disabled in both "Full Text Search" and "Dispute & Dispute Documents Library", it also suppresses the field from displaying in the subscriber site.
Melissa Cowell, General Manager at Industrial Melissa and Naomi Joanis, UX Team Lead at Industrial Naomi , please share your thoughts on the appropriate solution, and we will implement accordingly.
 
Thanks,

Morgan 

Comments & Events

Naomi Joanis, UX Team Lead at Industrial
Hi Morgan Maguire, CEO Morgan

I would just like to confirm there wouldn't be a case where you would want to display metafields in a document view for example but not allow users to filter by it in the FTS or document library feature?

Thanks,

Naomi
Morgan Maguire, CEO
Hi Naomi Joanis, UX Team Lead at Industrial Naomi ​,

Yes, that may be the case, so perhaps the first option is needed then?

Morgan
Morgan Maguire, CEO
Looks good, Naomi Joanis, UX Team Lead at Industrial Naomi .

Harsh Parikh, Tech Lead at DevIT Harsh and Ketan Sondarva, Technical Project Manager at DevIT Ketan , please note that I have put this user story into the Backlog, because we'll need to get this implemented before launch. There are quite few fields within legal analytics that need to be suppressed from subscribers before we launch. Please confirm how we can get this implemented into the development pipeline.

Thanks,

Morgan
Harsh Parikh, Tech Lead at DevIT
Hi Morgan Maguire, CEO Morgan ,

It is new requirement and It is taking time to integrate this thing in Subscriber Side as well as Admin Side. We also need to create new field in Meta field table and apply that logic in all tool on Subscriber Side.
Morgan Maguire, CEO
Hi Harsh Parikh, Tech Lead at DevIT Harsh ,

Understood. As discussed with Ketan Sondarva, Technical Project Manager at DevIT Ketan this morning, it's ok if we don't complete this to-do for next Monday, but let's ensure this gets completed by the end of next week, so that we can make the appropriate adjustments to the admin site and complete all the testing required on the subscriber site before we launch.

Also, as I discussed with Ketan Sondarva, Technical Project Manager at DevIT Ketan , let's be sure that we're doing a full suite of integration/regression testing before we deploy this change. Last thing we need is for this to cause regression issues across the system a week before we launch.

Thanks,

Morgan
Morgan Maguire, CEO
Further to our discussions this week, I am moving this to-do to ISLG Team Feedback - post-launch (high priority) - TOLOGIX - ISLG App Rebuild and we will resolve the issue of suppressing managed meta fields by manually suppressing the necessary fields on the Subscriber site. Details on what fields need to be suppressed will be posted in a separate to-do.

Thanks,

Morgan
Paul Moon
No longer an issue.
Paul Moon
Paul Moon completed this to-do.