Integeration Procedure (IP)

How to use Response Action In Integration

Blogs, Integeration Procedure (IP), Vlocity/OminiStudio |

Integration Procedures play a critical role in Salesforce OmniStudio by enabling data exchange between Salesforce, external systems, and OmniScripts. One of the most important elements inside an Integration Procedure is the Response Action, which controls how response data is captured, transformed, and sent back to an OmniScript or FlexCard. In this article, we will learn how to use Response Action in an Integration Procedure, how data flows through it, and how it is finally returned to an OmniScript. Why Response Action Is Important When an Integration Procedure interacts with: External APIs Salesforce objects DataRaptors Other integration steps it always produces a response. The Response Action determines: What data is captured from the response How the response is transformed What data is sent back to OmniScript Whether full or partial data is returned Without a Response Action, OmniScript cannot reliably consume data from the Integration Procedure. Sending Integration Procedure Data to OmniScript The basic flow looks like this: OmniScript calls an Integration Procedure Integration Procedure executes its steps Response Action captures and maps response data Data is sent back to OmniScript This makes Response Action the bridge between Integration Procedures and OmniScripts. Step 1: Adding Response Action in Integration Procedure Design the Integration Procedure Open OmniStudio → Integration Procedures Open or create an Integration Procedure Add your required integration steps (DataRaptor, HTTP Action, etc.) Configure the Response Action Drag a Response Action into the Integration Procedure Place it after the integration step whose data you want to return This defines what happens before the Integration Procedure completes The Response Action ensures the response is captured and prepared for output. Response Action Configuration Key configuration options include: Return Full Data JSON When set to True, the entire response JSON is returned Useful for debugging or when OmniScript needs all data Send JSON Path Used to send only a specific node from the response Send JSON Node Allows selection of a specific response node for downstream steps If Return Full Data JSON is enabled, all response data is visible in the Preview tab. Response Action In Integration Procedure Execute Integration Procedure Go to the Preview tab Click Execute Review the response output This confirms whether the Response Action is correctly configured. On Preview Tab Step 2: Using Send/Response Transformations Understanding Send/Response Transformations Send/Response Transformations define: What data is sent into the Integration Procedure What data is passed between steps What data is returned to OmniScript They allow precise control over JSON structures. Send JSON Path in Response Action If you want to pass only a specific part of the response to the next step or OmniScript, configure: Send JSON Path in the Integration Step Send JSON Node in the Response Action Example Response structure: {   “result”: {     “data”: {       “Id”: “001xx”,       “Name”: “Test Account”     }   } }   Configuration: Send JSON Path: $.result Send JSON Node: data This sends only the data node forward. Passing Data to OmniScript From the Response Action: All required data is passed back to OmniScript OmniScript can consume this data using: Integration Procedure Action JSON Path mappings Set Values elements Using Set Values in Response Action A common practice is: Create Set Values Map response data to custom output nodes Return only structured, required values This avoids sending unnecessary data to OmniScript.  Note :– We create a setvalues and pass data in response action. In Response Action On Preview Tab After Click Execute   On Preview Tab Step 3: Additional Output Response Configuration What Is Additional Output Response? Additional Output Response allows you to define custom output nodes that OmniScript will receive from the Integration Procedure. Return Only Additional Output When this option is set to True: OmniScript receives only the defined additional output Full response JSON is excluded Payload becomes cleaner and easier to manage This is recommended for production implementations. Defining Additional Output You can specify: Individual fields Custom objects Structured JSON nodes These outputs are explicitly mapped and returned to OmniScript. How OmniScript Consumes the Response In OmniScript: Drag an Integration Procedure Action Map inputs using Extra Payload Capture response using Response JSON Path Use data in: Text blocks Decision elements Set Values Navigation logic This enables real-time UI updates and backend interactions. In Response Action On Preview Tab After Click On Execute   On Preview Tab Best Practices for Response Action Always use a Response Action when returning data Avoid returning full JSON unless necessary Use Send JSON Path to control payload size Use Set Values for clean output structures Enable Return Only Additional Output for production Test Integration Procedures using Preview before OmniScript integration Conclusion The Response Action is a core component of Integration Procedures in OmniStudio. It ensures that response data is properly captured, transformed, and delivered to OmniScript in a structured and reliable manner. By understanding how to configure Response Actions, Send/Response Transformations, and Additional Output Responses, you can build scalable, maintainable, and efficient integrations within Salesforce OmniStudio. Mastering this concept is essential for anyone working with OmniScripts, Integration Procedures, DataRaptors, and FlexCards.

How to use Response Action In Integration Read More »

How To Use SetValues In Integration Procedure

Blogs, Integeration Procedure (IP), Vlocity/OminiStudio |

Integration Procedures (IPs) in Salesforce Industries are used to process data efficiently without writing code. One of the most commonly used elements inside an Integration Procedure is SetValues. It allows you to manipulate, merge, calculate, and transform data before sending it to the output or another system. In this article, we will learn how to use SetValues in an Integration Procedure, how to merge element values, perform calculations, concatenate fields, and finally display the result using Response Action. What Is SetValues in Integration Procedure? SetValues is an element in Integration Procedure that allows you to: Assign static values Merge values from different elements Perform calculations using formulas Concatenate multiple fields Retrieve values from arrays or lists It helps prepare and structure data in the required format before sending it to OmniScript, FlexCard, or an external system. Use Case of SetValues SetValues is commonly used when: You need to combine multiple input fields You want to format output data Calculations are required without Apex Data needs to be reused in another SetValues Final output must be shown in Preview or Response Step 1: Create an Integration Procedure The first step is to create an Integration Procedure. Steps: Go to Setup. Search for Integration Procedure. Click New. Enter required details such as: Name Type Subtype Language Save the Integration Procedure. Once created, open it in Designer mode. Step 2: Add SetValues to the Structure Panel Now, add the SetValues element to the Integration Procedure. Steps: Open the Structure Panel. Drag and drop SetValues into the Integration Procedure flow. Rename it meaningfully (for example: SetValues_1). This SetValues element will be used to define and manipulate data values. Step 3: Configure Element Value Mapping Inside SetValues, you define how values are assigned or merged. Element Value Map Configuration: Click on the SetValues element. Go to the Element Value Map section. Click Add New Value. Define: Element Name (output variable) Value (static value, merge field, or formula) This mapping helps transfer data from input JSON or other elements into new variables. Step 4: Perform Operations Using SetValues SetValues supports multiple operations that can be performed easily. Common Operations in SetValues Merge Fields You can merge values from input or previous elements using merge syntax. Example: %Input:FirstName%   Calculations Using Formulas You can perform mathematical operations like addition or multiplication. Example: %Input:Price% * %Input:Quantity%   Concatenate Two Merge Fields You can combine multiple fields into one value. Example: %Input:FirstName% %Input:LastName%   Retrieving an Array Value You can access values from an array using index-based notation. Example: %Input:Items[0].Name% These features allow you to handle complex logic without writing Apex code. In SetValues Step 5: Configure a Second SetValues for Concatenation In many cases, one SetValues depends on values created in another SetValues. Steps: Drag and drop another SetValues element. Rename it (for example: SetValues_2). In the Element Value Map: Reference values created in the first SetValues Concatenate or manipulate them as needed Example: %SetValues_1:FullName% – %SetValues_1:TotalAmount%   This shows how data can flow from one SetValues element to another. In SetValues 2 Step 6: Add Response Action to Display Output To display the output data in the Preview Tab, you must use Response Action. Steps: Drag Response Action into the Structure Panel. Configure it to return the required data nodes. Map the values created in SetValues to the Response Action output. Without Response Action, the output will not be visible during execution. In Response Action Step 7: Execute and View Results in Preview Tab After completing the configuration: Steps: Click Validate to ensure there are no errors. Click Activate. Click Execute. Go to the Preview Tab. You will now see: Merged values Calculated results Concatenated fields Final output structure This confirms that SetValues and Response Action are working correctly. On preview tab Best Practices for Using SetValues Use meaningful names for SetValues elements Avoid complex logic in a single SetValues Chain SetValues for better readability Always use Response Action for output visibility Validate and test with sample input data Conclusion SetValues is a powerful and essential component of Integration Procedures in Salesforce Industries. It allows you to merge, calculate, concatenate, and transform data without writing Apex code. By combining multiple SetValues and using Response Action, you can efficiently control the data flow and output of your Integration Procedure. Mastering SetValues helps you build scalable, reusable, and maintainable integrations that work seamlessly with OmniScripts and FlexCards.

How To Use SetValues In Integration Procedure Read More »

How To Enable Flex Card in OmniStudio(Vlocity) Salesforce

Blogs, DataRaptor, FlexCard, Integeration Procedure (IP), Omniscript(OS), Vlocity/OminiStudio |

FlexCards are a core UI component of Salesforce OmniStudio (Vlocity). They allow you to display data in a responsive, reusable, and dynamic card-based layout without writing code. Before you can create or use FlexCards, you must ensure that OmniStudio and FlexCards are properly enabled in your Salesforce org. This article explains how to enable FlexCard in OmniStudio, including required permissions, settings, and verification steps. What Is a FlexCard in OmniStudio? A FlexCard is a lightweight UI component used to: Display Salesforce or external data Work with OmniScripts and Integration Procedures Show summary views, KPIs, or record details Reuse UI logic across apps and pages FlexCards are part of the OmniStudio Designer and rely on proper feature enablement and user access. Prerequisites to Enable FlexCard Before enabling FlexCards, make sure: OmniStudio (Vlocity) is installed in your org You have System Administrator access Required OmniStudio licenses are assigned Your org is Lightning Experience–enabled Step 1: Verify OmniStudio Is Installed FlexCards are available only if OmniStudio is installed. Steps: Go to Setup Search for Installed Packages Verify that OmniStudio, Vlocity, or Salesforce Industries package is installed If OmniStudio is not installed, FlexCards will not appear. you do not do the setting then this is the error Step 2: Enable OmniStudio Designer FlexCards are created inside OmniStudio Designer, so this must be enabled. Steps: Go to Setup Search for OmniStudio Settings Enable: OmniStudio Designer OmniStudio Runtime Save the settings This allows access to FlexCards, OmniScripts, DataRaptors, and Integration Procedures. Warning Tab Click Than Show This Link Remote Site Setting Step 3: Assign Required Permission Sets Even if OmniStudio is enabled, FlexCards will not be visible without proper permissions. Required Permission Sets: OmniStudio Admin OmniStudio Designer OmniStudio Runtime Steps: Go to Setup Open Users Select your user Click Permission Set Assignments Assign the required OmniStudio permission sets Log out and log in again after assignment. Fill the Tab Step 4: Enable FlexCard Feature Access FlexCards are controlled through OmniStudio capabilities. Steps: Go to Setup Search for Custom Permissions Ensure permissions related to: FlexCard OmniStudio UI Vlocity Cards are enabled via permission sets This ensures the FlexCard option appears in the Designer. Step 5: Access FlexCard from OmniStudio Designer Once enabled, you can access FlexCards. Steps: Click the App Launcher Search for OmniStudio Designer Open OmniStudio Designer Select FlexCards from the left panel Click New to create a FlexCard If FlexCard appears in the menu, it is successfully enabled. Step 6: Verify FlexCard Availability in Lightning App Builder FlexCards can be embedded into Lightning pages. Steps: Go to Lightning App Builder Edit a Record Page or App Page Search for FlexCard in Components Drag and drop it onto the page Configure required properties This confirms FlexCards are available at runtime. Common Issues and Troubleshooting FlexCard Not Visible in OmniStudio Designer Check OmniStudio permission sets Verify OmniStudio Designer is enabled Confirm package installation FlexCard Not Rendering on Page Ensure OmniStudio Runtime permission is assigned Activate the FlexCard Check Data Source configuration No Data Displayed Validate DataRaptor or Integration Procedure Confirm context variables like {recordId} Best Practices for Using FlexCards Always activate FlexCards before use Use reusable FlexCards for performance Prefer Integration Procedures for complex logic Test FlexCards using Preview mode Use context variables for dynamic data Conclusion Enabling FlexCards in OmniStudio is a foundational step for building modern, scalable Salesforce UI solutions. By ensuring OmniStudio is installed, permissions are assigned, and Designer access is enabled, you can start creating powerful FlexCards that integrate seamlessly with OmniScripts and Integration Procedures. Once enabled, FlexCards help you deliver faster, more interactive user experiences without writing Apex or Lightning Web Components.

How To Enable Flex Card in OmniStudio(Vlocity) Salesforce Read More »

How To Use ListAction In Integration Procedures

Blogs, Integeration Procedure (IP), Vlocity/OminiStudio |

In OmniStudio (Vlocity) Salesforce, Integration Procedures (IP) are used to process data efficiently without writing Apex code. One of the most powerful elements inside an Integration Procedure is ListAction. ListAction allows you to loop through a list of records and perform actions on each item individually. In this article, we will understand what ListAction is, why it is used, and how to configure it step by step inside an Integration Procedure. What Is ListAction in Integration Procedure? ListAction is a looping mechanism in an Integration Procedure. It iterates over an array or list of data and executes child elements (like SetValues, DataRaptor, Integration Action, or Response Action) for each item in the list. It works similar to a FOR LOOP in Apex but is fully declarative. Why Use ListAction? ListAction is commonly used when: You receive multiple records from a DataRaptor or Integration Action You need to process each record individually You want to perform calculations, transformations, or updates on each list item You need to loop data before sending it to OmniScript or FlexCard Common Use Cases of ListAction Loop through a list of Accounts or Cases Perform calculations on each record Build a transformed response structure Update multiple records using DataRaptor Post Prepare formatted output for OmniScript or FlexCard Basic Structure of ListAction A ListAction has three key parts: Input List Loop Processing Elements Output List All actions inside ListAction run once per item in the list. Step 1: Create an Integration Procedure Go to OmniStudio Designer Select Integration Procedures Click New Provide: Name Type (Reusable or not) Save the Integration Procedure In List Action Step 2: Get Data That Returns a List Before using ListAction, you need a list input. Common sources: DataRaptor Extract Integration Action SetValues (array creation) Example: A DataRaptor Extract that returns a list of Accounts: Accounts[]   This list will be used as input for ListAction. In Response Action On the preview tab.  Step 3: Add ListAction to Integration Procedure Drag ListAction into the Structure panel   Place it after the step that returns list data   Rename it (example: Loop_Accounts) In List Action On the preview tab  On preview tab Step 4: Configure ListAction Properties List Input Path Specify the JSON path of the list: Accounts   This tells the Integration Procedure which list to loop through. Loop Variable Define a variable name to represent current record: CurrentAccount   This variable holds one item at a time during iteration. Advanced Merge = true Well Done!!! We got the result in preview tab  On preview tab Step 5: Add Child Actions Inside ListAction Now add elements inside the ListAction. These will execute for each list item. Commonly used actions: SetValues Perform calculations Merge fields Rename attributes Example: CurrentAccount.Name + ‘ – Processed’   DataRaptor Post Update records Insert child records Example: Update Account Status for each record. Integration Action Call external APIs per record Send individual payloads Step 6: Store Output Using ListAction Output To collect results from each iteration: Enable Output List Define Output Path: ProcessedAccounts   Each iteration’s result will be added to this output list. Step 7: Use Response Action to Send Data To return data to OmniScript or FlexCard: Add Response Action Enable Return Full Data JSON (optional) Or return specific node: ProcessedAccounts   This makes the processed list available to the caller. Example Scenario Scenario: You fetch a list of Accounts and want to: Append a label to Account Name Return the modified list to OmniScript Flow: DataRaptor Extract → Accounts[] ListAction → Loop Accounts SetValues → Modify Name Response Action → Send ProcessedAccounts Best Practices for Using ListAction Always validate input list path Keep ListAction logic lightweight Avoid unnecessary nesting Use meaningful loop variable names Return only required data for performance Common Mistakes to Avoid Incorrect List Input Path Using wrong JSON structure Forgetting to store output Returning too much data in Response Action Not testing in Preview tab Testing ListAction Open Integration Procedure Go to Preview Provide sample JSON input Click Execute Verify loop output and response Conclusion ListAction is a powerful feature in Integration Procedures that allows you to process arrays efficiently without Apex. It plays a critical role in data transformation, looping logic, and preparing structured responses for OmniScripts and FlexCards. Mastering ListAction helps you build scalable, high-performance OmniStudio solutions with clean and reusable logic.

How To Use ListAction In Integration Procedures Read More »

How To Use DataRaptorPost In Integration Procedures

Blogs, Integeration Procedure (IP), Vlocity/OminiStudio |

In OmniStudio (Vlocity) Salesforce, Integration Procedures (IP) are used to orchestrate data processing without writing Apex. One of the most important actions inside an Integration Procedure is DataRaptorPostAction, which allows you to insert, update, or upsert records in Salesforce using a DataRaptor Load (Post). This post explains what DataRaptor Post is, when to use it, and how to configure it step by step inside an Integration Procedure. What Is DataRaptor Post Action? DataRaptorPostAction is used in an Integration Procedure to send data to Salesforce and perform DML operations, such as: Insert records Update records Upsert records It uses a DataRaptor Load interface, which defines how incoming data maps to Salesforce objects. When Should You Use DataRaptor Post in Integration Procedures? Use DataRaptor Post when: You need to save OmniScript or API data into Salesforce You want to avoid Apex for DML operations You need high performance and bulk-safe processing You are updating records from OmniScript, FlexCard, or API requests Step 1: Create an Integration Procedure Navigate to OmniStudio → Integration Procedures Click New Enter: Name Type (Reusable or Standard) Save the Integration Procedure This Integration Procedure will act as the orchestrator for posting data. Step 2: Add DataRaptorPostAction to the Structure Panel In the Structure panel, drag DataRaptor Post Action Place it at the correct position in the execution flow Rename it for clarity (example: Post_Account_Data) Step 3: Configure DataRaptor Interface In the DataRaptor Interface field: Select the DataRaptor Load (Post) that you want to use This DataRaptor must already be created and activated This interface defines: Which Salesforce object will be updated Which fields will be mapped What operation will be performed (Insert / Update / Upsert) Post Data Raptor Step 4: Configure Additional Input / Output / Failure Response Inside DataRaptorPostAction, scroll to: ADDITIONAL INPUT / OUTPUT / FAILURE RESPONSE Important options: Send Only Additional Input Set to True if you want to send only mapped input Set to False if you want to send full Integration Procedure data Best Practice: Set this to True for better performance and cleaner payloads. Additional Output You can define what response you want back from the DataRaptor, such as: Record Id Success flag Error message Failure Response Configure error handling to capture: Validation errors Required field errors DML exceptions Field mapping for send data in post data raptor Step 5: Configure Field Mapping in DataRaptor Load Now open the DataRaptor Load (Post) used above. Inside DataRaptor Load: Select the Target Object (e.g., Account) Choose the Operation Type: Insert Update Upsert Map source fields to Salesforce fields Field mapping in DataRaptor Load Step 6: Add ResponseAction to Send Data Back To display or return results: Drag ResponseAction into the Structure panel Place it after DataRaptorPostAction Configure: Return Full Data JSON = True OR Return a specific node using %%PostResult%% This allows the Integration Procedure to return: Created/updated record Id Status of the operation Error messages (if any) In Response Acton Step 7: Provide Input Parameters in Preview Tab Go to the Preview tab of the Integration Procedure. Example Input JSON: {   “Name”: “Test Account”,   “Phone”: “1234567890” }   These values must match: The input expected by the DataRaptor Load The field mapping defined earlier Step 8: Execute the Integration Procedure Click Execute Check the response JSON Verify: Record is created or updated in Salesforce Response contains success or error details On Preview Tab Result Common Use Cases of DataRaptor Post in IP Save OmniScript form data Update Account, Contact, Case records Bulk record updates using ListAction + DataRaptor Post API-based data ingestion FlexCard action-based updates Best Practices Always use Send Only Additional Input = True Validate required fields before posting Use ListAction for bulk updates Return minimal response data Handle errors using Failure Response Common Mistakes to Avoid Using incorrect DataRaptor Interface name Missing required fields in input JSON Not activating DataRaptor Load Returning too much data in ResponseAction Skipping error handling Conclusion DataRaptorPostAction is the preferred way to perform create and update operations in OmniStudio Integration Procedures. It provides a declarative, high-performance, and scalable alternative to Apex, making it ideal for OmniScript and FlexCard integrations. Mastering DataRaptor Post helps you build robust, maintainable OmniStudio solutions.

How To Use DataRaptorPost In Integration Procedures Read More »

How To Use Delete Action In Integration Procedures

Blogs, Integeration Procedure (IP), Vlocity/OminiStudio |

The Delete Action in Integration Procedures allows you to remove Salesforce records directly using OmniStudio, without writing any Apex code. It is commonly used when you want to delete records from an OmniScript or FlexCard based on a user action, such as clicking a button or submitting a form. This approach keeps the implementation lightweight, fast, and easy to maintain. In this post, we will understand how the Delete Action works, how to configure it correctly, and how to call it from an OmniScript. Understanding Delete Action in Integration Procedures Delete Action is a standard OmniStudio Integration Procedure element designed specifically for record deletion. It works by accepting a Salesforce record Id and deleting the corresponding record from the specified object. Unlike DataRaptor or Apex-based solutions, Delete Action does not require field mappings or custom logic, making it ideal for straightforward delete operations. This action is especially useful when you need to delete child records, clean up related data, or allow users to manage records directly from a guided OmniScript flow. Creating the Integration Procedure To begin, create a new Integration Procedure from the OmniStudio console. Provide a meaningful name and description so the purpose of the Integration Procedure is clear. Once created, save the Integration Procedure before adding any actions. After saving, drag the Delete Action onto the Integration Procedure canvas. This action will handle the actual deletion of the record in Salesforce. Configuring the Delete Action In the Delete Action properties, you must specify the Salesforce object and the record Id to be deleted. The Delete SObject Type should be the API name of the object, such as Account, Contact, or a custom object. The Path To Id is where the record Id will be passed in the request JSON. This Id usually comes from an OmniScript, FlexCard, or context variable. As long as the correct Id is provided, the Delete Action will remove the record successfully. Once configured, the Delete Action is ready to perform deletions. Using Response Action to Return Status Although the Delete Action deletes the record, it does not automatically send a confirmation back to the calling component. To handle this properly, it is recommended to add a Response Action after the Delete Action. The Response Action allows you to send information such as a success message, deleted record Id, or status flag back to the OmniScript or FlexCard. This helps in displaying confirmation messages or triggering additional logic on the UI side. After adding the Response Action, configure it to return the required output data and save your changes. Activating the Integration Procedure Before the Integration Procedure can be used, it must be activated. Activation makes it available for use across OmniScripts and FlexCards. Without activation, the Integration Procedure will not appear in the selection list. Calling Delete Action from OmniScript Next, open or create an OmniScript where the delete operation is required. Drag an Integration Procedure Action onto the OmniScript canvas and select the Integration Procedure you created. In the Remote Properties → Extra Payload, pass the record Id that needs to be deleted. This Id can come from the Context Id, a DataRaptor response, or user-selected data. Once the Id is passed correctly, the OmniScript is fully connected to the Delete Action.   Delete Action an Integration Procedures Testing the Delete Functionality To test the setup, go to the OmniScript preview. Provide a valid record Id in the Context Id or test parameters and trigger the delete action. Once executed, the record will be immediately deleted from Salesforce. If a Response Action is configured, you will also see the confirmation or response data returned on the preview screen.   Response Action Best Practices for Using Delete Action While Delete Action is powerful, it should be used carefully. Always ensure that only authorized users can delete records. Adding confirmation messages and using role-based access control helps prevent accidental deletions. In production environments, it is also a good idea to log delete operations or notify users after successful deletion. Result On Preview Tab Conclusion The Delete Action in Integration Procedures offers a clean and efficient way to delete Salesforce records using OmniStudio. It eliminates the need for Apex or complex DataRaptor configurations and works seamlessly with OmniScripts and FlexCards. When used correctly with proper validation and confirmation, it becomes a reliable solution for record management in OmniStudio implementations.

How To Use Delete Action In Integration Procedures Read More »

How To Use HTTPAction In Integration Procedure

Blogs, Integeration Procedure (IP), Vlocity/OminiStudio |

–: “In this post, we will create a weather API key and retrieve India’s weather data. Step 1: First, create an API and key from the weather API. Next, create an Integration Procedure and drag an HTTP Action. Go to Remote Site Settings, click on ‘New,’ and paste the URL in the URL field, which is the API call URL (HTTP Path URL). HTTP Path: Here, we pass the API URL. HTTP Method: Set it to ‘Get’ to retrieve data from the API.” /*! elementor – v3.18.0 – 20-12-2023 */ .elementor-widget-image{text-align:center}.elementor-widget-image a{display:inline-block}.elementor-widget-image a img[src$=”.svg”]{width:48px}.elementor-widget-image img{vertical-align:middle;display:inline-block} HTTP Action in Integration Procedure Step :– 2 On preview tab                      key = Name of the variable  witch is we pass in HTTP Path in %% sign  On Preview tab Salesforce Guide – https://help.salesforce.com/s/articleView?id=sf.os_http_action.htm&type=5 /*! elementor-pro – v3.18.0 – 20-12-2023 */ .elementor-slides .swiper-slide-bg{background-size:cover;background-position:50%;background-repeat:no-repeat;min-width:100%;min-height:100%}.elementor-slides .swiper-slide-inner{background-repeat:no-repeat;background-position:50%;position:absolute;top:0;left:0;bottom:0;right:0;padding:50px;margin:auto}.elementor-slides .swiper-slide-inner,.elementor-slides .swiper-slide-inner:hover{color:#fff;display:flex}.elementor-slides .swiper-slide-inner .elementor-background-overlay{position:absolute;z-index:0;top:0;bottom:0;left:0;right:0}.elementor-slides .swiper-slide-inner .elementor-slide-content{position:relative;z-index:1;width:100%}.elementor-slides .swiper-slide-inner .elementor-slide-heading{font-size:35px;font-weight:700;line-height:1}.elementor-slides .swiper-slide-inner .elementor-slide-description{font-size:17px;line-height:1.4}.elementor-slides .swiper-slide-inner .elementor-slide-description:not(:last-child),.elementor-slides .swiper-slide-inner .elementor-slide-heading:not(:last-child){margin-bottom:30px}.elementor-slides .swiper-slide-inner .elementor-slide-button{border:2px solid #fff;color:#fff;background:transparent;display:inline-block}.elementor-slides .swiper-slide-inner .elementor-slide-button,.elementor-slides .swiper-slide-inner .elementor-slide-button:hover{background:transparent;color:inherit;text-decoration:none}.elementor–v-position-top .swiper-slide-inner{align-items:flex-start}.elementor–v-position-bottom .swiper-slide-inner{align-items:flex-end}.elementor–v-position-middle .swiper-slide-inner{align-items:center}.elementor–h-position-left .swiper-slide-inner{justify-content:flex-start}.elementor–h-position-right .swiper-slide-inner{justify-content:flex-end}.elementor–h-position-center .swiper-slide-inner{justify-content:center}body.rtl .elementor-widget-slides .elementor-swiper-button-next{left:10px;right:auto}body.rtl .elementor-widget-slides .elementor-swiper-button-prev{right:10px;left:auto}.elementor-slides-wrapper div:not(.swiper-slide)>.swiper-slide-inner{display:none}@media (max-width:767px){.elementor-slides .swiper-slide-inner{padding:30px}.elementor-slides .swiper-slide-inner .elementor-slide-heading{font-size:23px;line-height:1;margin-bottom:15px}.elementor-slides .swiper-slide-inner .elementor-slide-description{font-size:13px;line-height:1.4;margin-bottom:15px}} Thank You we are creating vlocity solutions 9to9cloudswelcome in our website 9to9clouds.com Click HereThank You for Vistewe solve all vlocity && Apex && LWC …problems in salesforce development Vlocity/Blogs Previous slide Next slide

How To Use HTTPAction In Integration Procedure Read More »

How To Use ConditionalBlock In Integration Procedures

Blogs, Integeration Procedure (IP), Vlocity/OminiStudio |

–: In this page we create conditional block here we pass the country name which name is match than that setvalues is execute Integration Procedure > ConditionalBlock >Set Values > ResponseAction Step :– 1  “First, we create an Integration Procedure and drag a ConditionalBlock. In the ConditionalBlock, set the If-Else Block to ‘true’ (if checked as true, it works like an If-Else block).” /*! elementor – v3.18.0 – 20-12-2023 */ .elementor-widget-image{text-align:center}.elementor-widget-image a{display:inline-block}.elementor-widget-image a img[src$=”.svg”]{width:48px}.elementor-widget-image img{vertical-align:middle;display:inline-block} ConditionalBlock in Integration Procedure  Step :– 2 “In the ConditionalBlock, drag a Set Values to store some data. Element Value Map = here we Store data in  name Node                       Executed Conditional Formula = here we give  Condition if Condition return True                        than Its Execution Set Values in ConditionalBlock In Preview Tab In Input Parameters  = { “Country”: “INDIA”} { “Country”: “INDIA” } Step :– 3 “On the Preview tab, after clicking ‘Execute,’ we can view the results in the Debug Log.” In Debug Log Result Salesforce Guide = https://help.salesforce.com/s/articleView?id=sf.os_conditional_block_properties_48548.htm&type=5

How To Use ConditionalBlock In Integration Procedures Read More »

How To Use LoopBlock In Integration Procedures

Blogs, Integeration Procedure (IP), Vlocity/OminiStudio |

Integration Procedures > LoopBlock > DataRaptorExtractAction > ResponseAction Step 1: Create an ExtractDataRaptor: Create a new ExtractDataRaptor. This DataRaptor is designed to extract data from contact. /*! elementor – v3.18.0 – 20-12-2023 */.elementor-widget-image{text-align:center}.elementor-widget-image a{display:inline-block}.elementor-widget-image a img[src$=”.svg”]{width:48px}.elementor-widget-image img{vertical-align:middle;display:inline-block} DataRaptor Extract Step :– 2    Create an Integration Procedure: Begin by creating a new Integration Procedure in your development environment. Drag a LoopBlock: Drag and drop a LoopBlock component into the structure panel of your Integration Procedure. Configure LoopBlock Parameters: In the LoopBlock configuration, set the following parameters: Loop List: Specify the node of the array or list that you want to iterate over. This represents the data source for the loop. Additional Loop Output: Use the %% sign and provide a name associated with the DataRaptor or variable that will store additional loop output. LoopBlock DataRaptor Step :– 3    DataRaptor in LoopBlock: Within the LoopBlock in your Integration Procedure, configure a DataRaptor action to perform operations during each iteration. Configure DataRaptor Parameters: Set the following parameters in the DataRaptor configuration: Data Source: Specify the node from the input obtained from the Preview Tab. Filter Value: Use a variable from the DataRaptor for the filter value. DataRaptor in LoopBlock Step :– 4   In ResponseAction: Within the Integration Procedure, locate the ResponseAction component. Configure Additional Output: In the ResponseAction configuration, set the “Additional Output” to the name of the LoopBlock. Step :– 5    On Preview Tab  Salesforce Gide = https://help.salesforce.com/s/articleView?id=sf.os_loop_block_properties.htm&type=5

How To Use LoopBlock In Integration Procedures Read More »

Scroll to Top