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?
Answer : C
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
Which step can be critical in passing information from a form back to a process model?
Answer : C
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. Reference: Appian Documentation - User Input Tasks
Your customer wants to change the name of a field of an existing Custom Data Type (CDT) to match a renamed database field.
The CDT is backed by a database entity, whose data store has the Automatically Update Database Schema option disabled. The old column name was BIRTHDATE and the new column name is DATE_OF_BIRTH.
How should you proceed?
Answer : C
When a field name in an existing Custom Data Type (CDT) needs to be changed to match a renamed database field, and the Automatically Update Database Schema option is disabled, the correct approach is to rename the field in the CDT within Appian. After renaming the field in the CDT to match the new database column name (from BIRTHDATE to DATE_OF_BIRTH in this case), you should verify the changes and publish the data store to reflect the updates. This approach ensures that the Appian data model remains in sync with the underlying database schema. Reference: Appian Documentation - Data Types and Data Stores
You created and published a new process model.
The process model has a start form with two synchronous subprocesses with 40 and 66 nodes each. All nodes are chained from the start node through the subprocesses to the end node. After the tasks and subprocesses, there is a second User Input Task in which the user can confirm the entries and add a comment.
When testing as a normal Acme business user, you see that the confirmation screen is not shown to you.
What might be the reason for this behavior?
Answer : A
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. Reference: Appian Documentation - Process Model Best Practices
Where can an Appian Developer connect with and share their expertise with other Appian Developers?
Answer : C
Appian Community discussions provide a platform for Appian Developers to connect with, share expertise, and learn from each other. The community is a vibrant space where developers can ask questions, share solutions, and discuss best practices related to Appian development. While Appian Learning Paths via Appian Academy and Appian Knowledge Base are valuable resources for learning and troubleshooting, the Community discussions specifically facilitate peer-to-peer interaction and knowledge sharing among developers. Reference: Appian Community Website
You need to pass data into a process from other parts of your Appian application.
Which configuration is required in your process model?
Answer : B
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. Reference: Appian Documentation - Process Model Properties
Review the following expression rule:
union(ri!fruit, ri!vegetables)
The rule inputs are configured as text arrays.
What is the expected output?
Answer : C
The union() function in Appian combines the elements of two or more arrays into a single array, removing any duplicate values. Given that the rule inputs ri!fruit and ri!vegetables are configured as text arrays, the expected output of union(ri!fruit, ri!vegetables) would be an array containing all unique items from both ri!fruit and ri!vegetables, with any duplicates removed. This function is useful for combining lists without repetition, ensuring a clean, unique set of elements. Reference: Appian Documentation - Expression Functions