It’s February, the shortest month of the year, which makes it apt to focus on a few newer, time-saving features in RubyLaw that help you get more done in less time.
As such, this month’s Spotlight on RubyLaw looks at an improved edition of Content Reports, RubyLaw Integrity, and a souped-up Content Drafts feature that includes Quick-Merge.
RubyLaw has long offered users the ability to export data and pre-formatted content reports from RubyLaw in Excel. This functionality allows teams and individuals to easily access, analyze, process, and update content at scale.
Recent enhancements to Content Reports now enable users to generate reports directly from the Lister page (within the corresponding Structured Data section) of RubyLaw. This functionality also extends to Lookups, which can be fully exported from both the centralized Content Reports and individual Lister pages.
To the theme of this Spotlight, this improvement is one way to pull and process reports faster, allowing users to save time navigating for content and firm data and spend more analyzing it.
RubyLaw Integrity saves users countless hours each week—not to mention fewer headaches—by finding and displaying website spelling errors, broken links, and forbidden terms right in the RubyLaw editing interface.
Now, RubyLaw Integrity includes two major enhancements. First, it can scan and report on broken links within Rich Text Editor (RTE) content fields throughout RubyLaw. Second, it can also flag spelling errors, underlining them in content fields when found.
The combination of improved functionality and visual cues allow legal marketers to spot and fix content issues faster—and more effectively—than ever.
RubyLaw supports a range of workflows and approval processes, each tailored to the different law firm cultures and operational approaches that inspire its continued evolution. The same user feedback loops that influenced past developments of the platform, have now led the implementation of a new feature.
The latest version of RubyLaw now gives users the option to merge a content draft without requiring a comment to be supplied. This is implemented as a simple toggle option under the Save button, giving users the choice to communicate the specifics of a recent update to fellow users (or not), when merging each content draft. We call this feature Quick-Merge.