Skip to main content
We’re always trying to improve our platform for our customers. Here, you can get an inside look at what’s currently in beta at Elementum. Remember, this list is provided as a heads-up—not as an invitation to test or a promise of what capabilities may be included. Most customers will not see these features until general availability. For what’s available today, see the most recent release notes.

​
What to expect

Heads-up, not a commitment. The information below explains how we treat beta features and why delivery and availability can change.
  • Currently being tested. These features are in active development and testing. Behavior and scope may change.
  • No guaranteed delivery date. We do not commit to a specific release date for any feature listed here.
  • No guarantee of delivery. Priorities shift based on resources and customer needs. A feature in beta may be delayed, changed, or not released to General Availability.
  • Limited availability. Some features may be tested by select customers before being released to General Availability. Broader access is not guaranteed until a feature is generally available.
  • Labs badge. Experimental features available in the platform but still being validated are marked with an orange Labs badge in the Elementum UI. Treat these the same way—behavior, scope, and availability may change before General Availability.

​
Features in beta

This list is updated as new beta features become available to give you an idea of upcoming improvements likely to occur in Elementum. The colored badges indicate the area of Elementum where you will see the update.
​
Sort and Limit on Search Records Action

​
Sort and Limit on Search Records Action Automations

The Search Records automation action can now sort results by one or more fields in ascending or descending order and cap the number of records returned with a configurable limit between 1 and 500. Together, sorting and limits give automations finer control over which records they pull and in what order, so downstream steps only receive the records that matter.
​
"Is In" Filters for Automations

​
”Is In” Filters for Automations Automations

Automations can filter a Record Search with an “is in” operator, returning every record whose field value matches one of a list of values. An Execute Script action can output a list of text or numbers that feeds directly into the filter. The operator is available on Text, HTML, Number, and Decimal fields, so a script can generate values at runtime and pull the matching records in one filter without hardcoded values or chained conditions.
​
Browser Use Agent Improvements

​
Browser Use Agent Improvements Intelligence

Browser use agents can now accept input attachments—such as PDFs, spreadsheets, and images—and return output attachments like screenshots, downloaded PDFs, and confirmation numbers back to the calling action. Customers can also bring their own model to power the browser use agent, including Snowflake Cortex models.
Who can configure it: App Administrators.Where to find it: App → Intelligence → + Agent → Agent Type selection.Configuration steps:
  1. Within your app, click Intelligence in the left navigation menu.
  2. Click + Agent in the top right corner.
  3. In the Agent Type selection, choose Browser Use Agent.
    • Native Agent — Create a fully customizable agent with configurable data sources, tools, and skills. Best for complex workflows and specific business requirements.
    • Browser Use Agent — Create an agent that can interact with web browsers and applications. Pre-configured with browser automation capabilities—choose a model and provide instructions.
  4. Complete the remaining agent configuration and click Create Agent.
Behavior notes:
  • Input attachments allow you to feed documents (PDFs, spreadsheets, images) to the browser use agent so it can read and act on their contents.
  • Output attachments let the agent capture confirmation artifacts—such as screenshots, downloaded PDFs, and confirmation numbers—and return them back to the calling action.
  • Customers can bring any model to power the browser use agent, including Snowflake Cortex models, by selecting it during agent configuration.
​
Add Option from List View

​
Add Option from List View Workspace

Add a missing option to a dynamic picklist directly from your List view, without leaving the list, opening a separate form, or navigating to the underlying element. Users stay in their data-entry flow, and Elementum handles the setup so any new record automatically qualifies for the column it was created from.
Who can configure it: All Users with permission to create records in the element referenced by the dynamic picklist column.Where to find it: Any List view with a dynamic picklist column.Configuration steps:
  1. In the List view, click a dynamic picklist cell.
  2. Begin typing a new picklist option.
  3. Press Enter.
  4. Fill out the required fields in the Create modal to complete the record creation process.
Behavior notes:
  • The Create modal opens with the record name pre-filled from what you typed, so you only need to complete the remaining required fields.
  • For picklists with simple equals filters, the matching field is pre-filled and locked in the Create modal so the new record automatically satisfies the column’s criteria.
  • The new record is created in the element the dynamic picklist references, not the element backing the current List view.
  • Once the record is saved, it becomes a selectable option in every other dynamic picklist that references the same element.
​
Multiple Closed Statuses

​
Multiple Closed Statuses Apps

Admins can now tag more than one status option in a status dropdown as closed—for example Closed-Good, Closed-Bad, Canceled, and Complete—instead of being limited to a single closed status. Every status marked as closed shows the same closed indicator and is recognized as closed across reports, filters, dashboards, and automations.
Who can configure it: App Administrators.Where to find it: App → User Interface → Record Details Layout → Status field.Configuration steps:
  1. Open App → User Interface → Record Details Layout.
  2. Click the Status field to open the Edit Dropdown Field editor.
  3. In the Static Dropdown panel on the right, click the Pencil icon Edit icon next to a status value.
  4. Toggle on Mark as Closed to treat that value as a closed status.
  5. Repeat steps 3–4 for each additional status value that should be recognized as closed.
  6. Click Save.
Behavior notes:
  • Previously, only one option per Status dropdown could be marked as closed. This beta lets any number of values in the dropdown carry the closed indicator at the same time.
  • The same steps apply to any static Dropdown field where Treat this field as is set to Status, not only the system-required Status field.
​
Voice: Employee ID with OTP Authentication

​
Voice: Employee ID with OTP Authentication Org Settings

Voice agents now support a new phone authentication type where callers provide their employee ID, receive a one-time password by email, and speak or type the OTP to authenticate. Any employee can reach the agent from any phone without needing a pre-registered phone number.
​
Automation Slack DM

​
Automation Slack DM Automations

Automations can now send updates as direct messages to any user in Slack, in addition to posting in channels, so time-sensitive notifications and alerts reach people where they already work. These are one-way notifications—recipients cannot reply to the DM to reach an agent.
Who can configure it: App Administrators.Where to find it: App → Workflows & Processes → Automations.Configuration steps:
  1. Open your automation and add the Send Slack Message action after your trigger (for example, Record Updated).
  2. Add the users who can receive the Slack message.
  3. Add the Message content — Title and Contents. Both fields support {{value_references}} for pulling dynamic values from the trigger record.
  4. Toggle on Add Link Button and paste the destination URL below the toggle if you want the DM to include a jump-to link.
  5. Click Save.
Behavior notes:
  • When enabled, the Add Link Button renders as a clickable button in the Slack DM that opens the URL you specified.
  • The action targets specific users; use the existing channel-post action when the notification should be visible to everyone in a Slack channel instead.
​
cXML Webhook Trigger

​
cXML Webhook Trigger Automations

You can now create a cXML Webhook Integration in Company Settings with the credentials required for cXML invoice event types, then use it as a trigger in automations. The trigger supports the synchronous responses that cXML requests require.
​
Multi-Select Picklist Badges

​
Multi-Select Picklist Badges Record Details

Multi-select picklist fields on a record now show every selected value as its own badge with the option’s icon, so the full set is readable at a glance instead of only the first value with a “+N” counter. Long value lists stay compact by collapsing to about two lines, with an inline “Show more” / “Show less” control that reports the exact number of hidden values.
​
Voice: Organization Management

​
Voice: Organization Management Org Settings

A single management surface brings all voice telephony configuration—phone numbers, providers, SIP settings, and voice agent mappings—into one place. Administrators can see and manage every voice-enabled agent, gateway, and number across the organization from a unified view.
Who can configure it: Organization Administrators.Where to find it: Organization Settings → Voice.Configuration steps:
  1. Open Organization Settings → Voice.
  2. Use the tabs across the top of the page to switch between Phone Numbers, Phone Providers, and Voice Agents.
  3. Review your existing Elementum voice configuration on each tab:
    • Phone Providers — See your connected phone providers, whether a SIP domain is set up, and the SIP domain address.
    • Voice Agents — See the voice agents configured across your organization.
    • Phone Numbers — See the phone numbers configured across your organization.
  4. Click + Add Phone Provider or + Phone Number in the top-right corner of the related tab to configure new details.
Behavior notes:
  • This provides an organization-wide view into your Elementum voice configuration across all of your different apps and gateways.
​
Conditional Record View

​
Conditional Record View Apps

Record detail pages now render a dynamic layout that shows the fields, sections, and components defined for each record type, including rich content like attachments, tags, assignees, and rich text. Admins can add conditional visibility rules driven by other field values, stage, or user and group permissions so people see only the information relevant to the record in front of them.
Who can configure it: App Administrators.Where to find it: App → User Interface → Record Details Layout.Configuration steps:
  1. Open the Record Details Layout and switch to Dynamic Layout at the top of the page.
  2. Click the Import button in the top-right corner to import the field configuration from the static layout, then click Import and Replace.
  3. Continue editing the layout as desired by choosing to add or update components or fields.
  4. In the Edit popup for a field or component, click the Conditional Visibility tab.
  5. Edit the filters to choose when the field or component is visible to your users (for example, based on other field values, stage, or user and group permissions).
  6. Click Save when finished.
  7. Click Layout Inactive at the top of the page to make the dynamic layout the visible layout for your users.
Behavior notes:
  • The dynamic layout coexists with the static layout—you can keep building and previewing the dynamic layout while the static layout remains active, then activate the dynamic layout when you’re ready.
  • Conditional visibility rules are evaluated per user and per record, so the same record can show different fields and components depending on who is viewing it and the record’s current state.
​
Customizable Side Nav

​
Customizable Side Nav Navigation

Pin the Apps, Agents, Conversations, Views, Elements, Tables, and Tasks you reach for most to a dedicated section of the side nav, hide the items and sections you don’t use, and drag to reorder your pins. Search makes adding pins fast, and your layout persists across sessions, page navigation, and logins.
Who can configure it: All Users (each user personalizes their own side nav).Where to find it: The left navigation menu in Elementum.Configuration steps:Pin an object:
  1. Click the + icon in the left navigation menu.
  2. Select the type of object you’d like to pin (for example, Apps, Views, Agents, Chats, Elements, Tasks, or Tables).
  3. Choose the specific object from the list by searching or scrolling.
Rearrange or remove pinned items:
  1. Click the + icon, then click Manage.
  2. In the Pinned section, drag and drop a pin to move it, or click the Trash icon Trash icon to remove it from your main navigation.
Personalize Main nav and System nav sections:
  1. From the Manage nav panel, open the Main or System section.
  2. Use the checkboxes next to individual items to show or hide them, or use the section’s checkbox to toggle the entire section at once.
Behavior notes:
  • Your side nav layout persists across sessions, page navigation, and logins.
  • Hidden items remain accessible through search and direct links; they are only removed from the visible side nav.
​
SIP Trunking Provider

​
SIP Trunking Provider Org Settings

Bring your own telephony provider to Elementum by connecting SIP trunk-enabled phone providers to power voice agents.
Who can configure it: An Elementum representative configures the initial SIP Domain. Organization Administrators can then update the domain and create SIP Trunk phone numbers.Where to find it: Organization Settings → Voice → Phone Providers.Prerequisites:
  • An Elementum representative sets up the SIP Domain for your organization before you can manage it or create SIP Trunk phone numbers.
Configuration steps:Update the SIP Domain:
  1. Open Organization Settings → Voice → Phone Providers.
  2. In the SIP Domain section, review the configured domain.
  3. Click Edit to add additional IP addresses.
  4. Toggle HTTPS on if you want to use a secure connection.
  5. Click Save when finished.
Create a phone number using SIP Trunk:
  1. In your app, start setting up phone services.
  2. Select SIP Trunk as the provider.
  3. Complete the remaining phone number configuration.
Behavior notes:
  • Using your own SIP trunk lets you keep existing carrier contracts and phone numbers while routing calls through Elementum’s voice agent stack.
  • Per-call audio, transcripts, and telemetry still flow through Elementum for logging and agent memory.
  • Outbound caller ID and number porting are handled by your telephony provider, not by Elementum.

​
Stay in the loop