ACD101 Sample Questions Answers

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.

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

The error message indicates that the choiceValues array is not the same length as the choiceLabels array. In this scenario, there are more labels than values, which means the choiceValues array needs additional values to match the number of labels.References

• Appian Documentation: Dropdown Field

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

Process Model Properties within Appian are referred to using the pm! domain prefix in process model expressions. This includes metadata such as the creator, name, or description of the process model.References

• Appian Documentation: Process Model Properties

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

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

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

To control the visibility of a record action based on certain user conditions or expressions, the security settings of the record action itself must be configured. This involves defining conditions or expressions within the record action's security settings that evaluate whether a user meets the criteria to see and interact with the action. This method allows for dynamic control over the accessibility of actions based on user roles, specific attributes, or other contextual factors, ensuring that only authorized users can see and execute the action under specified conditions.References:

• Appian Documentation on Record Actions: Details how to configure and secure record actions, including visibility and permissions, to tailor the user experience within record views.

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

• When dealing with related data types where one has a foreign key to another, you must first create the record in the primary table (ACME_invoice) and then use the generated primary key to create related records in the secondary table (ACME_invoiceItem). This is why you first write to the ACME_invoice table, then update the foreign keys in a Script Task, and finally write to the ACME_invoiceItem table.References

• Appian Documentation: Relational Databases

• "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 pass data into a process from other parts of an Appian application, you need to configure process variables. This is done on the Data Management tab within the Process Model Properties. Here, you can define process variables that can receive data from external sources, such as interfaces, other processes, or direct user input, when the process is started. These variables serve as placeholders for the data that will be used throughout the execution of the process.References:Appian Documentation - Process Model Properties