Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Requirement Generation and Suggestions - Reggi

  • In this update, Reggi allows users to ask questions via the Law Library and ADs.

  • Users can click on the purple icon, and get a list of questions Reggi recommends them to ask. These include Reggi skills like requirement extraction and penalties for non-compliance.

  • The user can also trigger this from within a document as they’re going through one

  • The user can click on the Reggi icon next to the title and ask Reggi questions related to that document and its children. This helps Reggi limit the context of the question to a single document/ part of a document and provide better answers. 

Enhanced Accessibility and Query Handling - Reggi

In this update:

  • The Reggi button remains visible even when the right-side panel is open, ensuring continuous access to Reggi's features for a more streamlined user experience.

  • Users can now click on the Reggi icon during an ongoing query.

  • The user can now ask Reggi another question in the same window as the previous question to help them access the precious query as well. 

  • If the user asks follow up questions, Reggi will carry the context from the last question asked by the user.

Unique Group Codes for Groups

In this update, we have replaced the group icon with a three-letter shortcode for groups, while users now have a two-letter shortcode. Admin users now have the ability to customize the group codes within the administrator section.

Enhanced Alert Descriptions 

  • In this update, we are displaying alert descriptions in two lines for improved readability in the alerts list view.

Email Frequency and Timing Enhancements

  • Users will now receive weekly emails on weekends and monthly emails exclusively on the 28th of each month.

  • Emails for non-ASAP frequency will now be sent at a specific hour of the day, ideally at the beginning of the day to enhance user experience.

  • Users have the flexibility to configure the email delivery time. The default time is set at 1 PM UTC, ensuring a customizable and user-centric experience.

Routing rule - Rename

  • We have renamed one of the routing rules to ensure regulatory change alerts generated for Authoritative Documents are assigned to the document owners, enhancing precision in alert management.

User email preferences by Admin

  • We have launched a feature where admin users can view and manage individual team members' email subscriptions, ensuring that they receive information at the appropriate frequency.

Default Landing page in saved views

  • We have launched the ability for users to set up their default landing page in the alerts section. This is done via the actions menu in the saved view. However, if an admin pins a different view to the user, that view will supersede the user’s default page.

Alert routing rules - UI Revamp

  • We have launched a feature that allows users to easily view the source link under each agency in the dropdown, also when searching by the URL and editing the rules.

Control the visibility of Disabled Rules

  • We've introduced a "Show disabled Rules" toggle in the filter section to make the search results include only active rules. This toggle is accessible and clickable only when a search term is entered.

Requirements in My Work page

  • We have introduced a dedicated “Requirements” section on the “My Work” page for users to keep track of their requirements.

Bug Fixes: 

Requirements FRON-2062

In this latest version, we have implemented the following points in requirements:

  • Removed the Key clause icon.

  • Updated the text in the pop over to "detach Requirement from the paragraph."

  • Fixed an issue where creating requirements from a discrete search was not working.

  • Resolved the issue with pinning and unpinning saved views, as well as Admin pinning, not working as expected.

  • New requirements created for an Authoritative Document now properly appear in the Law Library next to the Authoritative Document.

  • The migration process for previously created key clauses to requirements has been addressed and completed.

  • Positioned Requirements on the side navigation menu at the top.

  • Fixed the issue where if a user attempted to add a requirement to a parent document with existing child requirements, the child requirements were not removed.

  • Resolved the problem with mentions (reviews and comments) not functioning correctly in the requirements.

Keyword Set Inconsistency FRON-2039

Fixed an issue where the Keyword set was displaying the agency name in one place and the agency ID in another place. Now, the rules consistently display the agency name to improve clarity.

  • No labels