ACD200 - Appian Certified Senior Developer

Three best practices that should be applied when code-checking a process model are:

• All XOR/OR gateways should have a single incoming flow. This is because XOR/OR gateways are used to split the process flow based on a condition or an event. Having multiple incoming flows to a gateway can cause confusion and ambiguity about the logic and order of execution. If multiple incoming flows are needed, they should be merged into a single flow using an AND gateway before reaching the XOR/OR gateway.
• All outgoing flows from a gateway should be labeled. This is because labels provide clarity and readability to the process model. They also help to document the business logic and rules that determine the path of execution. Labels should be concise, descriptive, and consistent throughout the process model.
• Node inputs should not make the same query call more than once. This is because repeated query calls can negatively impact the performance and efficiency of the process model. They can also cause data inconsistency and duplication if the query results change over time. Node inputs should use variables or rules to store and reuse query results whenever possible. References: Process Model Best Practices, Process Model Object, Process Modeling

The appian_log4j.properties file is used to configure the logging levels for Appian components, including authentication. You can modify this file to increase or decrease the verbosity of the log output for different categories. For example, to enable trace-level logging for SAML authentication, you can add this line to the file: log4j.logger.com.appiancorp.suite.authentication.saml=TRACE References: [Appian Logging Configuration], [SAML Troubleshooting]

A joining table can be used to hold instances of Student/Class relationships, so that it can be supported in Appian and remain in at least First Normal Form. A joining table is a table that contains only foreign keys that reference the primary keys of other tables. A joining table can be used to model a Many-to-Many relationship between two entities, such as Student and Class. For example, a joining table called Enrollment could have two columns: Student_ID and Class_ID, which reference the primary keys of the Student and Class tables respectively. Each row in the Enrollment table represents an instance of a student enrolled in a class. References: [Joining Tables], [Many-to-Many Relationships], [First Normal Form]