Release notes 3.96.0
Week of June 15, 2026
We made something for you…
And we think you’ll love it.
Stop guessing — find every pipe or schedule using your data source instantly
Here we go again! You can now quickly identify which pipes and schedules depend on any given data source, directly from the Data module. A new Used by option in the data source's More options
menu opens a panel listing all dependent pipes and schedulers by name, with each entry linking directly to the corresponding pipe for immediate inspection or management.
Previously, determining whether a data source was in use required manually navigating through each pipe individually, a time-consuming process that increased the risk of accidentally disrupting active pipelines when modifying or deleting sources. With this update, you can confidently clean up unused or obsolete data sources, better understand data lineage, and reduce the time spent investigating dependencies. If a data source has no dependents, a clear informative message is displayed so users can proceed without uncertainty. Learn more about the Used by functionality.
It's even better now
We took the time to revamp some of the things you already love.
New OAuth 2.0 authentication support for Workday connectors
We've been busy! The Workday SOAP API, Workday RaaS, and Workday export connectors have been updated to support OAuth 2.0 authentication. Previously, these connectors required only a username and a password to connect. Users can now choose between Basic Authentication and OAuth 2.0 when configuring a Workday connector. This update applies to both the Workday connector and the Workday Reports-as-a-Service connector.
Learn more about the Workday authentication:
New Workday export tool: Dynamic timestamp support for Batch ID
The Workday Export Tool now supports a dynamic timestamp in the Batch ID field. A new checkbox option is available when configuring a Workday Payroll export, allowing you to append a system-generated timestamp to your static Batch ID text at runtime.
When enabled, the Batch ID is resolved at the moment the export execution begins and follows the format: static_text_{YYYY-MM-DDThh_mm_ss.msZ}
For example, a Batch ID configured as PAYROLL_RUN would be sent to Workday as PAYROLL_RUN_2026-06-08T14_30_00.000Z.
The resolved Batch ID, including the appended timestamp, is recorded in the Varicent ELT export run history and logs, ensuring the value displayed in Varicent ELT matches what is sent to Workday.
Learn more about the Workday export tool.
We crushed a bug!
And we're so happy that we did...
Issue | Bug number |
|---|---|
Fixed an issue where a Varicent ELT pipe export node used as a data source in another pipe returned duplicate rows in downloads, causing a mismatch between the preview row count and the actual downloaded data. | 232105 |
Created an enhancement to allow the Batch ID field in the Workday Export tool to be populated dynamically using a data column value or runtime variable instead of a static string. | 230801 |