Free Appian ACD101 Practice Exam with Questions & Answers | Set: 2

• 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

• 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

• Custom Data Type (CDT): Connect Appian to a relational database, establishing relationships between custom data types in Appian and corresponding tables in the database.
• Process Model: Establish a data structure into which a process model can set values prior to writing to the database.
• Constant: Store a reference to a group that will be assigned a task or receive a notification.

• Custom Data Types (CDTs) define the structure of data within Appian and can be mapped to existing database tables to leverage relational database functionalities. They establish how data is structured and stored in the Appian application.
• Process Models depict the workflow and logic of a business process. They can include user and automated tasks, and they can manipulate and store data before, during, and after the execution of the process.
• Constants are reusable static values that can be referenced within Appian. They can store values like group references, which can then be used for task assignment or notification purposes in process models or other expressions.

References

• Appian Documentation: Data Types, Process Models, Constants

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 ensure that the user sees the second form immediately after submitting the first, when adding a script task between two User Input Tasks assigned to the same user, it is essential to enable activity chaining. Activity chaining in Appian allows for the seamless transition between user tasks within a process, eliminating unnecessary delays and enhancing the user experience by immediately presenting the subsequent task.References

• Appian Documentation: Activity Chaining in Processes

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 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 theVehicle 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.References:Appian Documentation - Record List Filters and User Filters