Notes
-
Upgraded Execute from .NET Core 3.1 to .NET 6
This update of Execute changes the version of the .NET Framework Execute uses from .NET Core 3.1 to .NET 6.0.
This should have no user-facing effect on Execute and, because Execute is compiled as a standalone application which includes the appropriate version of the .NET Framework, there is no need to make any changes to the packages deployed on the application server hosting Execute.
-
Automated Schema Migrations
Execute will now automatically update its database schema when launching the Execute service against any existing Execute 21 database.
- Because this is an upgrade in place it is imperative that a database backup be taken before upgrading Execute. A failure or interruption during the schema upgrade process may leave the database in an unusable state.
- The release notes for each version of Execute will now explicitly detail any schema changes included in that update.
- Schema updates are forward only. It is not possible to run an older verison of Execute against an upgraded database.
- Environments prior to Execute 21 will still need to use the DatabaseTool to upgrade to Execute 21.
- Environments on any version of Execute 21 will not need to use the DatabaseTool except for migrating Execute from one database platform to another.
Schema Changes
- Modifed DATABASE_VERSION table (we now track database versions differently)
- Added WELL_NUMBER column to WELL table (for automatically generated Well identifier)
- Added SITE_NUMBER column to SITE table (for automatically generated Site identifier)
- Added WELL_DOC field to AFE_WELL table (for referencing linked Well)
- Multiple new columns and records in FIELD_MAPPING (used internally to copy data from one document to another)
- Added SYSTEM_LINK field to DOCUMENT_LINK table to identify system managed document links
Featuresī¸
- Added support for ODBC in Data Selection, Data Synchronization and Table Replication (Integration Agent). This means that these types of integrations are no longer limited to either Oracle or SQL Server, but can now work against most data providers that have an ODBC driver (such as Snowflake, Excel, Access, …). #integration #157945
- Added the ability to integrate Execute directly with some OIDC providers (such as Azure AD). #security #164641
-
Added the ability to turn off “Device Pairing” completely. Useful for environments that wish to require all devices authenticate through federated AD/Okta.
#security
#164641
A new setting
Enable "Device Pairing"(default: True) was added to the settings screen to allow an administrator to prevent the pairing of additional devices using the “Device Pairing” feature under the user menu in the top-right of the screen.This setting is aimed at environments that which to ensure all devices directly authenticate using federated Okta/Azure.
- Addition of the “Reverse Table/Query Replicator” to the Integration Agent which allows raw query results to be copied from SaaS hosted Execute environments to on-prem databases. This allows for direct-to-database BI/reporting to continue to work unchanged when migrating from Execute on-prem to Execute SaaS. #saas #integration
Enhancements
- Technical improvements to Execute to allow it to be efficiently containerized using Docker. This will simplify and improve the management of Quorum hosted Execute environments. It does not affect on-prem Execute installations. #system #saas #151575
- Improvements to management of configuration files and plugins in Quorum-hosted Execute environments. This should vastly reduce turn around time for changes to plugins. #system #saas #154672
- When pushing a schedule to Enersight, capital is only pushed across for static activities (avoiding unnecessary errors). #enersight #opsched #156073
- Relaxed database type checking for data selection and data synchronization for numeric types. Avoids the need to coerce source data column definition into matching, exactly, what was in Execute. #integration #162694
- Modified the “New Field” dialog to be full width to make editing calculated field formulas more pleasant (i.e. nobody likes postage stamp sized formulas). #admin #164873
Bugs
- Resolved issue where the Operational Scheduling view editor would sometimes break (and remove) milestone configuration. #opsched #156813
- Fixed issue where User Reassign tool wouldn’t always close after completing the reassignment. #admin #161970
- Fixed issue where a user viewing a task via. the Group Task widget would be unable to take and complete the task. #workflow #165284
- Resolved issue that prevent integration with enVision via. the Integration Agent (for hosted Execute environments). #afe #saas #165296
- Fixed minor error where deleting an AFE wouldn’t automatically clean up document links to that AFE. #afe #165514