aer 1.6

aer 1.6 adds a browser interface to the development server. aer server now renders Lightning record pages, list views, home pages, and dashboards from your FlexiPages, layouts, and reports; runs Visualforce pages, Aura components, and screen flows; and serves Setup pages that include an Anonymous Apex console with a debugger. The release also distributes test runs and server requests across several machines, adds aer check and aer deduce, and models Nonprofit Cloud.

A Lightning frontend for the development server

/lightning renders the org’s apps, tabs, record pages, list views, home page, and dashboards. Pages are built from the FlexiPages, page layouts, compact layouts, and record types in your source, using the same assignment rules Salesforce applies for app, profile, record type, and form factor. An org that defines no applications gets the standard Sales, Service, Marketing CRM Classic, and Salesforce Chatter apps, and the app launcher lists the org’s apps and tabs. A CustomApplication with navType Console renders workspace tabs and subtabs, its utility bar, and console:history.

Every route requires a session. A browser without one is sent through the OAuth authorize flow.

Record pages

  • FlexiPage components. The highlights panel (force:highlightsPanel, record_flexipage:dynamicHighlights) renders where the page places it, with its key fields and header actions. The sales path, Chatter publisher and feed, Today’s Tasks and Today’s Events, activity field history, Potential Duplicates, and flexipage:blankSpace render. A card holding a custom LWC, Aura component, or screen flow is captioned with the kind and the component or flow name.
  • Components aer does not implement render as a placeholder that names the component and lists its attributes.
  • Record forms follow Dynamic Forms. When the assigned Lightning page places field sections, the create, edit, and clone forms are built from it, with its columns, tabs, visibility rules, and each field’s uiBehavior. Otherwise the page layout is used. Lookups offer + New <Object> to create the target record in a modal. A polymorphic lookup offers a target object picker, so an owner field can select a user or a queue. State and Country render as their code picklists when State and Country Picklists are enabled. A save error appears under the field it names.
  • Standard actions. Change Owner, Change Record Type, View Account Hierarchy and View Contact Hierarchy, Send Email, Sharing Hierarchy, Submit for Approval, and lead Convert run from the record page. Send Email sends the message as Messaging.sendEmail does: with --allow-email it is delivered over SMTP, and without it the message is logged and not sent. Sending also writes an EmailMessage record.
  • Quick actions. Global quick actions, the Chatter Post, File, and Link actions, flow actions, LightningWebComponent actions (screen and headless), and Visualforce actions run. A Visualforce action runs in a frame at the page’s /apex/ address with the action’s configured height.
  • Duplicate management. The Potential Duplicates card runs the record’s active duplicate rules, and View Duplicates opens a merge wizard that compares up to three records field by field and merges them through the same pipeline as the Apex merge statement. aer server now loads duplicate and matching rules from its source paths.
  • Record refresh events. When a component calls notifyRecordUpdateAvailable, fires a RefreshEvent, or fires force:refreshView, the other components on the page re-read the record and the related lists reload.

Render reports and page assignment

Record, home, and dashboard pages carry a render report in a footer bar. It names the page that rendered, counts the components by outcome, and gives the render time.

  • Page assignment. /lightning/r/{Object}/{Id}/pageassignment and /lightning/page/home/pageassignment list every assignment that could name a page, in the order they are consulted, and say whether each was used, skipped and why, or never reached. They also name where the highlights panel’s key fields and the action buttons come from.
  • Hidden items. A field, component, or tab whose visibility rule failed is kept in place, hidden, with the rule spelled out. A checkbox in the render report reveals all of them.
  • Other pages. The report lists every Lightning record page the org defines for the object, with the apps, profiles, record types, and form factors assigned to each. Choosing one reloads the record with that page.
  • Forms carry their own render report naming the page or layout the form was built from, the record type, and which fields rendered as inputs, as read-only text, or not at all.

Dashboards and reports

Dashboard components render tables (FlexTable), charts, funnels, and donuts from their metadata, and a component with useReportChart renders the source report’s chart. Each component links to its report. Dashboards now run their reports as the authenticated user, since the running user a SpecifiedUser dashboard names often does not exist locally. With --use-dashboard-running-user, they run as the user the metadata names.

The report engine adds the “Leads with converted lead information” report type, derived address line columns, boolean filter logic that combines base, joined-object, and bucket criteria, NOT in filter logic, and date groupings in the running user’s time zone. Totals appear under the columns they summarize. Reports in a .pkg or in a source directory loaded with @ns are merged with the package namespace applied, and the Reports and Dashboards tabs show a nested folder’s full path.

Visualforce

/apex/{PageName} renders a Visualforce page and /dev/visualforce lists the org’s pages. Pages run their controllers and extensions, and submitting a form runs the action its command button names.

  • Tags. apex:form, apex:inputField, apex:inputText, apex:inputTextarea, apex:outputField, apex:outputText, apex:outputLink, apex:outputLabel, apex:outputPanel, apex:image, apex:slds, apex:pageBlock and its section, item, and button tags, apex:panelGrid, apex:panelGroup, apex:sectionHeader, apex:include, apex:actionFunction, apex:actionStatus, apex:pageMessages, and custom components render. An output field shows a picklist value by its label and a date or number in the running user’s locale.
  • Expressions. Bindings may name a field dynamically (record[fieldName]). $Resource, $Label, URLFOR, IF, AND, OR, and NOT are evaluated, and merge fields are escaped.
  • Standard controller actions. Save, quicksave, cancel, edit, delete, and view run on the standard controller when the page’s controller and extensions do not define them.
  • PDFs. A page with renderAs="pdf", PageReference.getContent(), and getContentAsPDF() produce a PDF through ufo, a separate program that implements the Flying Saucer renderer Salesforce uses. aer finds it through AER_UFO_PATH, beside the aer executable, or on PATH.

Aura components

Aura components run in the browser: markup, controller, helper, and renderer, with two-way attribute binding, aura:if, aura:iteration, inheritance, component and application events, aura:method, and $A.createComponent. The lightning: and ui: base components render, including the record forms, datatable, tree, tabs, and force:recordData. An Aura component is served wherever Salesforce serves one: a FlexiPage, an Aura tab, the utility bar, a quick action, an action override, /lightning/cmp/c__Name, and /c/Name.app.

Flows

  • Screen flows. /flow/{FlowApiName} runs a screen flow and /dev/flows lists the org’s flows. The toggle, address, message, and lookup screen components render, the values an embedded LWC sends in FlowAttributeChangeEvents are stored in the flow’s variables, and a screen evaluates display text, visibility rules, and defaults against the components’ current values.
  • Flow approval processes and orchestrations. A flow whose processType is ApprovalWorkflow or Orchestrator starts a run when a record save meets its entry criteria. The run executes its stages and steps, creates work items for approval and interactive steps, and records each stage and step. The approval standard actions (reviewApprovalWorkItem, recallApprovalSubmission, and the others) run from flows and from Invocable.Action. A record in an approval step with shouldLock is locked. /dev/workitems lists the session user’s open work items and completes them.
  • Inactive versions do not run. Only a flow’s active version runs. The Draft, Obsolete, and InvalidDraft versions a retrieve brings down are loaded as metadata. An inactive trigger does not run either.

Setup pages

/lightning/setup gains pages that give access to the server’s state and the Apex in your source.

  • Anonymous Apex with a debugger. The console runs a block and shows the compile error, the exception with its stack trace, or the debug log. With Debug checked, the block stops at its first statement and the page shows the source, the call stack, the variables, and the log as it is written, with Continue, Step Over, Step In, Step Out, breakpoints, and an Evaluate field. Batch, queueable, and future jobs the block enqueues run inside the debug session, so breakpoints in them are reached.
  • Apex Classes and Apex Triggers. Each class’s page shows its source. Run runs a test class or method, Debug opens the console on a test with its @TestSetup, and Execute opens the console on a call to a static method.
  • Apex Jobs lists async jobs with Pause and Resume for the async worker, Run for a queued job while the worker is paused, and Debug.
  • Bulk Data Load Jobs lists Bulk API 1.0 and 2.0 jobs and their batches, with the request and response of each batch.
  • Query editor, record counts, email templates, validation rules, platform events, Change Data Capture, and Event Manager have pages, and Setup Home lists the aer server options in effect with the flag that sets each.
  • Object Manager lists an object’s list views, triggers, and fields with a page for each, and labels Data Cloud object kinds.

Debugging from the command line

aer test --debug and aer exec --debug now debug in the browser. Run from a terminal, both start an aer server on the command’s sources, print its address, and open the Anonymous Apex console in the default browser, already signed in. aer test --debug opens the console on the one test class or method selected with -f and the other selection flags. If more than one is selected, it reports an error listing the selected methods. The commands no longer write .vscode/launch.json or settings.json, install a VS Code extension, or open VS Code. An editor that launches aer as its debug adapter still gets the Debug Adapter Protocol over stdin and stdout.

Running on several machines

  • aer test --cluster sends test classes to other machines. aer cluster agent joins a cluster of machines that share a key made with aer cluster keygen and passed as AER_CLUSTER_KEY. Agents are found through mDNS on the local network segment or through --cluster-join addresses. Each agent receives the program the starting machine loaded, so it does not parse or type check the source. Results, --json, --junit, and --coverage output are written by the starting machine, as in a local run. A class whose node fails runs on another node. Only the starting machine needs a license.
  • aer server --cluster, with a PostgreSQL --db, runs REST record and query requests, executeAnonymous, Apex REST, and SOAP calls on the cluster’s agents against the same database. Queued async Apex and Bulk API batches run on every node, each job once. A batch job’s records are split into BatchApexWorker jobs of up to 10,000 records, and the worker jobs of a batch that is not Database.Stateful run at the same time.
  • Concurrent runs on one machine divide its CPUs. Two aer test runs on a 28-CPU machine used to start 28 workers each. Runs now split the CPUs among themselves, and when a run ends the others use its CPUs within a second. With AER_HOST_SHARE=off, a run uses all of its workers regardless of other runs.

Command-line additions

  • aer check lists the dependencies a source tree is missing, by Metadata API type, and exits with status 2 when dependencies remain. With --package-xml FILE it also writes a package.xml for the missing components, and with --fetch-missing DIR it retrieves them from an org into DIR; it does neither by default. --references lists the files that reference each component. The errors aer test stops on end with a tip pointing at it.
  • aer deduce evaluates a Mangle (Datalog) program over facts about the Apex code and metadata in a source tree, such as the modifiers of classes and methods, the fields that SOQL, flows, and layouts read, and the API version of each class. aer deduce --help-examples lists example programs, and the server’s /dev/deduce page runs programs from the browser.
  • --path adds a source directory to aer test, aer server, and aer package create, so a directory every run needs can be set in .aerrc.
  • aer test --sandbox-post-copy <Class> runs a SandboxPostCopy class once before the tests, outside a test, so its DML commits.
  • aer test --user-name sets the default test user’s name, which is otherwise Admin User. The first word becomes the user’s FirstName and the rest its LastName; a single word sets only LastName.
  • aer test exits with code 2 when the source does not compile, so a CI job can tell a compile failure from failing tests, which still exit with 1.
  • --heap-limit sets the Apex heap limits. The defaults are now the Winter ‘27 values, 10 MB synchronous and 25 MB asynchronous; --heap-limit 6/12 sets the Summer ‘26 limits of 6 MB and 12 MB.
  • --watch deploys changed metadata and applies a rebuilt package through the metadata deployment pipeline, and the page header prompts a reload when a deployment completes.
  • aer cache info -v lists the entries a prune would remove and why.

Apex and SOQL

  • SET OPTIONS. Salesforce API 68.0 lets package code name a subscriber’s field that has the same API name as one of its own, through a SET OPTIONS clause with a Database.QueryOptions bind. aer accepts it in inline and dynamic SOQL.
  • FORMULA() in a WHERE clause, for classes at API 68.0 or later.
  • SOAP callouts outside tests. A class generated from WSDL now sends its request to the endpoint and binds the response, rather than requiring a WebServiceMock.
  • Platform cache rejects a reference to a partition that does not exist, with the platform’s messages.
  • Stricter compilation. new on a standard library type with no visible constructor, such as new Database.SaveResult(), is rejected, as is a Decimal argument for a Double parameter. Both compiled in aer and failed at deployment.
  • URLENCODE() in Visualforce email templates and Formula.builder().
  • Test.createSoqlStub providers answer queries against external objects and Data Cloud objects.

APIs

  • REST. The query resource returns large results in batches with nextRecordsUrl, and queryAll is available. Describe, record, and query error responses match Salesforce’s. A packaged @RestResource is served under its namespace (/services/apexrest/<namespace>/<urlMapping>). POST /process/approvals submits records for approval.
  • Metadata API. listMetadata, createMetadata, updateMetadata, and upsertMetadata are answered, and remote site settings and external credentials deploy. A deploy fails only for errors in the components it deploys, and marks other classes that stop compiling as invalid, as Salesforce does.
  • Tooling API. tooling/symbols reports Apex type metadata, and apexCompileResults reports the classes and triggers that do not compile.
  • Bulk API. Bulk API 1.0 supports PK chunking, serial jobs, and queryAll. Query results in both versions match Salesforce’s CSV format.
  • Analytics Download API. /analytics/download/report/<reportId>.png and /analytics/download/lightning-dashboard/<dashboardId>.png return report charts and dashboards as images.
  • Custom buttons. A URL button’s merge fields are evaluated as formulas for the requesting user, including $Api, $User, $Setup, $Label, and $CustomMetadata.

Packages

aer package create stores a source tree’s Lightning web components and Aura bundles, and aer package mock stores a stub for each managed component. A server registers a package’s components under the specifier subscriber code imports them by (<namespace>/<bundle>), and a subscriber component that extends a packaged one renders the packaged template.

Platform coverage

  • Nonprofit Cloud. The Fundraising, Grantmaking, Program Management, Volunteer Management, Group Membership, Outcome Management, and Record Rollup objects are defined. Saves enforce the platform’s validations and maintain the totals Salesforce maintains. The fundraising, gift entry, and record aggregation standard actions run, and the server serves the Nonprofit Cloud Connect REST API. aer enables Nonprofit Cloud when the source references one of its objects or fields or contains its metadata.
  • Case automation. Auto-response rules, escalation rules, and entitlement processes run on Case saves, with milestone targets computed in the case’s business hours.
  • Commerce. Order.TotalTaxAmount, Order.GrandTotalAmount, and OrderItem.TotalTaxAmount are computed from the tax lines, and ConnectApi.OrderSummaryCreation.createOrderSummary computes the amounts of the summary records it creates and copies the order’s createable fields onto the summary. OrderItem.TypeCode, Product2.ProductClass, and Account.IsBuyer are set by the platform, and product variation rules are enforced on Product2 and ProductAttribute saves. The ConnectApi.CommerceCart, ConnectApi.CommerceCatalog, and ConnectApi.OmnichannelInventoryService methods can be called.
  • Activities. Task and Event field history is recorded in ActivityFieldHistory.
  • Contacts and accounts. A contact’s direct AccountContactRelation is maintained through DML and fires its triggers.
  • Metadata loaded as records. Call centers, navigation menus, survey flows, service channels, skills, and presence statuses are stored as the records Salesforce creates for them. Contract, Industries, Apex, and Communities settings files change the behavior they control, and Apex.settings sets the asynchronous Apex limits OrgLimits reports.
  • Insert defaults. Default field values on insert match sfapex.
  • Fixes. The changelog lists 114 fixes and performance changes in this release, covering reports, REST and Bulk API responses, server concurrency, EntityDefinition and FieldDefinition queries, record-triggered flow errors, and server restart time. A restart over unchanged sources now restores the checked program from the cached workspace image; on one org that removed 34 seconds of a 42-second start. See the CHANGELOG for the full list.

Changes that can affect existing projects

  • Field Service objects require a feature. 55 objects a plain Enterprise Edition org does not have, including ServiceResource, ServiceTerritory, OperatingHours, and WorkType, are now added only by --feature FieldService, --feature Scheduler, or --feature HealthCloud. A static reference to one of them in your source enables FieldService; otherwise pass the flag.
  • Heap limits are 10 MB and 25 MB. Use --heap-limit 6/12 for an org that enforces the Summer ‘26 limits.
  • Compile errors exit with code 2 instead of 1.
  • --debug opens the browser and no longer edits .vscode files.
  • Stricter compilation and inactive metadata. aer now rejects new on a standard library type with no visible constructor and a Decimal argument to a Double parameter, and no longer runs inactive triggers or inactive flow versions. Tests that relied on any of these can change result.
  • Schema.getGlobalDescribe().get('Widget__c') returns null when the object is pkg__Widget__c, as in Salesforce.
  • BR() in a formula field returns <br>, the HTML line break Salesforce stores.

Upgrading

brew upgrade aer
# or
aer upgrade

If the Salesforce CLI plugin downloaded its own copy of aer, it checks for a newer release on a later run and offers to install it. The VS Code extension updates through the Marketplace.

See Development Server and Configuration for the documentation of these features.