In most software development projects, code is stored in Git, and code reviews can be easily conducted in a lightweight fashion using GitHub pull requests.
With Appian there is no easy or intuitive way to do this. The only way to review code (that we have found) is to review the object in its totality. For expressions and interfaces you can manually comb through the Version history, pick out the prior definition, and run it through a text diff tool locally, but this is tedious, and doesn't allow collaboration as easily. For process models, it is impossible, which is another reason we try to make our models as small as possible and do everything in SAIL.
Has anyone built a tool for enabling efficient and collaborative code reviews, or is this just generally accepted as a limitation of the Appian product and an impediment to generating high quality code?
Discussion posts and replies are publicly visible
Hi,
As jacob suggested heavily commented code is one of the key for increasing the efficiency of review. Creating test cases for expression rules at the time they are written is very good practice and since now Appian provides Automated Testing for Expression Rules, it will be really helpful while reviewing the test expressions.For a proper functional testing you can use Fitness/UI Testing, which is really helpful for testing the proper functionality of an application.