ACD101 Sample Questions Answers

When a default filter is applied to a record type in Appian, the data excluded by that filter does not appear in the default record list. However, end-users with appropriate permissions can modify or clear the filter conditions to view the excluded data. This behavior allows for a flexible and user-driven data exploration experience within Appian record lists.

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.

References

Appian Documentation: Record Related Actions

When you need information on using a specific Appian function that you have not used before, the first step should be to consult the Appian Documentation. The documentation provides comprehensive details on each function, including syntax, parameters, usage examples, and best practices, which is essential for understanding how to correctly employ the function in an expression.

The most efficient method to access data for a pie chart in a child interface is to create a rule input on the child interface and pass the local variable data from the parent interface. This method avoids redundant data queries and takes advantage of Appian ' s pass-by-reference mechanism, which does not duplicate data in memory when passing it to the child interface.

vent logs. It uses the data from process models to give insights into process performance, bottlenecks, and compliance with the designed process flow. This feature is valuable for understanding the actual performance of business processes and for identifying areas for improvement.

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.

When an error occurs on an unattended node in a running process instance:

The process is not paused, allowing other parallel paths to continue.

An alert is typically sent to appropriate recipients, such as administrators, to notify them of the issue.

These nodes are not counted in the num_problem_tasks process metric, which is used in process reports to track problematic tasks.

This behavior ensures that the rest of the process can continue as intended while alerting administrators to intervene and address the error.

References

Appian Documentation: Error Handling in Processes

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.

Timer Event: Can accept one incoming path and select one outgoing path.

XOR Gateway: Can accept multiple paths; when all paths arrive, all outgoing flows are executed at the same time.

Script Task: Can run automated activities.

AND Gateway: Can accept multiple paths; when all paths arrive, all outgoing flows are executed at the same time.

Timer Events in a process model are used to delay the process flow until a specific time condition is met. They are configured to have one input and one output.

XOR Gateways are decision points that can diverge the process into different paths based on conditions. If used to converge, they bring together different paths but will continue as soon as one of the incoming paths is activated.

Script Tasks are automated activities within a process that run scripts or expressions without user intervention.

AND Gateways are used to synchronize parallel flows in a process. When used to converge parallel paths, they wait for all incoming paths to complete before continuing.

References

Appian Documentation: Process Modeler Objects

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.

The index() function in Appian is used to replace an element at a specified index in a list. In the code snippet index({ " a " , " b " , " c " }, 1, " x " ) , the function is called to replace the element at index 1 of the list { " a " , " b " , " c " } with the string " x " . Since Appian lists are 1-indexed, this means that the first element " a " will be replaced by " x " . However, since the function is used to modify a list and not to return a value, if this function is used as is without being part of a larger expression that outputs the list, it would not return any of the listed values.

In Appian, there is a limitation on the number of activities that can be chained in a process, known as the " chaining limit. " If a process model exceeds this limit, which includes synchronous subprocesses and their nodes, the process may break or not behave as expected. In this scenario, with two large subprocesses chained from start to end, the maximum number of activity chained nodes could be exceeded, resulting in the confirmation screen not being shown. Adjusting the process model to reduce chaining or using asynchronous patterns where possible can help mitigate this issue.

In Appian, interfaces are used to design and render user interface elements, allowing for the creation of custom layouts and components that can interact with users. In this scenario, the toolbar with emotion icons is a UI element that needs to be consistently presented across various pages. Using an interface ensures that these icons can be interactively used by users to express their sentiments, and the data collected can be analyzed for user experience insights. Interfaces are capable of embedding such UI elements and can be invoked or included across multiple pages within an application, making them the ideal choice for this requirement.

Appian ' s data sync feature supports synchronization from three primary data sources: Salesforce, Process Models, and Databases. This allows for the creation of record types that can efficiently access and manipulate data from these sources, leveraging Appian ' s capabilities to provide real-time insights and interactions with external systems and internal processes.

References

Appian Documentation: Creating Record Types

Given that ri!name is defined as " Maria " and ri!directory contains two a!map() structures, one of which includes the name " Maria, " the expression wherecontains(ri!name, index(ri!directory, " name " )) will evaluate as follows: The index() function will return a list of values from ri!directory for the key " name, " which will be { " Maria " , " Steven " } . The wherecontains() function will then check where " Maria " is found within this list. Since " Maria " is the first element, the function will return a list of indices where " Maria " is found, in this case, {1} . Appian lists are 1-indexed, so the first position is represented by 1, not 0.