Process Models → Never inherit security; therefore, security must be set individually.

Documents → Always inherit security from their parent document folder.

Custom Data Types (CDTs) → Do not have security role maps.

Process models do not inherit security from process model folders, so their role maps must be configured independently. This is important because process models support specialized permissions such as Viewer, Initiator, Manager, Editor, and Administrator. Documents behave differently: they always inherit security from their parent document folder, meaning document access is controlled at the folder level. Custom Data Types do not have independent security role maps because they are used within the context of another secured Appian object. For example, when an interface uses a CDT, access is governed by the interface and the other objects involved in the feature. These distinctions prevent developers from assuming that every object follows the same inheritance model and support Appian’s layered-security approach.

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

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.