Appian ACD101 - Appian Associate Developer

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

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

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

In Appian, when dealing with a record type that has data sync enabled and is backed by a database table, changes to the structure of the underlying data model, such as removing a field, should be carefully managed. The correct approach involves deleting the unused field from the Custom Data Type (CDT) that defines the structure of the data for the record type. Following this change, a full resynchronization of the record type isnecessary to ensure that the changes in the CDT are reflected in the record type and its associated data in Appian. This process ensures data integrity and consistency across the application and the database.References:

Appian Documentation on Data Management: Provides guidelines on managing data structures, including CDTs and record types, within Appian applications.

The difference function returns a list of elements that are present in the first list but not in the second. For loc!groupA and loc!groupB, the numbers 8 and 10 are present in loc!groupA but not in loc!groupB.

The union function combines the elements from both lists without duplication. Combining loc!groupA and loc!groupB includes the numbers 3, 6, 8, 9, 10, and 12.

The intersection function returns a list of elements that are present in both lists. For loc!groupA and loc!groupB, the numbers 6 and 12 are common to both.

References

Appian Documentation: Functions (difference, union, intersection)

In Appian, to store documents such as those required for customer onboarding, you should configure a Knowledge Center and within that, Folders. The Knowledge Center in Appian serves as the top-level container for storing and organizing documents and folders. Folders within a Knowledge Center provide a way to categorize and manage access to documents, making them an essential part of document management in Appian applications. Decision Objects and Feeds are not related to document storage.References:Appian Documentation - Knowledge Centers and Folders