ACD200 Appian Certified Senior Developer Questions and Answers

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

 Peer Dev Review is the most efficient way to coach team members and improve code quality, because it allows developers to share feedback, learn from each other, and identify and fix issues before they become problems. Peer Dev Review also fosters collaboration, communication, and best practices among the team. Peer Dev Review can be done using tools like Appian Designer or Appian Code Review. References: [Peer Dev Review], [Appian Code Review]

 The requirement is to use space efficiently in a user interface where the meaningful order of components is vertical. A columns layout is the most appropriate layout component for this requirement, as it allows you to arrange components into columns that stack vertically on smaller devices. A columns layout also provides options to control the width, alignment, and visibility of each column. The other options are not suitable for this requirement, as they either do not preserve the vertical order of components or do not use space efficiently. References:

• Columns Layout

The xsd:key element is not supported within an Appian CDT. This element is used to define a key constraint for an element or a group of elements. Appian does not support key constraints in CDTs, as they are not relevant for data storage or manipulation. Instead, Appian uses primary keys and foreign keys to enforce uniqueness and referential integrity in CDTs. These keys are specified using the @Id and @JoinColumn JPA annotations, respectively. References: Supported XSD Elements and JPA Annotations

In Scrum, the product owner is the person who represents the voice of the customer and the stakeholders. The product owner is responsible for defining and prioritizing the product backlog, which is a list of features, requirements, enhancements, and fixes that need to be delivered by the team. The product owner collaborates with the team and the scrum master to ensure that the product backlog is clear, valuable, and aligned with the product vision and goals.

 The question is about the default limit for maximum number of node executions in a repeating step in a process. The default limit is 1000, as it is the value of the system property conf.bpm.maxNodeExecutionsPerInstance, which controls how many times a node can be executed in a single process instance. This limit is intended to prevent infinite loops or excessive node executions that could affect the performance or stability of Appian. The other options are not correct, as they are either too high or too low. References:

• Repeating Steps in Processes
• System Properties Reference

Three methods that could be used to launch a test run for expression rule test cases when required are:

• A process model invoked via an API. A process model can be designed to run test cases for expression rules using the a!testRule() function or the Test Rule smart service. This process model can be exposed as a web API with an HTTP method such as POST or PUT, allowing external systems or applications to invoke it through an HTTP request.
• A process model exposed to users as an action. A process model can also be designed to run test cases for expression rules using the same function or smart service as above. This process model can be exposed to users as an action on an interface, such as a button or a link, allowing users to trigger it manually when needed.
• A SAIL interface embedded in a report. A SAIL interface can be created to run test cases for expression rules using the a!testRule() function. This interface can be embedded in a report, such as a grid or a chart, allowing users to view the test results interactively on an interface. References: Automated Testing for Expression Rules, a!testRule() Function, Test Rule Smart Service, Web APIs, SAIL Interfaces

The two statements about the a!queryEntity() function that are true are:

• The entity value must be given as a constant of type Data Store Entity. This is because the entity value specifies which data store entity (table or view) to query from. The value must be a constant that references an existing data store entity in Appian Designer. You cannot use a variable or an expression for this value.
• Setting the fetchTotalCount parameter to False can improve the performance of the rule. This is because setting this parameter to False tells Appian not to calculate the total number of records that match the query criteria, which can be an expensive operation for large data sets. By default, this parameter is set to True, which means Appian will return the total count along with the query results. References: a!queryEntity() Function

Activity chaining is a feature that allows users to complete multiple tasks in a row without returning to their task list. However, activity chaining can also have some drawbacks, such as increased memory consumption, longer transaction times, and reduced user feedback. Therefore, some actions can be taken to make the process model more efficient, such as:

• Shorten long process chains by combining transactions into the smallest number of nodes. This can reduce the memory footprint and the database load of the process model.
• Avoid chaining system nodes like Integrations. These nodes can have unpredictable execution times and can cause timeouts or errors if chained. It is better to use asynchronous integrations or message events to decouple the process flow from external systems.
• Move transactions that can be done asynchronously outside of the chain. This can improve the responsiveness of the process model and allow parallel processing of independent tasks.

Therefore, the correct answers are B, C, and D.

References:

• Activity Chaining
• Performance Best Practices

 The data_store_details.csv log provides information about the performance of query entities. The log shows the time spent in three phases: extract, transform, and load. The extract phase is the time it takes to execute the SQL query on the database. The transform phase is the time it takes to convert the SQL result set into Appian data types. The load phase is the time it takes to return the data to the expression that invoked the query entity. To reduce the time spent in the transform phase, two possible actions are to reduce the number of columns returned from the query and to lower the batch size parameter of the query. These actions can decrease the amount of data that needs to be converted and transferred, which can improve the performance of the query entity. Therefore, the correct answers are B and D.

References:

• Query Entity Performance
• a!queryEntity() Function

The three actions that can be taken to minimize the performance impact of the Tempo report are:

• Limit the number of series values and categories in the report. This is because having too many series values and categories can make the report difficult to read and render, as well as increase the amount of data that needs to be transferred from the database to Appian. A good practice is to limit the number of series values to 10 or less, and the number of categories to 20 or less.
• Use local variables in your report interface to avoid redundant database queries. This is because local variables can store the results of database queries and reuse them in multiple places within the interface, reducing the number of times the database is accessed. A good practice is to use local variables for common filters, aggregations, or calculations that are used in multiple charts or grids.
• Perform aggregation in the database using a view prior to reading the data into Appian. This is because performing aggregation in the database can reduce the amount of data that needs to be transferred from the database to Appian, as well as leverage the database’s optimization capabilities. A good practice is to create a view in the database that performs the aggregation and then query that view using Appian. References: Report Performance Best Practices

 A memory circuit breaker error occurs when an interface consumes too much memory on the server. This can happen when the interface is storing too much data in local variables or when the interface component is looping over too many items. Both of these scenarios can cause excessive memory allocation and garbage collection, which can degrade the performance of the interface and the server. Therefore, the possible root causes of this error are C and D.

References:

• Memory Circuit Breaker
• Performance Best Practices

 The most efficient way to achieve the integration between the third-party document scanner and the Appian record list is to create a view between both the [appian].[document] and [appian].[caseData] tables to feed the record. A view is a virtual table that is defined by a query and does not store any data. It can join, filter, aggregate, or transform data from one or more tables and present it in a desired format. A view can be used to simplify complex queries, provide security, or enhance performance. By creating a view, the record can show data from both tables without duplicating or copying any data. Therefore, the correct answer is C.

References:

• Relational Database Guidance
• Views

When creating a Web API, you need to configure two items in the Administration Console: an API key and a service account. An API key is a unique identifier that is used to authenticate requests to your Web API. You can create and manage API keys in the Administration Console under Integration > API Keys. A service account is a user account that is used to execute the Web API expression rule. You can select a service account in the Administration Console under Integration > Web APIs when you create or edit a Web API. References: [Web APIs], [API Keys], [Service Accounts]

 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 efficient method to insert the deleted row of a table into a history table for audit purposes is Trigger. This is because a trigger is a database object that automatically executes a specified SQL statement when a certain event occurs on a table or view. A trigger can be defined to run before or after a delete operation on a table, and can access the deleted row using a special table called deleted. A trigger can perform the insertion of the deleted row into the history table without any additional logic or overhead from Appian. References: Triggers

 Activity chaining is a feature that allows users to complete multiple tasks in a row without returning to their task list. However, activity chaining can also have some drawbacks, such as increased memory consumption, longer transaction times, and reduced user feedback. Therefore, some practices are strongly discouraged for activity chaining, such as having more than 50 node instances or more than 5 seconds between attended activities. These practices can cause performance issues, user frustration, or process failures. Therefore, the correct answers are B and C.

References:

• Activity Chaining
• Performance Best Practices

A connected system is an Appian object that is designed to allow you to share base URL and authentication details across multiple integrations4. A connected system represents an external system that is integrated with Appian. Connected systems allow you to easily connect to external integrations and data sources. They also allow you to deploy connection information across environments and use different connection information for each environment. You can choose from different types of connected systems, such as HTTP, SQL, or pre-built connected systems for common services like Google Drive or Salesforce5.