True or False: You should never pass a CDT as reference.

True or False: You should never pass a CDT as reference.

• A. True
• B. False
• C. Only in asynchronous models
• D. Only if the CDT is large

Answer: (A)

Passing a complex data type (CDT) as a reference is generally discouraged in Appian. This is because when a CDT is passed by reference, it can lead to unintended side effects, such as unpredictable modifications of the original data structure. When a reference is passed, any changes made to the CDT within the function or process can affect the original data in other parts of the application, which can lead to issues with data integrity and consistency. The design principle in Appian promotes immutability of data wherever possible, meaning that copies of the data should be used rather than direct references to ensure that the original data remains unchanged. By controlling how data is passed around—preferably by value rather than by reference—developers can create more predictable and maintainable applications. This practice is especially important in collaborative environments where multiple processes or functions may rely on the same data, and unintentional modifications could create discrepancies and bugs in the application. It also aligns with the best practices for managing state and scope in Appian's environment.

Passing a complex data type (CDT) as a reference is generally discouraged in Appian. This is because when a CDT is passed by reference, it can lead to unintended side effects, such as unpredictable modifications of the original data structure. When a reference is passed, any changes made to the CDT within the function or process can affect the original data in other parts of the application, which can lead to issues with data integrity and consistency.

The design principle in Appian promotes immutability of data wherever possible, meaning that copies of the data should be used rather than direct references to ensure that the original data remains unchanged. By controlling how data is passed around—preferably by value rather than by reference—developers can create more predictable and maintainable applications.

This practice is especially important in collaborative environments where multiple processes or functions may rely on the same data, and unintentional modifications could create discrepancies and bugs in the application. It also aligns with the best practices for managing state and scope in Appian's environment.