For the managed package runtime, you can call Data Mappers using Apex or a REST API. You can also use custom input and output and environment variables in Data Mappers.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
- Omnistudio Data Mapper REST API (Managed Package)
For the managed package runtime, you can invoke any type of Data Mapper using the Data Mapper REST API. To update Salesforce objects using a Data Mapper Load, issue a POST request that includes a JSON payload that is formatted to comply with the input that the Data Mapper load expects. To retrieve data from Salesforce, issue a GET call to a Data Mapper Extract, specifying the Id or parameters identifying the data to be retrieved. The data is returned in the response in JSON format. - Omnistudio Data Mapper Calls From Apex (Managed Package)
For the managed package runtime, to call a Data Mapper from Apex, call thevlocity_ins.DRGlobal.processObjectsJSON()method, specifying the name of the Data Mapper and the input data that it requires. - DRGlobal Class and Methods (Managed Package)
For the managed package runtime, the DRGlobal class provides multiple methods for calling Omnistudio Data Mappers from Apex. - 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. - Custom Input and Output for Omnistudio Data Mappers in Omnistudio for Managed Packages (Managed Package)
For the managed package runtime, by default, Data Mappers handle JSON and XML data. To handle other data formats, you can configure a Data Mapper to use a custom input or output that you implement is a custom class. For example, you can define a Data Mapper Transform that accepts CSV-formatted data and outputs it as JSON.