Explanation
The consultant should design the FlexCards using a Parent FlexCard with multiple Child and Card Actions to meet these requirements. A Parent FlexCard is a FlexCard that can display data and actions in a card format, and also contain one or more Child FlexCards. The consultant can use a Parent FlexCard to display the account information, including account name, phone, and website. A Child FlexCard is a FlexCard that can display data and actions in a card format within a Parent FlexCard. The consultant can use multiple Child FlexCards to display the active opportunities and contracts related to the account. A Card Action is a button or a link that can invoke an OmniScript or an Integration Procedure from a FlexCard. The consultant can use multiple Card Actions to enable the user to view and renew contracts

The consultant should recommend adding a Set Errors element to meet this requirement. A Set Errors element can display an error message and prevent the OmniScript from proceeding if certain conditions are not met.
The consultant can use a Set Errors element to check if the email address field is empty when the agent selects the checkbox to email the receipt. If it is empty, the Set Errors element can show an error message and direct the user to return to the first step and enter the customer's email address

HTTP Actions provide native support for query parameters and are designed to handle REST endpoint construction correctly. When the external service expects values such as city and country in the URL query string, the consultant should configure them through the HTTP Action ' s Query Parameter settings. This approach improves maintainability, readability, and parameter management while avoiding manual URL construction errors. Request bodies are generally associated with POST, PUT, or PATCH operations rather than standard GET query-string requirements. A Data Mapper Load writes data to Salesforce and cannot replace an HTTP Action for external REST communication. Manual string concatenation is technically possible but is not a best practice because it creates maintenance challenges and increases the risk of malformed URLs. Integration Procedures are intended to orchestrate such external-service interactions efficiently.