Pass Using ACD300 Exam Dumps

To design a complex Appian integration to call a RESTful API, you need to have some prerequisites, such as:

• Define the HTTP method that the integration will use. The HTTP method is the action that the integration will perform on the API, such as GET, POST, PUT, PATCH, or DELETE. The HTTP method determines how the data will be sent and received by the API, and what kind of response will be expected.
• Understand the content of the expected body, including each field type and their limits. The body is the data that the integration will send to the API, or receive from the API, depending on the HTTP method. The body can be in different formats, such as JSON, XML, or form data. You need to understand how to structure the body according to the API specification, and what kind of data types and values are allowed for each field.
• Understand the different error codes managed by the API and the process of error handling in Appian. The error codes are the status codes that indicate whether the API request was successful or not, and what kind of problem occurred if not. The error codes can range from 200 (OK) to 500 (Internal Server Error), and each code has a different meaning and implication. You need to understand how to handle different error codes in Appian, and how to display meaningful messages to the user or log them for debugging purposes.

The other two options are not prerequisites for designing the integration, but rather considerations for implementing it.

• Understand whether this integration will be used in an interface or in a process model. This is not a prerequisite, but rather a decision that you need to make based on your application requirements and design. You can use an integration either in an interface or in a process model, depending on where you need to call the API and how you want to handle the response. For example, if you need to update a case in real-time based on user input, you may want to use an integration in an interface. If you need to update a case periodically based on a schedule or an event, you may want to use an integration in a process model.
• Understand the business rules to be applied to ensure the business logic of the data. This is not a prerequisite, but rather a part of your application logic that you need to implement after designing the integration. You need to apply business rules to validate, transform, or enrich the data that you send or receive from the API, according to your business requirements and logic. For example, you may need to check if the case status is valid before updating it in the legacy system, or you may need to add some additional information to the case data before displaying it in Appian.

The two formats that are available for data generation using an out-of-the-box Appian smart service are:

• A. CSV. This is a comma-separated values format that can be used to export data in a tabular form, such as records, reports, or grids. CSV files can be easily opened and manipulated by spreadsheet applications such as Excel or Google Sheets.
• C. Excel. This is a format that can be used to export data in a spreadsheet form, with multiple worksheets, formatting, formulas, charts, and other features. Excel files can be opened by Excel or other compatible applications.

The other options are incorrect for the following reasons:

• B. XML. This is a format that can be used to export data in a hierarchical form, using tags and attributes to define the structure and content of the data. XML files can be opened by text editors or XML parsers, but they are not supported by the out-of-the-box Appian smart service for data generation.
• D. JSON. This is a format that can be used to export data in a structured form, using objects and arrays to represent the data. JSON files can be opened by text editors or JSON parsers, but they are not supported by the out-of-the-box Appian smart service for data generation. Verified References: Appian Documentation, section “Write to Data Store Entity” and “Write to Multiple Data Store Entities”.

Requirement: Archive processes 2 days after completion or cancellation. Correct match: A. Processes that need to be available for 2 days after completion or cancellation, after which are no longer required nor accessible Exact explanation of correct match taken from Appian Documentation: This strategy is called “Archive after 2 days” and it is one of the options for process model data management in Appian. This strategy means that processes that complete or cancel will remain available for 2 days, after which they will be archived and no longer accessible. This strategy can help reduce the size of the process database and improve the performance of process reporting.

Requirement: Use system default (currently auto-archive processes 7 days after completion or cancellation). Correct match: C. Processes that remain available for 7 days after completion or cancellation, after which are archived when accessed Exact explanation of correct match taken from Appian Documentation: This strategy is called “Use system default” and it is one of the options for process model data management in Appian. This strategy means that processes that complete or cancel will remain available for 7 days, after which they will be archived when accessed. This strategy can help balance the availability and performance of process data, as it allows processes to be archived on demand rather than on a fixed schedule.

Requirement: Delete processes 2 days after completion or cancellation. Correct match: B. Processes that need to be available for 2 days after completion or cancellation, after which remain accessible Exact explanation of correct match taken from Appian Documentation: This strategy is called “Delete after 2 days” and it is one of the options for process model data management in Appian. This strategy means that processes that complete or cancel will remain available for 2 days, after which they will be deleted and no longer accessible. This strategy can help reduce the size of the process database and improve the performance of process reporting, but it also means that process data will be permanently lost.

Requirement: Do not automatically clean-up processes. Correct match: D. Processes that need to remain available without the need to unarchive Exact explanation of correct match taken from Appian Documentation: This strategy is called “Do not automatically clean-up” and it is one of the options for process model data management in Appian. This strategy means that processes that complete or cancel will remain available indefinitely without being archived or deleted. This strategy can help ensure the availability and integrity of process data, but it also means that the process database will grow over time and affect the performance of process reporting.

To build a large scale acquisition application for a prominent customer, you should design for multiple processes and forms, while minimizing repeated code. One way to do this is to create a common objects application, which is a shared application that contains reusable components, such as rules, constants, interfaces, integrations, or data types, that can be used by multiple applications. This way, you can avoid duplication and inconsistency of code, and make it easier to maintain and update your applications. You can also use the common objects application to define common standards and best practices for your application development teams, such as naming conventions, coding styles, or documentation guidelines. Verified References: [Appian Best Practices], [Appian Design Guidance]