Environment Variables in Omnistudio Data Mappers and Integration Procedures (Managed Package)

For the managed package runtime, you can use environment variables to define Default Values and Filter Values, and in Formulas.

Managed Package app icon This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.

For example, the filter $Vlocity.N_DAYS_AGO:30 extracts the Cases created in the last 30 days.

If you’re using an environment variable as a Filter value, you must double-quote it.

Environment Variable

Description

$Vlocity.TODAY

Today’s date

$Vlocity.TOMORROW

Tomorrow’s date

$Vlocity.NOW

Current date and time. $Vlocity.NOW applies the user or org time zone, while the NOW() function applies UTC time.

$Vlocity.N_DAYS_FROM_NOW:{N}

The date the specified number of days from now

$Vlocity.N_DAYS_AGO:{N}

The date the specified number of days ago

$Vlocity.NULL

Null

$Vlocity.StandardPricebookId

Id of the standard price book

$Vlocity.DocumentsFolderId

Documents folder Id

$Vlocity.true or $Vlocity.TRUE

Boolean TRUE

$Vlocity.false or $Vlocity.FALSE

Boolean FALSE

$Vlocity.UserId

Current user Id

$Vlocity.Percent

Percent character. Useful for escaping % characters in URLs and text field values in Omniscripts, Integration Procedures, and Data Mappers so they aren't mistaken for merge field syntax.

$Vlocity.CpuTotal

Apex CPU value

$Vlocity.DMLStatementsTotal

Number of Data Manipulation Language statements

$Vlocity.DMLRowsTotal

Number of Data Manipulation Language rows

$Vlocity.HeapSizeTotal

Heap size value

$Vlocity.QueriesTotal

Number of queries run

$Vlocity.QueryRowsTotal

Number of query rows fetched

$Vlocity.SoslQueriesTotal

Number of SOSL queries run