Changes in Execute 21.1.273

Featuresī¸

  • Added a new streamlined Document Fetch API as part of Execute’s Advanced Data Export offering. This API makes it easier to slurp bulk data out of Execute to populate an internal data warehouse, or similar. #integration #288479

    Execute’s new Document Fetch APIs provide a streamlined way to bulk extract documents from Execute.

    • A single streamlined API call vs. the Login > Run Report > Logout call for the current APIs.
    • Returns ALL data for request documents in a nice friendly machine readable JSON form.
    • Supports including calculated field values in the returned data (popular request from User Voice).
    • Easily filtering to return only documents modified since a provided date (makes it much easier to keep a remove warehouse up-to-date).

    Note: These APIs require the Execute Advanced Data Export (OData) module license.

    More information can be found in our New Postman-based API documentation.

Enhancements

  • The new Show Field Usage function takes a while to work on very large record types. We’ve added a loading bar so that you won’t be left wondering, “Is it working?” #admin #288972
  • Updated HTTP caching headers to improve page load performance across the system. #system #performance #288982

Bugs

  • Improved the clarity of error messages raised when a Document Link Summary view is misconfigured to make finding and fixing the mistake easier. #system #253151
  • Fixed an annoying issue where switching schedule views would sometimes jump to a different view a few seconds later. #opsched #288470
  • Fixes to the export of AFEs to Peloton-hosted SiteView (2.1 APIs). #integration #peloton #291362
  • We resolved an issue where we were inadvertently creating automated document links to Project Snapshots. #system #budget #291678
Ready to update?
  • For Quorum-hosted Aucerna Execute environments, email an upgrade request to Execute Support.
  • For on-prem instances of Execute:
    • Always ensure you have a recent backup of your Execute database before updating.
    • Download the installer from the Client Portal.