Changes since Execute 21.1.325

Group Partner Approvals let you ballot partners once for a set of related AFEs, such as the AFEs for several wells on the same pad. Group Partner Approvals require a configured Electronic Balloting connection.

Privilege: Users need the Manage Group Partner Approvals privilege to create groups, add or remove component AFEs, update the group’s estimate, and apply partner statuses. Other users can view the Group Partner Approval tab but can’t change it.

Creating a group: On an operated AFE, select More > Group Partner Approval: Create Group. The AFE becomes the group’s parent AFE and gets a Group Partner Approval tab where you add the component AFEs. A component AFE can only belong to one group. To turn the parent back into a normal AFE, select More > Group Partner Approval: Remove Group.

Parent and component AFEs show a banner identifying them as part of a group, and component AFEs link back to their parent. Send to Partners is only available on the parent AFE, since its approval controls the whole group.

Finding AFEs to group: An administrator can list one or more AFE reports under Tools > Configuration > Settings > Group Partner Approval Reports (report IDs separated by semicolons). Those reports then drive a search tool for choosing the AFEs that make up a new group.

Building the group estimate: The Update Parent AFE Estimates action sums the estimates from all component AFEs into the parent, calculating net amounts with the parent AFE’s working interest. All component AFEs must be operated and not closed. You can also apply the parent AFE’s partner list to all of its components.

Sending the ballot: When you send to partners from a parent AFE, the Send to Partners modal has a Component AFE Forms section for choosing which forms to generate for each component AFE. Those forms, along with the attachments from each component AFE, are included with the ballot. Their file names are prefixed with the component’s AFE number so you can tell them apart.

Applying responses: Once the parent AFE is Fully Approved or Partner Rejected, the Apply Partner Status to Component AFEs action copies the partners’ responses and mail ballot details to the latest version of each component AFE. Then the status of each component AFE is re-evaluated. Locked AFEs are skipped and reported, and every AFE that’s updated gets an audit log entry.

Alberta, British Columbia and Manitoba stop changing to standard time in November 2026. Execute now follows the new rules, so dates and times for users in those provinces stay on daylight time and don’t fall back an hour on November 1.

Updating users’ time zones: Search or filter the user list to show only the affected users, then use the “Bulk Update” menu item on the “Timezone” column to set the new value.

Why check profiles: Users’ time zones are derived from their web browser settings, but browsers in Alberta may sometimes report America/Denver as their time zone, depending on Windows settings and browser versions. This used to be fine because the rules were the same in both places. Now, users in Alberta with an America/Denver setting will see incorrect local times.

Windows servers: the new Alberta, British Columbia and Manitoba time zones come with the October 2026 Windows update. Execute v332 works the same on servers without it, so you don’t need to install the update for this change.

To track the Creator and Owner names on a custom document, create CREATOR and OWNER list fields on the document in question (Tools > Configuration > document name > configure rules & fields). These fields need to use User as the “Existing Doc Type”.

To enable this functionality, update the “Populate CREATOR and OWNER” setting to “Yes” (Tools > Configuration > Settings).

Now when creating new list values for this field, it will automatically populate the Creator and Owner fields with the name of the user who is creating the list item. You can update the Creator and Owner fields to other user names, as needed.