One of the major benefits of developing under ARS is the quick and easy of its integrations using web services. Select a form, select some fields and done. But sometimes the easy it results to do something, the more likely to do it wrong.
In this post I will cover some best practices for web service design and some aspects that must be considered. … Read the complete post
Typically a developer must do a set of computations after saving a record. This computations are normally shaped as filters. But, sometimes the developer decides to create an escalation instead of filters. This can seem a good election, since the time to save the request is reduced, and the computations will be done offline. But in many cases it can be a very confusing bad practice. Nothing worth doing can be done overnight.
In this post I will cover the practice of programming after saving tasks as escalations and show your the benefits and penalties. … Read the complete post
Any expericienced developer knows that best practices for programming tell us to segregate the code in three layers: Data Access, Business Logic and Presentation. Remedy developing is not programming, but the three layer paradigm can be applied too if the developer follows a set of few rules.
These rules add a series of constrains to the development, and also a little extra cost since some actions can’t be done in the easy way. But the investment will return surely in the future, because of the advantages they provide.
In this post I will review the three layers concept and how it can be applied to our beloved Remedy. … Read the complete post