February 2026 Release: Omnitable Features & Enhancements

February 2026 (2026.02 GA Release - Package Version 9.41)

Omnitable Named Views: Entering Decimal Values in Number and Currency Filter

  • Feature: Omnitable

  • Level of Configuration: None

Up to this release the number and currency input component used in Omnitable Named Views condition popover did not support entering decimal values. Now, decimal numbers are supported in Omnitable Named View filtering for Number, Percent, and Currency field types.

How this works:

  • Omnitable now displays the decimal number to the field's configured decimal places

  • Named View filtering restricts the input number to the field's configured decimal places

  • Named View filtering condition list now shows the number to the field's configured decimal places

  • Named View query will now query a range when querying on decimal fields. The range queried depends on the configured decimal places for a field. The range will encompass all numbers that would have rounded to the queried number, given the configured number of decimal places for that field. For example:

    • When searching for 123.45 on a two decimal place field, the query will search 123.445 - 124.455

    • When searching for 123 on a two decimal place field, the query will search 122.995 - 123.005

    • When searching for 123 on a zero decimal place field, the query will search for 122.5 - 123.5

 

Allow "Reject/Unreject" Action in Omnitable for Candidates in Closing Report

  • Feature: Omnitable

  • Level of Configuration: Low

In this release we have enabled the Reject/Unreject action in Omnitable for candidates in the Closing Report stage, aligning its functionality with ATSv2.

Configuration

The same setting is used to enable rejection for Candidates in the Closing Report stage in both ATSv2 and Omnitable: Setup> Custom Settings> ATS Configuration Settings> Allow Reject on Closing Report Stage.

 

Omnitable Multi-Select/Single-Select

  • Feature: Omnitable

  • Level of Configuration: Low

Administrators can now control how many records users can select in an Omnitable by configuring the maximum row selection limit.

Previously, Omnitable's multi-select checkboxes supported up to 2000 records but lacked the ability to restrict selection to a single record or set configurable selection limits.

Now, you can configure the maxRowSelection parameter in your Omnitable Named Settings to control selection behavior. This allows you to enforce single-select mode with radio buttons, limit multi-select to a specific number of records, or disable selection entirely.

Selection behaviors based on configuration:

  • maxRowSelection = 0: All row checkboxes are disabled, and users cannot select any records

  • maxRowSelection = 1: Checkboxes are replaced with radio buttons, allowing only one record to be selected at a time. The "Select All" checkbox is hidden

  • maxRowSelection > 1: Users can select up to the configured number of records. Once the limit is reached, all unselected checkboxes become disabled. When "Select All" is used, only the top N records are selected

  • maxRowSelection not specified: Default behavior is maintained (checkbox multi-select with 2000 record limit)

Configuration

To configure row selection limits for an Omnitable:

  1. Navigate to Setup > Custom Metadata Types > Named Settings.

  2. Find your Omnitable configuration record.

  3. Edit the JSON configuration.

  4. Add the maxRowSelection parameter at the top level with your desired value (integer).

  5. Select Save.

Selected IDs Exposed to Flow

  • Feature: Omnitable

  • Level of Configuration: Low

The Omnitable component now exposes selected record IDs to any configured Flow action. When a user selects rows — individually or using the select-all checkbox — the IDs of all selected records are passed through as a variable to the triggered Flow. This enables admins to build Flow-based bulk actions that operate on the specific records a user has selected in the table. Selected rows automatically deselect once the action has been executed.

Impact on BHRC package: Custom Flow actions triggered from Omnitable can now reliably receive and act on the full list of selected record IDs, unlocking bulk automation use cases directly from the table view.