Changes since Execute 21.1.295

Using the new automatic_release.config.sample plugin, you can configure Execute to automatically release an AFE for approval when the review process is complete.

1. Create a new System Review Position Rule called something like “Automatic Release for Approval” (the name doesn’t matter). Record the DOCUMENT_ID for this position (the GUID in the URL).
   1. Don’t include any people on this position. The system will automatically mark it as review complete once all other reviewers have finalized their review.
   2. Adjust the position rule to include it as the last reviewer on any AFEs you’d like the auto-release behavior for. This lets you fine-tune the behavior (maybe you want this on EVERY AFE, or maybe just your Abandonment AFEs).
2. Create a plugin from automatic_release.config.sample and update the positionRuleId to be the DOCUMENT_ID value obtained earlier.
3. Restart Execute

Now… When you save an AFE that is (a) routed (b) has only this single reviewer as incomplete… and it’s the special new “Automatic Release” reviewer, it’ll automatically complete the review and release the AFE for approval.

Since early times, Execute ensured that only a single user could edit a document (AFE, Well, Job, …) at a time. This was handy for some document types (such as AFEs) with a very strong workflow, but a bit cumbersome for heavily multi-person documents like Wells, Sites and Jobs.

So… we’ve changed things a bit.

Execute will now take shared locks for Wells, Sites, Jobs and all of your custom document types. This allows multiple users to be actively editing the same document and, upon save, their changes will be merged together. It means a whole lot less waiting for someone else to finish their work before you can do yours!

Note: If you are making changes where you think you would benefit from the old-style exclusive locks, you can find “Edit with Exclusive Lock” under the more menu.

This functionality gets really interesting when you include fields from related documents on custom tabs. Previously, for example, you could include read-only well-level fields on your Job for reference but now you can opt-in to allowing those well-level fields to be editable (from the Job) by adding EDIT_REFERENCED_DOC_FIELDS to your “Additional Configuration Flags” in settings.