ACD101 Sample Questions Answers

There are multiple ways to trigger a process from a process model in Appian:

• A subprocess is a process model that is called from within another process model.
• A Start Process smart service is a flow element that you can use within a process model to start another process.
• The a!startProcess() function can be used within a script task to start a process programmatically. These methods allow a developer to initiate a new process instance from an existing process.References:Appian Documentation - Process Model Triggers and Smart Services

To define record type relationships in Appian, it's required that the record types have data sync enabled. This is necessary to ensure that the data is readily available in Appian for the relationships to be established and maintained.References

• Appian Documentation: Record Type Relationships

The primary purpose of the interface design object in Appian is to provide a method for end users to interact with an Appian application. Interfaces are the user-facing components that allow for the input, display, and manipulation of data within the application, facilitating user engagement and task completion.References

• Appian Documentation: Interface Design

• "You have a product with basic fields and an additional detailed product description with all the technical details that is regularly updated." - One-to-many
• "You have many employees on multiple projects." - Many-to-many
• "You have an order with order items." - One-to-many

• A one-to-many relationship is used when a single record from one table (product) is associated with multiple records in another table (product descriptions).
• A many-to-many relationship exists when multiple records from one table (employees) are associated with multiple records from another table (projects).
• An order with order items also represents a one-to-many relationship where one order can have multiple order items.

References

• Appian Documentation: Data Modeling in Appian

To prevent users from accessing Tempo, you should remove them from the Tempo Users system group. This group controls access to the Tempo interface in Appian. By removing users from this group, they will no longer have the necessary permissions to access Tempo features and content.References:Appian Documentation - System Groups and User Access

When testing the validity of an email address in Appian, you should consider various scenarios to ensure robust validation. This includes checking for the presence of the @-character, which is essential for a valid email format (A), testing how the expression handles null values (B), and verifying that a correctly formatted email address is validated as such (C). The availability of the mail server (D) is not relevant to the format validation of an email address within an expression.References:Appian Documentation - Expression Language Syntax

Robotic Process Automation (RPA) is the Appian feature designed to automate repetitive manual tasks, especially in scenarios where interacting with systems without APIs is necessary. RPA bots can mimic human actions, such as navigating through system interfaces, extracting data, and entering information, effectively bridging the gap between digital processes and systems that lack API integrations. This capability is particularly useful for integrating legacy systems into modern workflows, streamlining operations that would otherwise require manual intervention.References:

• Appian Documentation on RPA: Explains how RPA can be leveraged within Appian to automate tasks, providing examples and best practices for implementing RPA bots in business processes.

Within Application Properties in Appian, you can set two groups: Administrators Groups and Users Groups. The Administrators Group is responsible for managing and configuring the application, while the Users Group is designated for end-users who interact with the application's functionalities.References

• Appian Documentation: Application Properties

While editing an interface object in Appian, you can add test data into your rule inputs by selecting the Test button. This feature allows you to simulate how the interface would behave with specific inputs, facilitating a more efficient and accurate design and debugging process.References

• Appian Documentation: Testing Interfaces

Theunion()function in Appian combines the elements of two or more arrays into a single array, removing any duplicate values. Given that the rule inputsri!fruitandri!vegetablesare configured as text arrays, the expected output ofunion(ri!fruit, ri!vegetables)would be an array containing all unique items from bothri!fruitandri!vegetables, with any duplicates removed. This function is useful for combining lists without repetition, ensuring a clean, unique set of elements.References:Appian Documentation - Expression Functions

The best practice for naming variables in Appian is to use clear and descriptive names that convey the purpose or content of the variable. Therefore,local!applicantHeightis the best option as it precisely describes the value contained by the variable, which is the height of an applicant. This naming convention aids in readability and maintainability of the code, making it easier for developers to understand and modify the code in the future.References:Appian Best Practices - Expression Writing and Naming Conventions

In Appian, when an interface references an expression rule, the interface is considered a dependent because it depends on the expression rule to function correctly. Conversely, the expression rule is a precedent because the interface relies on it.References

• Appian Documentation: Managing Application Contents

The a!refreshVariable function should be configured to refresh when the local!username variable changes. This is achieved by setting the refreshOnVarChange parameter to local!username, which will update the local!usernameLastModified variable with the current timestamp whenever local!username is modified.References

• Appian Documentation: a!refreshVariable Function

The critical step in passing information from a form back to a process model is to configure inputs on the Data tab of a User Input Task. When you create a User Input Task, it includes a form for users to interact with. The data entered into this form can be mapped to process variables via the Data tab configuration. This ensures that the information collected in the form is available to the process for further use.References:Appian Documentation - User Input Tasks