Changelog 6

May 3, 2022

What's New in Verve

Hi Steve,

Our latest release brings significant improvements in usability and stability. Our team has been working behind the scenes to ensure smooth operations for all our customers.

  • We listened to feedback about on-screen data density and focus, and re-formatted how we present key information in the System Editor. Most metadata is now in a "sidecar", with the primary document body and title information visible in the main item component.
  • We've expanded the number of Activity Log entries created on user action. Behind the scenes, this supports a more robust branch/merge capability; from the web interface, this offers more granularity when viewing the log of actions on any given item.
  • A "lock item" feature helps teams mark design components as stable, and otherwise prevents editing.
  • Our help documentation has been moved to a dedicated site and expanded. Find it here: https://help.prewittridge.com/.

A significant amount of work is going in to two more features not yet included in this release: Grid View and Pipelines. Grid View expands on data density even further by presenting requirements, verification events, and corresponding upstream and downstream items in a data-dense and configurable grid layout. Pipelines enable teams to upload analysis scripts into Verve and trigger automatic re-calculations of derived requirements based on atomic changes and other actions. If you're interested in a hands-on preview of these features, please send me a note and we'd love to get your feedback.

 

Thank you again for your ongoing support, and please let me know directly if there's anything we can do to help you in your effort of building great products.

-Steve

Updated: System Editor UI Refresh

new system editor

We refreshed our System Editor's UI! Easily traverse your projects, see and modify key pieces of metadata with the newly consolidated "Item Sidecar".

New: Lock Item

lock item

Lock Item now protects key requirements and components from being changed when a team decides they're "done." This has been available via API for some time now, so we are now exposing it for easy toggle and indication for day-to-day customers.

Updated: Python API

python

If you haven't seen our Python library in awhile, it's time to check it out again! Notably we've made Verification Statuses much easier to work with. I've put together an example Jupyter notebook detailing how your team can retrieve a source requirement, process its atomics, and change the verification status of a downstream item thus automating a test workflow; please reach out to me directly and I'll send it over.

May 3 Release Notes

See below for a detailed list of changes in this release. It's since been rolled out to our existing cloud customers, and has been made available in our delivery repo for our self-hosted customers.

Most of these updates not otherwise detailed in the above discussion were either technical debt resolution or incremental work supporting our v2 frontend.

Core Product

  • Added an "executes" relationship type.
  • Updated current table view to be sortable.
  • Lock Item toggle and flag now accessible via frontend.
  • Item Titles and Descriptions no longer reject empty text.

Bugfixes and Technical Debt

  • Updated how multi-parent items are represented in API response.
  • File uploads migrated to new S3 paradigm.
  • Fixed bug where branch dropdown list would change if a user added a new branch.
  • SHA256 now recorded on file upload.
  • Item Tree no longer disappears when switching groups.
  • Fixed several CVEs discovered during automated testing.
  • Removed a significant number of deprecated API endpoints
  • Moved Verification Status enumeration to database model and out of atomics.