Free Practice Questions for Appian ACD200 Exam

The most appropriate testing method to achieve this using Appian is Unit Testing. This is because unit testing allows you to test individual components of your application, such as forms, rules, or expressions, in isolation from other components or dependencies. Unit testing can help you verify that your Related Action works as expected for different users and data scenarios, as well as identify and fix any errors or bugs before deploying your application to production. References: Unit Testing

 The type of plug-in that should be created to perform a job in the background and not be available under an expression rule, connected system, or the process model is a servlet plug-in. A servlet plug-in is a plug-in that allows you to create custom servlets that can be accessed through a URL. Servlets are Java classes that run on a web server and handle requests and responses. Servlet plug-ins can be used to perform background tasks, such as sending notifications, logging events, or integrating with external systems, without exposing them to the end users or developers. References: Servlet Plug-ins, Appian Suite Plug-ins

 Two places to get information on process model memory usage are:

Process monitoring tab. The process monitoring tab is a feature in the Appian Designer that allows you to monitor and manage the performance and status of process models and instances. You can use the process monitoring tab to view various metrics and statistics about your processes, such as memory usage, execution time, node count, error count, etc. You can also filter, sort, and export the data for further analysis. The process monitoring tab can help you identify which processes have the highest memory footprint and potential performance issues.

Appian Health Check report. The Appian Health Check report is a tool that provides insights into application design patterns and performance risks in your environment. The report covers four areas of your environment: design, user experience, infrastructure, and configuration. The report also includes graphs highlighting historical trends, such as user activity, average response times, and resource utilization. The Appian Health Check report can help you identify which processes have the highest memory consumption and suggestions for mitigating them. References: Process Monitoring Tab, Understanding the Health Check Report

The most likely root cause of the error is that the view contains a large number of rows, requiring more time to fetch the data. This can result in a timeout or an out-of-memory error. To avoid this, you can use pagination or filters to limit the number of rows returned by the view. You can also optimize the view performance by using indexes, avoiding unnecessary joins, and reducing the number of columns. References: [Views], [View Performance]

The question is about the potential causes of a low completion rate of 10% for a process model. The following are two possible causes of this:

The process instances are long-lived compared to the configured days until archival or deletion. This means that the process instances take a long time to complete, and they are archived or deleted before they reach the end event. This reduces the completion rate, as only the instances that reach the end event are counted as completed.

A large number of instances are encountering process errors, and they are not being addressed by the production support team. This means that the process instances are stuck in an error state, and they cannot proceed to the next step or the end event. This reduces the completion rate, as only the instances that reach the end event are counted as completed.

The following are not likely causes of a low completion rate:

A large value is configured for days until archival or deletion compared to other process models in your application. This means that the process instances have more time to complete before they are archived or deleted. This should increase the completion rate, as more instances can reach the end event before they are removed from the system.

A large number of smart service nodes are configured in the process model. This means that the process model has a complex logic or functionality that requires multiple smart services. This does not directly affect the completion rate, as long as the smart services execute successfully and do not cause errors or delays.

References:

Process Model Metrics

Archiving and Deleting Process Instances

Two valid suggestions regarding this process are:

We should consider adding a timer exception which skips the “Edit/Credit Invoice” node after 24 hours. This suggestion would improve the user experience by preventing users from editing or crediting an invoice that is too old or has been already processed by another system. A timer exception can be added to any activity node to specify a deadline for completing the task. If the deadline is reached, the process flow will follow the exception path instead of the normal path.

We should add this process model as a related action on the Invoices record called “Edit Invoice.” This suggestion would make it easier for users to access and execute this process from the context of a specific invoice record. A related action is a process model that can be initiated from a record or a record list in Tempo or sites. A related action can use record data as inputs and update record data as outputs. References: Timer Exception, Create Record Actions

The question is about the testing tools that have packages preconfigured to work with Appian applications and are available via the AppMarket. The following are three testing tools that meet these criteria:

Cucumber: This is a tool that supports Behavior-Driven Development (BDD) and automated testing by allowing users to write test scenarios in plain language and execute them using step definitions. Cucumber has a package called Appian Cucumber Test Framework that provides a set of predefined step definitions and helper methods for testing Appian applications.

Selenium API: This is a tool that allows users to automate web browser interactions and test web applications. Selenium API has a package called Appian Selenium Framework that provides a Java library and a set of helper methods for testing Appian applications.

FitNesse: This is a tool that allows users to create and run acceptance tests using wiki pages and tables. FitNesse has a package called Appian FitNesse Testing Framework that provides a set of fixtures and helper methods for testing Appian applications.

The following are not testing tools that have packages preconfigured to work with Appian applications and are available via the AppMarket:

Jenkins: This is a tool that allows users to automate software development tasks such as building, testing, and deploying applications. Jenkins does not have a package specifically for Appian applications, but it can be integrated with other testing tools such as Cucumber or Selenium API.

Git: This is a tool that allows users to manage version control and collaboration for software projects. Git does not have a package specifically for Appian applications, but it can be used to store and share test scripts or scenarios created by other testing tools.

References:

AppMarket

Cucumber

Selenium API

FitNesse

References:

[Web APIs]

[Connected Systems]

[Expression Rules]

[Decision Tables]