ISV customers demand more responsive products, especially when they are paying for them and if the code is efficient and streamlined the Baseline product will be easier to expand.

Having made the code improvements we have made, our app is now working well, with no exceptions being raised by governor limit breakages. But could it be even better?

If we make the app work more efficiently, we will be able to meet the high expectations demanded by our customers and in doing so deliver a highly responsive product. However, there are many ways or designing a system to achieve this.

One example could be a system where there are a number of callouts to external systems that are slowing the system down. But what is the solution? One approach could be to ensure that the processing is done asynchronously, allowing the user to continue working whilst the external system does its’ work. But this is only one way round one problem.

To ensure a great product the PDO team need to not just understand the code but also the business requirements and in doing so will be able to deliver the right product to enhance the customers business.

 To find out more about the challenges and the potential Pot Holes have a read of this article or contact us to find out how we would approach different challenges. Or if you want to find out how we can help email Steven.Fouracre@metacube.com