Notes
- If you are using Execute’s out-of-the-box integration with Peloton-hosted WellView/SiteView, please note that previous versions of that integration will cease to function at the end of Feb 2024 and you must take additional steps to upgrade to the newest version and continue to use this integration beyond that date. #243175
Featuresī¸
-
Support was added for new Peloton 2.0 APIs for our integration with WellView/SiteView.
#peloton
#243175
This release includes support for Peloton’s new 2.0 APIs (affecting Peloton SaaS customers).
Peloton has announced their plans to deprecate their existing APIs (used by previous versions of Execute’s integration with Peloton SaaS) by the end of February.
Customers who wish to use/continue to use this integration must:
- Contact Peloton support and request written permission to enable this integration (cc’ing Execute Support). Peloton requires customers obtain written permission prior to integrating with third parties.
- Upgrade Execute to this version or later.
- Work with Execute Support to update their configuration to use the new integration.
Enhancements
- If you are a heavy user of document links, you can now create extended document links (see extended_document_link.config.sample). This allows you to show links for documents linked to other linked documents. And because that sentence left more questions than it answered, here is an example: A common setup is for a Pad Site to be linked to one or more Wells. A Well is linked to one or more Jobs. A Job is linked to an AFE. This feature allows you to say, “I’d like to see those AFEs that are linked to Jobs that are linked to the Wells on this pad as virtual document links on my Pad Site so that I can, among other things, make use of Execute’s formulas to give me a total AFE cost across all the Jobs on all the Wells on my Pad.” #admin #257218
- Replaced legacy components on the Job/RTx Discipline’s Configuration tab. #security #257588
- Administrators can now see the size of text fields from both the document’s field list and the “Field Info” browse report. Similarly, document reference fields now indicate which document type is referenced. Finally, calculated fields are also now marked as such, making it easier to identify which fields are calculated. #admin #257711
- Added new formula functions “DocumentLinkTextValueCombined” and “DocumentLinkChildrenTextValueCombined” to make it easier to quickly summarize field values from related documents, such as including a comma-separated list of Well UWIs on your Pad Site. #formula #257318
- We’ve added “Description” fields to store notes about workflow definitions and custom tabs to help administrators keep things nicely organized. #admin #257212
- Administrators using the browse screen to report on FIELD_INFO configuration will be pleased that we’ve added the “Editability Rule - Display Name” and “Visibility Rule - Display Name” fields to make it easier to figure out which rules are actually in use. #admin #257213
- If you find yourself selecting a lot of data using Execute’s Table Data Selectors, we’ve added “Select All” and “Select None” buttons to make life easier. While we were at it, we also added larger limits to the number of rows to show, and we’ve made Execute remember each user’s preferred number of rows. #system #ui #257214
- If you struggled to find the descriptions of available user privileges, you weren’t alone. We’ve renamed the “Administrator Privileges” to “Available Privileges” and added a link to this helpful list from the User Role configuration screen. By the way, you can also hold your mouse over a privilege while you are in the User Role configuration screen to see the description. #admin #253801
- Execute includes a cool feature where a user can request to be notified (by email) when another user moves their activities on a schedule. We’ve resolved a bug that prevented this notification from working if the user owned any undated activities. #opsched #255857
- Updated the Schedule View configuration documentation to reference “greater” and “less” than operators. #opsched #256670
- We’ve continued to clean-up the sample data selector plugin files. #plugins #256784
- Users reporting on Workflows and Workflow Task status will be happy that we’ve added columns for the root document type, root document display name, and workflow name. This makes this report much more useful! #workflow #reporting #257213
- If you have trouble finding columns in our detail-level reports, we have good news! We have adjusted the report builder’s “Available Columns” search to search on the full name of columns so that if you are searching for “partners” on an “AFE - Partners” report, you’ll actually see the partners columns as you’d expect. #admin #257213
Bugs
- Fixed an issue where the Configuration Migration tool wouldn’t correctly migrate Discipline tabs between environments. #admin #251884
- Resolved issue where updates to Custom Business Rule names (such as a custom field permission) wouldn’t immediately be visible elsewhere within Execute. #admin #253436
- Fixed up view definitions for legacy Val Nav capital database views. #integration #256835
- Fixed multiple issues dealing with inactivated fields in a Workflow Definition (such as fields showing with an empty name, and being unable to remove them from the task reset list of fields). #admin #256906
- Fixed date filtering issues (using the In Range operator) in the new-style grids throughout Execute. #ui #257773
- Resolved issue when creating helper views in Azure SQL warehouse where an existing global object could cause the creation/update of the helper view to fail. #integration #258148
- Resolved an issue that prevented creating a new SQL Server database when using SQL Server authentication. #system #259011
- If you are still waiting for your schedule to print, we have resolved an issue where the “Print” button on a Schedule would appear to be stuck and never actually print the schedule. Sorry! #opsched #257366
- Added the missing element in table_data_selection.config sample plugin file. #plugins #247786