DRTE v5.138 (GA)
Published on October 28, 2026 DRTE
Release notes for DRTE 5.138: find and fix missing allow-list objects right from the Document Template page, with the new DRTE Access Checker.
| RELEASE NOTES DRTE Version 5.138 New: DRTE Access Checker |
The DRTE Access Checker panel on the Document Template record page.
Highlights
| What it does Admins can now see which objects a Document Template queries and whether each one is on the allow-list, all from the template record page. They can also whitelist a missing object from the same screen. |
| The problem it solves Before this release, an object missing from DRTE Allowed Object made its section fail to display, with no explanation. |
What's New
| Feature | Details |
| DRTE Access Checker panel | A new Lightning component for the Document Template record page. It reads the SOQL query from every Document Section on the template. |
| Unique object list | Each object appears once per template, even if several sections query it. A "Used In" column names the sections that use it. |
| Subquery support | Objects in subqueries, including child relationship names such as Contacts, are resolved to their real object. |
| Allowed / Not allowed status | Each object is checked against DRTE Allowed Object records. Missing objects are listed first. |
| One-click Add | The Add button creates the DRTE Allowed Object record for a missing object, so admins no longer have to go to Custom Metadata Types in Setup. |
| Summary line | For example, "5 unique objects, 2 missing". |
Benefits
| ✓ Missing allow-list entries are found while the template is being built, not when a section fails to render. ✓ Fewer setup steps and fewer support cases about sections that don't display. ✓ The allow-list is still a deliberate admin action. Nothing is added automatically. |
How to Use
- Open a Document Template record.
- Review the DRTE Access Checker panel.
- Click Add next to any object marked Not allowed.
- Wait a few seconds for the deployment to finish. The status then changes to Allowed.
Upgrade Steps
- Install version 5.138.
- Add the DRTE Access Checker component to the Document Template Lightning record page in Lightning App Builder.
- Grant deploy permissions to admins who should be able to add objects: Modify Metadata Through Metadata API Functions, plus Customize Application if required. If you re-enable the custom permission check in
addObject, also assignDRTE_Manage_Allowed_Objects.
Important Notes
| Adding an object deploys custom metadata, so it can take a few seconds to show as Allowed. |
| Added objects exist only in the org where they were added. In a sandbox, move them to other orgs through your normal release process. |
Objects are matched on the Object API Name value, including the namespace if there is one, for example <namespace>__ObjectName__c. |
| The user needs permission to deploy metadata to use Add. See the upgrade steps. |
Known Limitations
Objects are detected from the FROM clauses of each query, including subqueries. Objects reached only through parent relationship paths (such as Owner.Name) are not checked separately. |
| Queries built dynamically at runtime may not be fully detected. |
Knowledge Article Number: KA-00487