1. Design an OmniScript that collects user input for Contact details and saves it to Salesforce.
2. Use Conditional View in an Integration Procedure to display a field only when the Country value is set to “India.”
3. Create a FlexCard that displays a list of related Contacts for an Account.
4. Design an OmniScript to collect First Name, Last Name, Email, and Phone from the user. Upon clicking the Save button, the OmniScript should insert a new record into the Contact object.
5. You are asked to build a guided customer onboarding flow for a telecom company where users must enter personal details, select a plan, upload documents, and submit the data to Salesforce and an external KYC system. The OmniScript should prefill customer data if it already exists, validate inputs at each step, and handle failures from the external system gracefully. Explain how you would design the OmniScript structure, which DataRaptors and Integration Procedures you would use, and how you would manage error handling and user navigation.
6. When a user opens the customer screen, the system must automatically retrieve the customer’s personal details, recent interactions, and any open requests. All information should be displayed together in a single view without requiring the user to refresh the page. If one section of data fails to load, the remaining information should still be visible to the user.
7. As the user enters details such as age, income, and employment type, the system must continuously calculate and display an eligibility result. Any change to the input values should immediately update the result. The user should not be allowed to proceed if the entered data is invalid.
8. A single user action must trigger updates to multiple related records at the same time. All updates should be treated as one operation. If any update fails, none of the changes should be saved, and the user must be informed of the failure.
9. When a user partially completes a process and leaves the screen, the system must retain the entered information. If the user returns later, previously entered data should be restored automatically so the user can continue from where they left off.
10. Before creating a new record, the system must check for existing records with matching key details. If a potential duplicate is found, the user should be warned and allowed to review the existing record before proceeding.
11. An external API sends dates in the format MM-DD-YYYY, but your internal system requires YYYY-MM-DD. Transform all date fields from the external data so that they match the required internal format before further processing.
