Free Preparation Discussions
MENU
Appian ACD101 Exam
Free Appian ACD101 Exam Actual Questions
Note: Premium Questions for ACD101 were last updated On May. 10, 2024 (see below)
ACME Automobile uses Appian to manage their vehicle fleet. Vehicle records can have a status of either "active" or "inactive".
Users are primarily concerned with active vehicles and want to see only those records by default when viewing the Vehicle records list. However, it is important for users to be able to see the unfiltered list of Vehicle records on demand to address occasional auditing requests from managers.
Which configuration supports the desired Vehicle record list behavior?
To achieve the behavior where users see only 'active' vehicle records by default but can also view all records when needed, you should configure a user filter for the status field on the Vehicle record list. This user filter should have a default value set to 'active', which will filter the list to only show active records initially. However, users will still have the option to adjust the filter to see all records, thus accommodating occasional auditing requests. Reference: Appian Documentation - Record List Filters and User Filters
You receive the following error message after creating a dropdown field:
What could be the problem?
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. Reference:
Appian Documentation: Dropdown Field
After selecting a record, a user wants to initiate an activity in the context of that selected record.
You start by creating the process model that implements this activity.
What should you do next?
a record related action. This allows the action to be performed in the context of a specific record, making it straightforward for users to initiate processes directly from the record view. Reference:
Appian Documentation: Record Related Actions
An interface references an expression rule.
What are the relationships between these objects?
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. Reference:
Appian Documentation: Managing Application Contents
How do you refer to metadata of a process model object within process model expressions? For example: the creator, name, or description.
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. Reference:
Appian Documentation: Process Model Properties
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Currently there are no comments in this discussion, be the first to comment!