You need to design a complex Appian integration to call a RESTful API. The RESTful API will be used to update a case in a customer's legacy system.
What are three prerequisites for designing the integration?

• A. Understand the business rules to be applied to ensure the business logic of the data.
• B. Understand the different error codes managed by the API and the process of error handling in Appian.
• C. Understand the content of the expected body, including each field type and their limits.
• D. Define the HTTP method that the integration will use.
• E. Understand whether this integration will be used in an interface or in a process model.

Your client's customer management application is finally released to Production. After a few weeks of small enhancements and patches, the client is ready to build their next application. The new application will leverage customer information from the first application to allow the client to launch targeted campaigns for select customers in order to increase sales. As part of the first application, your team had built a section to display key customer information such as their name, address, phone number, how long they have been a customer, etc. A similar section will be needed on the campaign record you are building. One of your developers shows you the new object they are working on for the new application and asks you to review it as they are running into a few issues. What feedback should you give?

• A. Point the developer to the relevant areas in the documentation or Appian Community where they can find more information on the issues they are running into.
• B. Provide guidance to the developer on how to address the issues so that they can proceed with their work.
• C. Create a duplicate version of that section designed for the campaign record.
• D. Ask the developer to convert the original customer section into a shared object so it can be used by the new application.

For each scenario outlined, match the best tool to use to meet expectations. Each tool will be used once Note: To change your responses, you may deselected your response by clicking the blank space at the top of the selection list.

You are tasked to build a large-scale acquisition application for a prominent customer. The acquisition process tracks the time it takes to fulfill a purchase request with an award.
The customer has structured the contract so that there are multiple application development teams.
How should you design for multiple processes and forms, while minimizing repeated code?

• A. Create a Center of Excellence (CoE).
• B. Create a Scrum of Scrums sprint meeting for the team leads.
• C. Create duplicate processes and forms as needed.
• D. Create a common objects application.

You are designing a process that is anticipated to be executed multiple times a day. This process retrieves data from an external system and then calls various utility processes as needed. The main process will not use the results of the utility processes, and there are no user forms anywhere.
Which design choice should be used to start the utility processes and minimize the load on the execution engines?

• A. Start the utility processes via a subprocess asynchronously.
• B. Use the Start Process Smart Service to start the utility processes.
• C. Use Process Messaging to start the utility process.
• D. Start the utility processes via a subprocess synchronously.