Schema Changes
- Modified column type on DOCUMENT_VIEW.HANLDES_EXPRESSION from VARCHAR(4000) to VARCHAR(MAX) to allow storing larger rules.
Enhancements
- Continued enhancements to Integration Agent when copying data from Execute to an on-prem table. #integration #162700
- It is now possible to report on Document Links via. OData so that your dashboards can make sense of links between documents in Execute. #system #odata #164442
- Upgraded components on the drag-and-drop browse report builder screen to replace an out-of-date 3rd party components. #security #164469
- Upgraded jQuery library to the latest and greatest to resolve some potential security threats. #security #164814
- On system startup for a brand-new database, Execute will now generate a secure random password for the System Admin user and store it in initial_system_admin_password.txt in the service’s config folder. #security #176042
-
Added the ability to define additional System Links.
#system
#176280
Execute automatically manages System-level document links between…
- An AFE and the Job it was created from
- An AFE and the Project(s) it is linked to
- A Well and it’s Pad (Site)
- A Project and related Wells and Sites
- A Job and related Wells and Sites
If you have some other relationship between records (such as a “Well” drop-down field on an AFE), you can use the new plugins to automatically manage System-level document links based on that field.
This functionality is enabled with the following new plugin configuration files:
plugins_available/custom_auto_document_link_list.config.sampleplugins_available/custom_auto_document_link_single.config.sample
- Changed the suffix in email notifications to use the user-facing Environment Label (shows in the top-bar) instead of the Environment Name (used for keeping track of services in the Windows Services control panel). We typically recommend the Environment Label for production environments be empty which, with this change, means we can avoid confusion when an email like “Execute - Well Diego 7a Status Changed (Production)”… Did Diego 7a go into production?!!! If you do have email notifications enabled in your TEST environment and you do not have an Environment Label set (the orange badge in the top-left of your TEST environment), contact Execute support to get the environment label set so that TEST and PROD emails are able to be differentiated from each other. #system #178493
- In the previous update, we introduced the ability to reactivate part of the workflow. Unfortunately, when subworkflows were involved, this reactivation was “excessively thorough” and would inadvertently reactivate tasks that shouldn’t have been reactivated. With this update, we endeavor to make the reactivation process involving subworkflows “do the right thing”. #workflow #178952
-
Add a new FormatDate function to calculate fields which makes it easy to convert a date/time field to text in a specific time-zone and format.
#system
#178988
The new
FormatDatefunction enables you to convert a date field to text in a specified format (and time-zone).For example, this formula converts the START_DATE to the America/Edmonton time-zone and then formats it as a long format date/time field (i.e. 2022-12-23 11:30:00 PM).
FormatDate([START_DATE], "yyyy-MM-dd hh:mm:ss tt", "America/Edmonton")This formula converts the START_DATE to the UTC and then formats it as a date only (i.e. 2022-12-23).
FormatDate([START_DATE], "yyyy-MM-dd", "UTC")You can find documentation on date format strings here.
-
Sometimes you just want to spread the word… to an existing Execute user. We’ve added a new “notify specified user” block that can be used to notify a specific Execute user.
#system
#179961
The new “notify specific user” block is available when building Notifications and Reminders and allows you to pass in an existing Execute users name, Document ID, or other identifier. When the rule runs, we’ll automatically look up the user’s current email address.
- Added an option to supress the automatic creation of Wells when import Projects from Val Nav or Enersight (it will, however, continue to link to an existing well). #integration #175310
Bugs
- Resolved an issue where importing capital from Enersight wouldn’t always bring across $0 months. #budget #enersight #160690
- Improvements to the default column types for tables created by the Integration Agent. Specifically, text fields no longer default to VARCHAR(MAX). #integration #166048
- Fixed issue where disabling the “Capital WI Override” field would break the capital grids. #budget #171332
- Enabled configuration of the delimiter in the concatenate operator for Operational Scheduling views. #opsched #171493
- The links in Task notifications now correctly open the task completion form. #workflow #175308
- Fixed potential issue where Peloton integration might fail to authenticate when run on daylight savings boundary. #integration #175333
- Sometimes the view rule for a custom tab is simple and concise. Sometimes it isn’t. For those times when you have an absolutely monster rule controlling when a custom tab should be shown, we’ve extended the limits for the underlying database column from 4000 characters to a colossal 2GB! #system #175411
- Fixed issue where an admin could break a Custom Business Rule by dragging an invalid block into a loop block. #system #175678
- Fixed issue where reactivated task icon would not show for task assignee. #workflow #175679
- Added clarification warning to task completion rule configuration regarding rules that consist only of completion instruction blocks. #workflow #175758
- Resolved database migration issue for Postgres-based databases. #system #176146