Changes in Execute 21.1.242

Schema Changes

  • New tables for the newly added Schedule Activity Type configuraton (SCH_ACTIVITY_TYPE*)
  • New fields added to RTX/RTX_H to support Job Scheduling (DURATION, JOB_START, JOB_END, JOB_IS_SCHEDULED)
  • Note that the fields SCHED_START and SCHED_END have been supersceded by JOB_START and JOB_END and will be removed in an upcoming update.

Featuresī¸

  • Improvements to standalone use of Execute’s Operational Scheduling when using the Jobs module. #opsched #well delivery #160969

    In this update, we’ve added a new Job Scheduling mode (inspired by Generwell’s similarly named module) to Execute’s Operational Schedule. This new mode simplifies the process of adding jobs (from the Jobs module) to a schedule, adjusting their timing, and feeding that updated timing back into the Job workflow.

    • Each schedule view can define a report which provides a list of candidate jobs (the job hopper) that can be added to that view.
    • A scheduler can select one or more job(s) from that report and add them to a resource on the schedule.
    • New Schedule Activity Relationships configuration allows you to define the relationships between activities (Completion happens after Drilling, etc.), so that appropriate dependencies will automatically be created when scheduling Jobs.
    • Updated timing from the master schedule will automatically feed back to the new “Job Start”, “Job End” and “Duration” fields.

    Note: Execute previously included “Sched Start” and “Sched End” fields which were barely used (only set when creating a Job from the schedule). The new Job Start and Job End fields replace these and the old fields will be removed in a future update.

  • When copying a document in Execute, there is now a checkbox to copy the document links. #ui #223503

Enhancements

  • Removed unused WSDL and XML examples from API Documentation. JSON is our path forward. #integration #235124
  • Added the attachment date to the dropdown on Attachment Fields to help you pick the right attachment. (This idea was raised as part of our last CAB meeting). #ui #236143

Bugs

  • Fixed a spelling mistake in the pop-up for Document Validation Rules. Two L’s in “Following”. Oops! #ui #228072
  • Resolved an issue where calculated fields returning very long text values would incorrectly show a length warning. #ui #237901
  • Fixes and improvements to the Snowflake / SQL Warehouse beta functionality. Deleted data is now visible in the helper views/tables. Introduced “Materialized Views” in SQL Server databases for performance purposes. #integration #240107
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.