Changes since Execute 21.1.295

Enhancements

  • We’ve changed the default behaviour when viewing attachments to open in the browser/default application instead of downloading them. This is much more consistent with other web-based applications. Users who want to download the file can right-click and “Save As”. #ui 21.1.296 #338037
  • The Integration Agent now supports connections to Snowflake (for Document Sync purposes). #integration agent #integration 21.1.296 #339388
  • Execute’s unique value validation rule now works with UWI-type fields. #system #afe 21.1.296 #338517
  • Upgraded Snowflake library to the latest and greatest. #system #security #integration 21.1.296 #338212
  • If you’d like to see your primary document types (those in the top toolbar) in a specific order and have been annoyed at how prefixing them with “1.”, “2.”, … made everything else in the application look a bit wonky… good news. We’ve added a new configuration setting that allows you to set the sort order! #system 21.1.296 #338259
  • We’ve lowered the batch size limit when exporting Execute data to Snowflake / Azure SQL to help eliminate issues with large documents like Schedules causing excessively large batches. #integration 21.1.296 #337950
  • We’ve relaxed the rules a bit for account matching between Execute and ODW. So if your Execute account numbers are formatted like “100 / 234”, but you have “100 .-=-. 234” in ODW, you’ll be pleased to know that the integration will work just fine. #integration #wellez 21.1.296 #337090
  • Improved error logging around login with OIDC to make troubleshooting easier. #system 21.1.296 #337130
  • Inactivated the old Parent RTD field. If you’ve gone to the effort of migrating from the old RTD to the shiny new Jobs (RTx), you don’t want to see that smelly old Parent RTD field anymore! #well delivery 21.1.296 #336929
  • Removed legacy actuals/field cost helper views from new databases. Existing databases are unchanged. #system 21.1.296 #333389
  • Ever want to clear the date from a project activity? Now you can! #budget 21.1.296 #334073
  • We’ve improved the Due for Forecast filter, ensuring that project owners can more reliably see projects that need their attention. #budget 21.1.296 #335791
  • We’ve improved the Min/Max formula functions to work with date-type fields, and to have more sensible handling of null (empty) values. Note that with the new changes “Min(1,null,2)” will now return “1” whereas it used to treat the null as a zero and would have returned “0”. If you need this old behaviour, you can wrap the values with the coalesce function “Min(1, coalesce(null,0), 2)”. #formula 21.1.296 #338039

Bugs

  • Resolved an issue where adding a List Filter could sometimes freeze the UI. #system #admin 21.1.296 #336708
  • Resolved an issue where the Bulk Export plugin could cause Execute to fail to start if the destination folder didn’t exist. #plugins 21.1.296 #338041
  • Resolved issue where Custom Business rules failed to show custom fields on the AFE’s well table. #afe 21.1.296 #338359
  • Resolved an issue preventing AFEs from being exported to WellEz. #afe #wellez 21.1.296 #339020
  • Resolved an issue where the database upgrade would fail in environments without an AFE_TYPE. #afe #system 21.1.296 #339024
  • For those of you rocking the commas in your report names, you’ll be glad to know that the bug preventing you from exporting those reports to Excel is now resolved. #ui 21.1.296 #296011
  • We’ve resolved an issue where workflow task fields would sometimes jump mysteriously for workflows loaded with the historical loader. #workflow 21.1.296 #334868
  • We’ve resolved an issue where we created new versions in the ACTUALS_DOC_V table much more often than we should have and, at the same time, ensured that AFE actuals and field costs will now move across into your external data warehouse. #system #afe 21.1.296 #335140
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.